test_server_security_groups fails because instance not found as device id

[Lance Bragstad]

When running tempest against a controller and dedicated compute node, I consistently fail these two tests:

 - tempest.api.compute.security_groups.test_security_groups.SecurityGroupsTestJSON.test_server_security_groups[gate]
  - tempest.api.compute.security_groups.test_security_groups.SecurityGroupsTestXML.test_server_security_groups[gate]

failing because of

Traceback (most recent call last):
  File "/tmp/tempest/tempest/tempest/api/compute/security_groups/test_security_groups.py", line 128, in test_server_security_groups
    sg_name)
  File "/tmp/tempest/tempest/tempest/services/compute/xml/servers_client.py", line 511, in add_security_group
    return self.action(server_id, 'addSecurityGroup', None, name=name)
  File "/tmp/tempest/tempest/tempest/services/compute/xml/servers_client.py", line 421, in action
    str(doc), self.headers)
  File "/tmp/tempest/tempest/tempest/common/rest_client.py", line 154, in post
    return self.request('POST', url, headers, body)
  File "/tmp/tempest/tempest/tempest/common/rest_client.py", line 289, in request
    resp, resp_body)
  File "/tmp/tempest/tempest/tempest/common/rest_client.py", line 333, in _error_checker
    raise exceptions.NotFound(resp_body)
NotFound: Object not found
Details: <itemNotFound code="404" xmlns="http://docs.openstack.org/compute/api/v1.1"><message>instance_id 7991301c-7042-4a9f-a69a-aea934ca0113 could not be found as device id on any ports</message></itemNotFound>

this is the test case: https://github.com/openstack/tempest/blob/master/tempest/api/compute/security_groups/test_security_groups.py#L127

In the nova.conf I have security_group_api = neutron which means we are using neutron to try and do all this.. faliing here:
https://github.com/openstack/nova/blob/master/nova/network/security_group/neutron_driver.py#L415

because we hit this: https://github.com/openstack/nova/blob/master/nova/network/security_group/openstack_driver.py#L38

More trace info here: http://paste.openstack.org/show/65187/

I've got the controller configured with neutron ml2 as the plugin.

[Matt Riedemann (mriedem)]

Neutron ML2 is the plugin but what's the mechanism driver? OVS? LinuxBridge?

[Yang Yu (yuyangbj)]

Echo comment #1, what's your mechanism driver? If your controller is using OVS and compute node is using LinuxBridge, you should configure /etc/neutron/plugins/ml2/ml2_conf.ini as below.
mechanism_drivers = linuxbridge,openvswitch

[Lance Bragstad (lbragstad)]

My /etc/neutron/plugins/ml2/ml2_conf.ini shows mechanism_drivers = linuxbridge, openvswitch, which is on my control node.

[David Kranz (david-kranz)]

Can you do what this test is doing manually? I am skeptical that this is a bug in tempest. More likely a configuration issue.

[Launchpad Janitor (janitor)]

[Expired for tempest because there has been no activity for 60 days.]

[Martin Gerhard Loschwitz (martin-loschwitz)]

We're running into this as well.