Image deployed from incorrect storage node
-
Hello,
Let’s say I have 2 locations/storage node. Texas location which is the Master Node and California which is the Slave Storage Node, both of them are under the same group and I can see the images synced to the California node. I’ve ran into issue where if I selected California for location during the imaging process, it’ll still pull the image from Texas which is the master node.
On the laptop screen it says it’ll pulling from the <texas_ip>/images and under task management in the web page, it’ll say location California but working with Texas node.
What’s weird is I can see that it’s downloading the inits from the California node. To my understanding, if I’m in California and I select California for the location during imaging, it’ll pull the image from California. Please correct me if I’m wrong on this.
I also check the .fogsettings file and make sure all info are correct.
But have any of you ran into this issue and is there anything I can do to fix this?
Thanks in advanced.
-
@brian-mainake So do you have the fog location plugin installed? If yes you allocated each storage node (master or slave) to a specific location?
The last bit during fog target host registration, did you allocate the target computer to a certain location? From your explanation it sounds like either the storage node (master or slave) or the target computer is not in the same location so it goes to the master node.
-
@george1421 very sorry for the late response.
yes i have the plugin installed and allocate each storage node to a specific location.
yes during the fog registration, i selected the specific location. so if the target computer is in california office, i selected california.
the california slave storage server is in the california office, and same as the target computer. i even tried on VMs that the server is hosted in the same location. but i would run into the same issue.
when the image is being deployed, it’ll say <texas ip>/images instead of pulling it from california for example.
-
@brian-mainake Which version of FOG do you run? Are all the nodes on the same version?
-
@brian-mainake Need more information.
-
@Sebastian-Roth Sorry for the late response. I ended up re-installing everything and its good now. I also changed the permission of the images to executables on the storage nodes, not sure if that helps but its all working now.
Thank you for your help.
-