Bug 1806020

Summary: [baremetal] NetworkManager does not always set hostname
Product: OpenShift Container Platform Reporter: Brad P. Crochet <brad>
Component: Machine Config OperatorAssignee: Brad P. Crochet <brad>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mnguyen, wsun
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1806008 Environment:
Last Closed: 2020-03-10 23:54:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1806001, 1806008    
Bug Blocks:    

Description Brad P. Crochet 2020-02-21 20:14:46 UTC
+++ This bug was initially created as a clone of Bug #1806008 +++

+++ This bug was initially created as a clone of Bug #1806001 +++

NetworkManager doesn't always set the hostname when DHCP6 is involved.
This sets the hostname when $DHCP6_FQDN_FQDN is populated and does not
equal localhost.localdomain. This is a workaround while we try to figure
out why NetworkManager is not setting the hostname as it should.

Comment 6 errata-xmlrpc 2020-03-10 23:54:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.