[Rdo-list] Overcloud nodes host-name persistence

AliReza Taleghani shayne.alone at gmail.com
Fri Oct 16 07:22:53 UTC 2015


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 <http://ir.linkedin.com/in/taleghani>

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 <http://ir.linkedin.com/in/taleghani>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rdo-list/attachments/20151016/5f631b1e/attachment.htm>


More information about the rdo-list mailing list