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

Hostname Change Bug 1.58

Scheduled Pinned Locked Moved Solved
Bug Reports
3
5
453
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.
  • Z
    zuchowra
    last edited by Jul 27, 2020, 2:42 PM

    Bug in Version 1.58 .

    If you have host name change set to off globally and re enable, it doesn’t refresh all the hosts. You have to go to each host manually and uncheck host name change if checked, hit save, than check it off again and hit save.

    Second Work Around

    Have hosts in a group, go to services, uncheck hostname change, hit save, recheck hostname change, hit save.

    Ray

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jul 27, 2020, 3:04 PM

      This is not a bug. This is intended behavior.

      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

      Z 1 Reply Last reply Jul 28, 2020, 6:29 PM Reply Quote 1
      • G
        george1421 Moderator
        last edited by Jul 27, 2020, 3:06 PM

        I’m going to say that’s not a bug but a feature. I can understand why the developers would set it up this way. If the feature is off (globally) and you turn it on, there is a risk that every host could be renamed and rebooted unexpectedly. From a safety standpoint I can understand why you would be required to go in and touch each host definition before the name change happened.

        But just in case this is not an expected behavior I’m going to move this post to the Bugs forum and then let the Developers tell us yes or no.

        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!

        1 Reply Last reply Reply Quote 0
        • Z
          zuchowra @Tom Elliott
          last edited by Jul 28, 2020, 6:29 PM

          @Tom-Elliott alright no worries. I thought it was a bug. Thanks for the quick response.

          Ray

          1 Reply Last reply Reply Quote 0
          • G
            george1421 Moderator
            last edited by Jul 28, 2020, 6:44 PM

            Mod Note: Solving and closing this thread

            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!

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              4/5
              Last post

            212

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project