test_device_tagging compute tempest tests failing in master network component line

Bug #1969669 reported by Rafael Castillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

Affecting periodic-tripleo-ci-centos-9-standalone-full-tempest-api-network-master

Failing tests
tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest.test_tagged_attachment[id-3e41c782-2a89-4922-a9d2-9a188c4e7c7c,image,network,volume]
tempest.api.compute.servers.test_device_tagging.TaggedBootDevicesTest.test_tagged_boot_devices[id-a2e65a6c-66f1-4442-aaa8-498c31778d96,image,network,slow,volume]
tempest.api.compute.servers.test_device_tagging.TaggedBootDevicesTest_v242.test_tagged_boot_devices[id-a2e65a6c-66f1-4442-aaa8-498c31778d96,image,network,slow,volume]

Example runs:
https://logserver.rdoproject.org/26/41926/5/check/periodic-tripleo-ci-centos-9-standalone-full-tempest-api-network-master/57ede6e/logs/undercloud/var/log/tempest/failing_tests.log.txt.gz
https://logserver.rdoproject.org/openstack-component-network/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-standalone-full-tempest-api-network-master/dde51e1/logs/undercloud/var/log/tempest/failing_tests.log.txt.gz

summary: - test_device_tagging compute tempest tests failing in network component
- line
+ test_device_tagging compute tempest tests failing in master network
+ component line
Revision history for this message
yatin (yatinkarel) wrote :

Looks duplicate of https://bugs.launchpad.net/tripleo/+bug/1968732. Although the jobs are master based and have config-drive enabled by mistake as per the other bug, all failing tests specifically calling metadata proxy and thus failing.

Also similar wallaby jobs should also be hitting same failes or even extra failure then this as there config-drive is not enabled.

Revision history for this message
yatin (yatinkarel) wrote :

I Checked again considering consistent failures(shouldn't have been that consistent if same other issue). And found it's due to https://review.opendev.org/c/openstack/neutron/+/833015 which needs pyroute>=0.6.6 but current promoted containers still have 0.6.5.

RDO zed already have 0.6.9 as upper-constraints https://review.rdoproject.org/r/c/rdoinfo/+/42155. So to clear this issue in component pipelines, just need a new promotion so containers have pyroute2-0.6.9.

Revision history for this message
yatin (yatinkarel) wrote :

Ok there is similar bug[1] exists but for different job, so any one of these can be closed as duplicate. Promotion should clear all similar issues in network component promotion pipeline.

[1] https://bugs.launchpad.net/tripleo/+bug/1969985

Revision history for this message
Douglas Viroel (dviroel) wrote :

Last run after master proomtion[1] is green, failed jobs are now passing.
pyroute was also update here https://review.rdoproject.org/r/c/rdoinfo/+/42155

[1] https://logserver.rdoproject.org/76/36976/35/check/periodic-tripleo-ci-centos-9-standalone-full-tempest-api-network-master/809da51/logs/undercloud/var/log/tempest/stestr_results.html.gz

Closing this one and abandoning skiplist patch.

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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