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

Steps/Requirements to Update FOG 1.5.4 to 1.5.6

Scheduled Pinned Locked Moved Solved
FOG Problems
3
11
1.1k
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.
  • S
    Sebastian Roth Moderator
    last edited by May 31, 2019, 8:30 PM

    @UWPVIOLATOR I would recommend you wait a couple of days as we prepare för 1.5.7 release with important fixes.

    Please read the update notes for 1.5.5 before you go ahead!!!

    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
    • S
      Sebastian Roth Moderator
      last edited by May 31, 2019, 8:34 PM

      Forgot to post the link… https://news.fogproject.org/fog-1-5-5-officially-released/

      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
      • U
        UWPVIOLATOR
        last edited by May 31, 2019, 10:37 PM

        @Sebastian-Roth Thank you for that we will do that when updating to 1.5.6, but for future upgrades is it best practice to update nodes then update master? If we miss a node (we have 12-15) will that break the master node in any way? Also if we update nodes and then don’t update the master will that break things? What happens if we update the master but not the nodes. Say we go to 1.5.63 then 1.5.7 comes out. If we don’t go back and then update all of them right way that ok but I would assume you would want them to be updated eventually correct?

        T 1 Reply Last reply Jun 1, 2019, 12:39 AM Reply Quote 0
        • T
          Tom Elliott @UWPVIOLATOR
          last edited by Jun 1, 2019, 12:39 AM

          @UWPVIOLATOR once all nodes are at 1.5.5 I don’t imagine there being an issue with updating nodes as needed. 1.5.5 the logic for replication changed quite a lot which is why we highly suggest making sure all nodes are at least st this level first.

          Mind you reasoning:

          1. Logic checks occur at the nodes themselves, so 1.5.5 modified how these checks operated.

          2. Master checks changed and need the information returned in such a way that only 1.5.5 did properly.

          I’m sure there’s more but this is more to just illustrate the point more directly as to the “why”

          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
          • U
            UWPVIOLATOR
            last edited by Jun 5, 2019, 7:35 PM

            @Sebastian-Roth @Tom-Elliott We planed a maintenance window tomorrow morning to update our FOG. We were going to update storage nodes today but when we update the nodes from 1.5.4 to 1.5.6 in the FOG GUI we no longer see them connected. 072Cache was updated to 1.5.6 and we updated the username in GUI to fogproject and verified the password. Is this normal until we update the master node to 1.5.6?

            92a4ef5a-33db-48a5-a7c1-c9714c5da561-image.png

            U 1 Reply Last reply Jun 5, 2019, 8:24 PM Reply Quote 0
            • U
              UWPVIOLATOR @UWPVIOLATOR
              last edited by Jun 5, 2019, 8:24 PM

              I tested that node and it still deploys image so my guess is its a glitch in the GUI until we update the master node.

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Jun 5, 2019, 8:38 PM

                @UWPVIOLATOR You better shut down the replication services NOW - systemctl stop FOGImageReplicator; systemctl stop FOGSnapinReplicator on your master node.

                Read the important notice here: https://news.fogproject.org/fog-1-5-5-officially-released/

                We can sort out the rest tomorrow.

                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

                U 1 Reply Last reply Jun 5, 2019, 11:43 PM Reply Quote 0
                • U
                  UWPVIOLATOR @Sebastian Roth
                  last edited by Jun 5, 2019, 11:43 PM

                  @Sebastian-Roth Yes I had already had it disabled.

                  1 Reply Last reply Reply Quote 1
                  • S
                    Sebastian Roth Moderator
                    last edited by Sebastian Roth Jun 5, 2019, 10:43 PM Jun 6, 2019, 4:43 AM

                    @UWPVIOLATOR said in Steps/Requirements to Update FOG 1.5.4 to 1.5.6:

                    072Cache was updated to 1.5.6 and we updated the username in GUI to fogproject and verified the password. Is this normal until we update the master node to 1.5.6?

                    No, unfortunately this is a bug in 1.5.6 and we are working on releasing 1.5.7 soon to fix that. Manually adjusting the username works för you just aß well. Beside the Storage Node settings you need to fix the username in FOG Configuration -> FOG Settings as well.

                    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
                    • U
                      UWPVIOLATOR
                      last edited by Jun 7, 2019, 6:15 PM

                      So this can get marked as resolved. Everything worked as expected except when you update the nodes the GUI did not show the new version until after we updated the Master. All the issues we had with 1.5.4 were resolved with 1.5.6. Very happy with this update.

                      GUI is super fast!
                      The freezing on formating MBR/GPT on start of imaging is back to only a few seconds. Replication seems to be acting normal again.

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

                      202

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project