TestNetworkAdvancedServerOps is trying to use floating IPs for ssh even though ssh_connect_method = fixed

[Matt Riedemann]

tempest.conf:

http://logs.openstack.org/85/235485/6/check/gate-tempest-dsvm-neutron-full/2289378//logs/tempest_conf.txt.gz

Results:

http://logs.openstack.org/85/235485/6/check/gate-tempest-dsvm-neutron-full/2289378/logs/testr_results.html.gz

For example:

tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedServerOps.test_server_connectivity_pause_unpause

File "tempest/scenario/manager.py", line 782, in create_floating_ip

That should not be trying to use floating IPs.

This is for a change that's testing cells + neutron config for a gate job:

https://review.openstack.org/#/c/235485/

[Matt Riedemann (mriedem)]

Hmm, I just saw:

tenant_networks_reachable = false

    cfg.BoolOpt('tenant_networks_reachable',
                default=False,
                help="Whether tenant networks can be reached directly from "
                     "the test client. This must be set to True when the "
                     "'fixed' ssh_connect_method is selected."),

So we don't have that configured properly. The ssh_connect_method option help should call this out probably.

[Matt Riedemann (mriedem)]

However, test_network_advanced_server_ops still blindly tries to use floating IPs:

        floating_ip = self.create_floating_ip(server, public_network_id)
        # Verify that we can indeed connect to the server before we mess with
        # it's state
        self._wait_server_status_and_check_network_connectivity(
            server, keypair, floating_ip)

So we should still skip this test if ssh_connect_method != 'floating'.

[OpenStack Infra (hudson-openstack)]

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

[Matt Riedemann (mriedem)]

Here are more that rely on floating IPs:

tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_cross_tenant_traffic [95.516466s] ... FAILED

tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops [22.756673s] ... FAILED

tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os

[OpenStack Infra (hudson-openstack)]

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

[Matt Riedemann (mriedem)]

tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_cross_tenant_traffic [95.516466s] ... FAILED

2015-11-06 21:56:06.141 | File "tempest/scenario/test_security_groups_basic_ops.py", line 448, in test_cross_tenant_traffic
2015-11-06 21:56:06.141 | self._deploy_tenant(self.alt_tenant)
2015-11-06 21:56:06.141 | File "tempest/scenario/test_security_groups_basic_ops.py", line 319, in _deploy_tenant
2015-11-06 21:56:06.141 | self._set_access_point(tenant)
2015-11-06 21:56:06.141 | File "tempest/scenario/test_security_groups_basic_ops.py", line 282, in _set_access_point
2015-11-06 21:56:06.141 | self._assign_floating_ips(tenant, server)
2015-11-06 21:56:06.141 | File "tempest/scenario/test_security_groups_basic_ops.py", line 288, in _assign_floating_ips
2015-11-06 21:56:06.142 | client=tenant.manager.network_client)
2015-11-06 21:56:06.142 | File "tempest/scenario/manager.py", line 782, in create_floating_ip

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/242708
Reason: Need to handle this differently.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/242707
Reason: Need to handle this differently.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matt Riedemann (<email address hidden>) on branch: master
Review: https://review.openstack.org/242705
Reason: Need to handle this differently.

[Castulo J. Martinez (castulo-martinez)]

@Matt Riedemann, are you still working on this fix?

[Matt Riedemann (mriedem)]

No, the patch was abandoned and wasn't the correct approach, we need to add a feature flag to tempest to tell tempest if floating IPs are supported in the deployment, which really makes this a duplicate of bug 1603492 so I'll mark it as such.