Comment 8 for bug 1607412

@Anton,

Looking at the Neutron server screen you posted above, I can see that the DNS extension has not been configured in Neutron (please look at the list of ML2 extensions in parameter ml2_extension_drivers: http://logs.openstack.org/62/324262/3/gate/gate-grenade-dsvm-neutron-multinode/9af98c8/logs/new/screen-q-svc.txt.gz#_2016-07-25_10_18_54_680

Contrast that with what I have in my development system, where the DNS extension is configured:

2016-07-28 21:37:42.199 ^[[00;32mDEBUG oslo_service.service [^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mml2.extension_drivers = ['port_security', 'dns']^[[00m ^[[00;33mfrom (pid=20513) log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2573^[[00m

So when the request gets to Neutron, the controller for ports verifies that all the attributes in the request body are supported: https://github.com/openstack/neutron/blob/master/neutron/api/v2/base.py#L673. This calls the attributes.verify_attributes method that you point to above and we get the exception because, since the DNS extension is not loaded, the dns_name attribute is not supported.

I can also see the request from Nova to get the extensions loaded in Neutron:

http://logs.openstack.org/62/324262/3/gate/gate-grenade-dsvm-neutron-multinode/9af98c8/logs/new/screen-q-svc.txt.gz#_2016-07-25_10_23_35_494

I cannot see the response from Neutron in this log, but this is tempest code, so there must be a tempest log somewhere. That is where we should look at next, to see the response sent back from Neutron