All storage nodes look up images in default
-
Hi @Tom-Elliott , I’m not sure I’ve explained myself.
We have two storage groups: default and storage1, each composed by a single node.
If I upload an image to storage1, I can. When but I try to download it, I get a message saying I must upload it first. I’ve realized it is searching in default storage group, not storage1. -
@Frank That’s how it’s supposed to work.
The image doesn’t exist on the other group because that’s not where the default group WAS.
-
@Frank Basically, it should only be associated to the storage1 group. If the image doesn’t exist within storage1 group, it should fail as you’re seeing. What we need to know is where it currently actually is.
-
@Tom-Elliott the image IS in the storage1 node. I can see it on /images directory
-
@Frank What I mean, what storage GROUP is the image associated with?
-
@Frank The only thing is that storage1 node wasn’t market as master. Can it be the reason? The image is associated to storage1 group
-
@Frank From the sounds of it, FTP can’t login to your Master storage node. It checks the node it’s trying to use for the image.
Can you run through the FTP troubleshooting guide?
-
@Tom-Elliott I’ve made a test with storage1 node as master and it is the same. It keeps on looking at default storage group. I’m going to update code as you suggested.
-
@Tom-Elliott after upgrading to 6547 it works!!
So it seems something related to your last fixes.
Thanks for you help.
What do you recommend me as update policy? How do I know if an update is stable? -
@Frank I don’t know if an update is stable until somebody updates and lets me know if prior issues are corrected for.
It’s one of the “cons” i guess of being on Trunk.
While I try my darndest to keep things as functional as I can, with changes can come problems.
