Open Stack

On Wed, 2020-01-29 at 16:44 +0200, Volodymyr Litovka wrote:
> Dear colleagues,
> 
> I'm using DNS Integration and just faced an issue - after renaming
> instance, I can't bind port to the instance using new name:
> 
> 1) I've created intances with name 'devel'
> 2) then I renamed it to devel ((openstack server set --name packager devel)
> 3) when binding port with dns_name using new name ('packager' in my
> case), the following error appear:
> ERROR nova.api.openstack.wsgi PortNotUsableDNS: Port
> c3a92cf6-b49b-4570-b69b-0c23af1d1f94 not usable for instance
> 6aa78bd5-099e-4878-a5ac-90262505a924. Value packager assigned to
> dns_name attribute does not match instance's hostname devel
> 
> and yes, record in DB still uses an old hostname:
> 
> mysql> select display_name from instances where hostname='devel';
> +--------------+
> > display_name |
> 
> +--------------+
> > packager     |
> 
> +--------------+
> 1 row in set (0.00 sec)
> 
> 
> and hostname remains the same (initial) regardless of any changes to
> display_name.
> 
> I'm on Rocky. Is it bug or feature and are there ways to work around this?
i think you should be able to change the display name but i would not expect that display name to change
the host name used by the guest. it is likely a bug that the portbinding appears to be using the displayname
for designate integration. i know we use the display name as the hostname for the vm by default but
i would not expect openstack server set --name packager devel to alter the hostname served to the vm over dhcp
once the vm is intially created. i would expect to be able to alther that via designate and for the display name to be
independt of the host name after the inital boot.

so yes there is likely a bug in that we are using the disply name somewhere we shoudl not be.
> 
> Thank you.
> 
> --
> Volodymyr Litovka
>    "Vision without Execution is Hallucination." -- Thomas Edison
>