Description of problem: test.neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity To run this test we should not use Cirros image. Before running the test we should verify which image is in use. If the test run with an unsupported image like Cirros it will fail with: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/neutron/tests/tempest/scenario/test_trunk.py", line 240, in test_subport_connectivity server['ssh_client'].exec_command(command) File "/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", line 36, in wrapper return function(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", line 92, in exec_command return self.ssh_client.exec_command(cmd) File "/usr/lib/python2.7/site-packages/tempest/lib/common/ssh.py", line 201, in exec_command stderr=err_data, stdout=out_data) tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; PATH=$PATH:/sbin; IFACE=$(ip l | grep "^[0-9]*: e" | cut -d \: -f 2) && sudo su -c "ip l a link $IFACE name $IFACE.10 type vlan id 10 && ip l s up dev $IFACE.10 && dhclient $IFACE.10"', exit status: 2, stderr: ip: RTNETLINK answers: Operation not supported Version-Release number of selected component (if applicable): osp-11 openstack-neutron-10.0.0-13.el7ost How reproducible: always Steps to Reproduce: 1. run the test with Cirros image 2. 3. Actual results: Expected results: Additional info: https://review.openstack.org/#/c/436756/8/neutron/tests/tempest/api/test_trunk.py@242
@Jakub, thoughts? Should the test intelligently skip if the VM cannot execute the VLAN subinterfaces command?
(In reply to Assaf Muller from comment #1) > @Jakub, thoughts? Should the test intelligently skip if the VM cannot > execute the VLAN subinterfaces command? I think we've already discussed this in a ML thread. The goal of tempest is to validate cloud is configured properly. If op has images that don't support VLAN interfaces then trunk feature won't work for him properly and op should be aware of that. The failure is legitimate and it should fail in case VMs are not able to talk to each other over subports.
Closing per comment 2. I agree with Jakub.
I am changing target here to Ocata (OSP11). OSP12 will get the fix through the regular RDO to OSP release pipeline.
Test was skipped when ran with cirros image. Ran 1 tests in 17.975s PASSED (id=0, skips=1)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3105