← Back to team overview

yahoo-eng-team team mailing list archive

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

 

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
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):
  Expired

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



References