Storage Node different for capture and deploy
-
Hello,
I have a little problem with my fog server 1.5.2. I have 2 storage node : “default” used only for wol and multicast. And a second nfs node for to save my images. When i capture an image it’s work perfectlly fog save my image on my second node (name is Ubox) but when i want to deploy this image the storage node used is all the time the “default”…
Could you explain me if it’s normal operation or it’s a bug?
I have try to skip this problem to set Max Clients to 0 on my default Node it’s work but when i want to see my Nodes on the Storage Management web page i have a blank page…
Thanks alot to help me
-
@zeltron80 said in Storage Node different for capture and deploy:
Could you explain me if it’s normal operation or it’s a bug?
It’s normal operation. FOG uses the first server it finds that has available slots - unless you’re using the location plugin which changes this behavior.
I have try to skip this problem to set Max Clients to 0 on my default Node it’s work but when i want to see my Nodes on the Storage Management web page i have a blank page…
This is a known bug in 1.5.1 and 1.5.2 where if the max clients is set to 0, it causes a problem. This will be fixed in the next release candidate.
