tempest test_preserve_preexisting_port fails, "Unrecognized attribute(s) 'dns_name'"

Bug #1574565 reported by Hiroyuki Ito
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Matt Riedemann
networking-midonet
Invalid
Critical
Hiroyuki Ito

Bug Description

tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_preserve_preexisting_port failed like the following error:

http://logs.openstack.org/43/306343/4/check/gate-tempest-dsvm-networking-midonet-v2/193b941/

Traceback (most recent call last):
      File "tempest/test.py", line 113, in wrapper
         return f(self, *func_args, **func_kwargs)
       File "tempest/scenario/test_network_basic_ops.py", line 662, in test_preserve_preexisting_port
         self.assertEqual('', port['device_id'])
       File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in assertEqual
         self.assertThat(observed, matcher, message)
       File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 493, in assertThat
         raise mismatch_error
     testtools.matchers._impl.MismatchError: '' != u'260b6313-90e9-47f7-90b8-74f4a75877ab'

I wonder if the following neutron server error is related and it is related to the current nova change(*):

2016-04-25 07:29:01.069 21424 INFO neutron.api.v2.resource [req-408f3e48-a219-4748-908c-7eeeb28d932c neutron -] update failed (client error): Unrecognized attribute(s) 'dns_name'
2016-04-25 07:29:01.070 21424 INFO neutron.wsgi [req-408f3e48-a219-4748-908c-7eeeb28d932c neutron -] 127.0.0.1 - - [25/Apr/2016 07:29:01] "PUT /v2.0/ports/6476e377-74a4-4872-8a7f-f792b3420794.json HTTP/1.1" 400 332 0.003440

(*) change-id: I65edb33b955a91d1701fc91cb9fae0a5f26d4e46

Changed in networking-midonet:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 2.0.0
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i added nova to the bug because it looks like a nova bug.
ie. missing "constants.DNS_INTEGRATION in self.extensions" check.

Changed in networking-midonet:
assignee: nobody → Hiroyuki Ito (ito-hiroyuki-01)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to networking-midonet (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/310347

Revision history for this message
Matt Riedemann (mriedem) wrote : Re: tempest test_preserve_preexisting_port fails
Changed in nova:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Matt Riedemann (mriedem) wrote :

I'll push a fix for nova. This is why random attributes in unversioned dictionaries being passed between nova and neutron are bad, especially when using optional extensions in Neutron also.

summary: - tempest test_preserve_preexisting_port fails
+ tempest test_preserve_preexisting_port fails, "Unrecognized attribute(s)
+ 'dns_name'"
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
assignee: nobody → Matt Riedemann (mriedem)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/310474
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b256cae8e204fbbf6f3d40f5f4d47013be018a6d
Submitter: Jenkins
Branch: master

commit b256cae8e204fbbf6f3d40f5f4d47013be018a6d
Author: Matt Riedemann <email address hidden>
Date: Wed Apr 27 09:47:59 2016 -0400

    Only reset dns_name when unbinding port if DNS is integrated

    We only set the dns_name on the port if the "DNS Integration"
    extension is enabled, so we should only reset it on the port
    when unbinding if the extension is enabled, otherwise some
    Neutron stadium plugins will fail since they don't expect
    the 'dns_name' attribute to be on the port.

    Change-Id: I7451fbfad53236e9e147a0387dac45ae97f3e75b
    Closes-Bug: #1574565

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-midonet (master)

Change abandoned by Hiroyuki Ito (<email address hidden>) on branch: master
Review: https://review.openstack.org/310347

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/312312

Changed in networking-midonet:
status: Confirmed → Invalid
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/nova 14.0.0.0b1

This issue was fixed in the openstack/nova 14.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/mitaka)

Reviewed: https://review.openstack.org/312312
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=00dd02f28f83121ff0ec409f338a0c75bec5c03c
Submitter: Jenkins
Branch: stable/mitaka

commit 00dd02f28f83121ff0ec409f338a0c75bec5c03c
Author: Matt Riedemann <email address hidden>
Date: Wed Apr 27 09:47:59 2016 -0400

    Only reset dns_name when unbinding port if DNS is integrated

    We only set the dns_name on the port if the "DNS Integration"
    extension is enabled, so we should only reset it on the port
    when unbinding if the extension is enabled, otherwise some
    Neutron stadium plugins will fail since they don't expect
    the 'dns_name' attribute to be on the port.

    NOTE(mriedem): This backport adds an import that wasn't in
    stable/mitaka but is used in the unit test from the original
    patch.

    Change-Id: I7451fbfad53236e9e147a0387dac45ae97f3e75b
    Closes-Bug: #1574565
    (cherry picked from commit b256cae8e204fbbf6f3d40f5f4d47013be018a6d)

tags: added: in-stable-mitaka
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/nova 13.1.0

This issue was fixed in the openstack/nova 13.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.