Loading...

XML

Word

Printable

Type: Bug
Resolution: Done-Errata
Priority: Major
Fix Version/s: 6.17.0
Affects Version/s: 6.16.0
Component/s: Provisioning Templates
Labels:

Satellite Team:

Rocket
Target Version:

6.17.0
Blocked:
False
Severity:
Important

Release Note Type:
Bug Fix
Release Note Text:

Hide
.Provisioning uses correct hostname for RHEL 9 hosts

Previously, when you provisioned RHEL 9 to a host, Satellite registered the host with the localhost entry as the hostname. This resulted in consequent failures to provision other RHEL 9 hosts.
The provisioning templates have been fixed to use the correct hostname.
As a result, provisioning RHEL 9 hosts works as expected.

Show
.Provisioning uses correct hostname for RHEL 9 hosts Previously, when you provisioned RHEL 9 to a host, Satellite registered the host with the localhost entry as the hostname. This resulted in consequent failures to provision other RHEL 9 hosts. The provisioning templates have been fixed to use the correct hostname. As a result, provisioning RHEL 9 hosts works as expected.
Release Note Status:
Done

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Test Coverage:

Automated
Preliminary Testing:
Pass

Market:

Description of problem:

Issues on sat6.16 when provisioning rhel9

How reproducible:

100% (you can check in the attached video)

Is this issue a regression from an earlier version:

Not sure.

Steps to Reproduce:

1. Enable and sync all the repos

2. Create the ak + hostgroup + subnet

3. Try the provisioning, using fdi for instance

Actual behavior:
one entry localhost.localdomain will get created, and the server will get registered on this entry (localhost.localdomain). You can also confirm that when executing "subscription-manager identity" on the new rhel9 content host

Also, whenever moving on to deploy a second one, it will fail, once there is already a localhost.localdomain registed on Satellite, and the installation will stop

Expected behavior:
Move on with the deploy/installation/registration with no problem, and use the correct FQDN during the registration, and not localhost.localdomain

Business Impact / Additional info:

is cloned by

SAT-31570 Issues on sat6.16 when provisioning rhel9