Updating a port without dns_name parameter clears dns_name when dns-integration is enabled

[James Anziano]

If the dns-integration extension is enabled, updating a port without explicitly specifying a dns_name parameter will clear the dns_name field.

To reproduce:
Make sure your environment is configured to use the dns-integration extension.
Have a port with a dns_name already set.
Run neutron port-update my-port --name=my-new-port
The command should complete successfully, but if you now run neutron port-show my-new-port, you will see the dns_name field is empty in addition to any other changes you requested.

DevStack all-in-one built from master
Perceived severity: medium

[Miguel Lavalle (minsel)]

Confirmed. I am able to reproduce as indicated

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/289551

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/289551
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=58e9102bff7280b36bcd24a55b7403d13ce68041
Submitter: Jenkins
Branch: master

commit 58e9102bff7280b36bcd24a55b7403d13ce68041
Author: James Anziano <email address hidden>
Date: Mon Mar 7 19:42:47 2016 +0000

    Only clear dns_name when user specifies parameter

    Previously dns_name would be set to empty string as long as the
    dns-integration extension was enabled and the user didn't specify a
    different value. This meant that dns_name would be cleared even if the
    user didn't pass it as a parameter at all. This patch only clears
    dns_name if the user passed that parameter without specifying a value.

    Change-Id: I1be9a2f9c3dc9850cc167b204506e36d5272d642
    Closes-Bug: 1554153

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/neutron 8.0.0.0rc1 release candidate.