Bug 1655627

Summary: Updating to cloud-init to 18.2-1.el7_6.1.x86_64 causes the set_hostname routine to trigger.
Product: Red Hat Enterprise Linux 7 Reporter: Siggy Sigwald <ssigwald>
Component: cloud-initAssignee: Eduardo Otubo <eterrell>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Vratislav Hutsky <vhutsky>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.6CC: akaris, eterrell, huzhao, jgreguske, mkalinin, pveiga, rochen, william.temple, xiaoxwan, yacao, yujiang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 22:49:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Siggy Sigwald 2018-12-03 15:26:55 UTC 
Description of problem:
Customer had a system with RHEL 7.4.  upgraded to 7.6 and rebooted.  Customer received the unexpected hostname change at that time. Customer downgraded the cloud-init package to 0.7.9 and rebooted.  Customer try to re-upgrade to 18.2 to reproduce the issue.  After updating cloud-init for the second time the the issue is not observed. Behavior only occurs after rebooting system as part of RHEL 7.4 to 7.7 upgrade.

How reproducible:
Every time

Steps to Reproduce:
1. Upgrade OS from RHEL 7.4 to RHEL 7.6 on RHOSP10
2. Reboot the node.

Actual results:
Hostname changes.

Expected results:
hostname does not change.
Comment 2 William Temple 2019-01-07 14:34:22 UTC 
Hi, 

   Just checking if there is an update which addresses this issue.  We patch thousands of systems routinely, so extra cautions need to be taken to avoid the problem.

Thanks,
Bill