[Rdo-list] Overcloud nodes host-name persistence

[Marius Cornea]

Nice catch, I was able to reproduce it on my system and reported it here:
https://bugzilla.redhat.com/show_bug.cgi?id=1272376

----- Original Message -----
> From: "AliReza Taleghani" <shayne.alone at gmail.com>
> To: rdo-list at redhat.com
> Sent: Friday, October 16, 2015 9:22:53 AM
> Subject: Re: [Rdo-list] Overcloud nodes host-name persistence
> 
> if you update hostname via hostnamectl and restart nova-compute service
> without reboot it works! but rebooting will cause new hostname is place :-/
> 
> Sincerely,
> Ali R. Taleghani
> @linkedIn
> 
> On Fri, Oct 16, 2015 at 10:49 AM, AliReza Taleghani < shayne.alone at gmail.com
> > wrote:
> 
> 
> 
> It seem that If you restart bare metal servers! there will be a problem after
> boot that the node will be register it self with a different name rather
> than the one used on deployment!
> 
> 
> as the attachment shown the failed compute node is registered with new name:
> => overcloud-novacompute-2.localdomain
> as it was
> => overcloud-novacompute-2
> during deployment!
> 
> I check:
> ```
> [heat-admin at overcloud-novacompute-2 ~]$ sudo hostnamectl set-hostname
> --transient overcloud-novacompute-2
> [heat-admin at overcloud-novacompute-2 ~]$ sudo hostnamectl set-hostname
> overcloud-novacompute-2
> ````
> but after reboot the server again append localdomain to iit's hostname
> 
> Sincerely,
> Ali R. Taleghani
> @linkedIn
> 
> 
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
> 
> To unsubscribe: rdo-list-unsubscribe at redhat.com