• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Overflow imaging from storage node that's not a master in a storage group

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    21
    3.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JGallo
      last edited by JGallo

      @p4cm4n Both Master node and slave node in a storage group are storage node installs. The master node is the “master” for that particular storage group. Replication is not an issue getting image to slave. I’m having issues getting clients to pull from the slave once master node slots become unavailable.

      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
      • Wayne WorkmanW
        Wayne Workman @JGallo
        last edited by

        @JGallo I took a look at my home server and I see what you’re saying. Go to the existing location, and set the ‘node’ field to ‘please select an option’ aka blank. Leave the storage group as it is. See if that works.

        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/

        1 Reply Last reply Reply Quote 0
        • J
          JGallo
          last edited by

          @Wayne-Workman Thank you. I will try tomorrow and observe when we deploy another image to a lab that we have scheduled. We have a three day weekend so my apologizes for late response.

          1 Reply Last reply Reply Quote 0
          • J
            JGallo
            last edited by

            @Wayne-Workman Interesting bug I think may exist. So I went into the location plug in and set the ‘node’ field to exactly what you said ‘please select an option’ and hit update then going to the location management page I no longer see a storage group set for the location. The strange thing is that going into the location it does show a storage group defined. It’s just when I go to the location management page that it doesn’t show. So by setting the ‘node’ field to blank, it appears that no storage group is defined at least according to the main menu of the location plug in.

            Here is what it looks like. Hopefully you understand what I’m trying to describe.

            0_1542124667060_location plug in.PNG

            1 Reply Last reply Reply Quote 0
            • Wayne WorkmanW
              Wayne Workman
              last edited by

              @moderators @testers @developers can anyone confirm that the location plugin should/does support a storage group serving a location? As opposed to an individual storage node serving a location.

              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/

              Tom ElliottT 1 Reply Last reply Reply Quote 0
              • Tom ElliottT
                Tom Elliott @Wayne Workman
                last edited by

                @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

                Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                • Wayne WorkmanW
                  Wayne Workman @Tom Elliott
                  last edited by

                  @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/

                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                  • J
                    JGallo
                    last edited by

                    @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.

                    1 Reply Last reply Reply Quote 2
                    • Tom ElliottT
                      Tom Elliott @Wayne Workman
                      last edited by

                      @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.

                      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

                      1 Reply Last reply Reply Quote 0
                      • J
                        JGallo
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 1
                        • S
                          Sebastian Roth Moderator
                          last edited by

                          @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.

                          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

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            JGallo @Sebastian Roth
                            last edited by

                            @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?

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sebastian Roth Moderator
                              last edited by

                              @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.

                              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

                              J 2 Replies Last reply Reply Quote 1
                              • J
                                JGallo @Sebastian Roth
                                last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • J
                                  JGallo @Sebastian Roth
                                  last edited by

                                  @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.

                                  1 Reply Last reply Reply Quote 1
                                  • 1
                                  • 2
                                  • 1 / 2
                                  • First post
                                    Last post

                                  196

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project