yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2111332] [NEW] Neutron DNS integration ignores and resets dns_name when using pre-created port to create instance

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Robert van Leeuwen <2111332@xxxxxxxxxxxxxxxxxx>
Date: Tue, 20 May 2025 13:00:44 -0000
Reply-to: Bug 2111332 <2111332@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Pre-created neutron ports with a custom dns_name gets overwritten when the instance is created with the port-id.
(using the neutron dns integration with designate)

How to re-create:
Create a port with custom dns_name:
openstack port create --network abc myport --dns-name fancy-dns-name

Port is now created with the right DNS name:
openstack port show $PORT
dns_assignment          | fqdn='fancy-dns-name.my-domain.'


Now we create the VM with that port-id:
openstack server create --image cirros --flavor testflavor mytestvm --nic port-id=$PORT

After creation of the server the port no longer has the custom dns-name that was set on the port but rather the name of the server that was created. e.g.
openstack port show $PORT
dns_assignment          | fqdn='mytestvm.my-domain.'

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2111332

Title:
  Neutron DNS integration ignores and resets dns_name when using pre-
  created port to create instance

Status in OpenStack Compute (nova):
  New

Bug description:
  Pre-created neutron ports with a custom dns_name gets overwritten when the instance is created with the port-id.
  (using the neutron dns integration with designate)

  How to re-create:
  Create a port with custom dns_name:
  openstack port create --network abc myport --dns-name fancy-dns-name

  Port is now created with the right DNS name:
  openstack port show $PORT
  dns_assignment          | fqdn='fancy-dns-name.my-domain.'

  
  Now we create the VM with that port-id:
  openstack server create --image cirros --flavor testflavor mytestvm --nic port-id=$PORT

  After creation of the server the port no longer has the custom dns-name that was set on the port but rather the name of the server that was created. e.g.
  openstack port show $PORT
  dns_assignment          | fqdn='mytestvm.my-domain.'

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2111332/+subscriptions