Overflow imaging from storage node that's not a master in a storage group
-
@Wayne-Workman I know that it does. Simply assign ONLY a storage group, and any nodes within the storage group will be available to the host in question.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott That’s what I instructed @JGallo to do, but when he does that, it unsets the storage group. Look at his last post.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman @Tom-Elliott I just imaged one computer with the empty storage group in the location plug in and it pulled the image from the slave node. I’m going to leave it like that for now and when we go to image the lab later today, I will report. Like I said before, it is strange that the storage group is not visually represented on the location management page but once you click on the location, you can see that the storage group is defined.
-
@Wayne-Workman It doesn’t unset the storage group, it just doesn’t show the storage group under the list all item. Likely just a typo, but at the moment not a high priority thing.
-
@Tom-Elliott @Wayne-Workman Worked like a charm. The lab imaged with 20 going on at once with both nodes active and remaining clients were placed in line to wait until slots opened up. Thank you both for all your help.
-
@JGallo said in Overflow imaging from storage node that's not a master in a storage group:
Interesting bug I think may exist…
As Tom said, just a display thing. I got around to figure this out today and pushed a fix to the
dev-branch. I don’t have a proper setup to test location deployments and all. It does fix the display issue for sure (tested) but I don’t find the time to setup and test the whole lot. -
@Sebastian-Roth Cool. We have several projects in the mix right now but once it slows down, I plan on upgrading to 1.5.5 since i haven’t had a chance to do so. Would that fix happen to be in the working branch by any chance or should i stay on the dev branch?
-
@JGallo No the last release 1.5.5 doas not have the fixes. Will be in the next release to some in the next weeks I suppose. Nut sure when though. You definitely have the changes when you are on the
dev-branch. -
@Sebastian-Roth Fair enough. I will switch over to the dev-branch on nodes and fog server once we’re done with these projects. I should be able to do it prior to our winter break. Thank you again for your help on this.
-
@Sebastian-Roth So I went ahead and switched to dev-branch and upgrade nodes along with fog server. Seems like it’s working fine and the storage group info is now displayed. Thank you again for your help in this.
