Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-39469

When provisioning rhel9+ via fdi using static network information, localhost.localdomain will be created on Satellite webUI

XMLWordPrintable

    • Bug Fix
    • Hide
      Before this update, static network information provisioning created a localhost.localdomain entry due to a missing hostname update during RHEL9 provisioning with static network information. This resulted in an unnecessary localhost.localdomain entry for the end user. With this release, the hostname is now set to a static value before the Rhsm call, fixing the localhost.localdomain creation issue. As a result, stably setting the hostname before the Rhsm call prevents localhost.localdomain creation, improving provisioning consistency.
      Show
      Before this update, static network information provisioning created a localhost.localdomain entry due to a missing hostname update during RHEL9 provisioning with static network information. This resulted in an unnecessary localhost.localdomain entry for the end user. With this release, the hostname is now set to a static value before the Rhsm call, fixing the localhost.localdomain creation issue. As a result, stably setting the hostname before the Rhsm call prevents localhost.localdomain creation, improving provisioning consistency.
    • Proposed
    • To Do

      Description of problem:

      When provisioning rhel9+ via fdi using static network information, localhost.localdomain will be created on Satellite webUI

       

      We got a similar issue long ago, and it was already fixed, the main difference here is that, before, we were using the DHCP, and now, it's static.

       

      How reproducible:

      100%

       

      Is this issue a regression from an earlier version:

      no

       

      Steps to Reproduce:

      1. Setup satellite for provisioning (rhel9)

      2. FDI, using static network information

      3. Start the provisioning of rhel9

      Actual behavior:
      Initially, the content host will be created on Satellite, and once the VM reaches the rhsm call, a new entry will be created on satellite, called localhost.localdomain

       

      Expected behavior:
      The same content host entry should be used. During the rhsm call, the Content Host should already know the hostname, which is not the case.

       

      Business Impact / Additional info:

       

          1.
          		 [QE] automation for set FDI name Sub-task In Progress Undefined Amol Patil
          2.
          		 [QE testing] When provisioning rhel9+ via fdi using static network information, localhost.localdomain will be created on Satellite webUI Sub-task Closed Undefined Amol Patil

              rhn-engineering-sshtein Shimon Shtein
              rhn-support-wpinheir Waldirio Pinheiro
              Amol Patil Amol Patil
              Jan Fiala Jan Fiala
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: