Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1722034

Summary: Tempest test cases and scenarios failed with multiple Availability Zones
Product: Red Hat OpenStack Reporter: Martin Kopec <mkopec>
Component: openstack-tempestAssignee: Chandan Kumar <chkumar>
Status: CLOSED ERRATA QA Contact: Martin Kopec <mkopec>
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: apevec, chkumar, knoha, lhh, mkopec, slinaber, udesale
Target Milestone: rcKeywords: Triaged
Target Release: 15.0 (Stein)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tempest-20.0.0-0.20190703110412.a955095.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1722027 Environment:
Last Closed: 2019-09-21 11:23:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1693488, 1722027    
Bug Blocks:    
Attachments:
Description Flags
verification output none

Description Martin Kopec 2019-06-19 12:04:15 UTC
+++ This bug was initially created as a clone of Bug #1722027 +++

+++ This bug was initially created as a clone of Bug #1693488 +++

Description of problem:
Tempest test cases and scenarios failed with multiple Availability Zones
For example, cinder has an availability zone, which is called az1 and nova doesn't have an availability zone that it means None.
Following test cases failed.
~~~
{0} tempest.api.compute.admin.test_live_migration.LiveAutoBlockMigrationV225Test.test_volume_backed_live_migration ... FAILED
{0} tempest.api.compute.admin.test_live_migration.LiveMigrationRemoteConsolesV26Test.test_volume_backed_live_migration ... FAILED
{0} tempest.api.compute.admin.test_live_migration.LiveMigrationTest.test_volume_backed_live_migration ... FAILED
{0} setUpClass (tempest.api.compute.servers.test_create_server.ServersTestBootFromVolume) ... FAILED
{0} tempest.api.compute.servers.test_device_tagging.DeviceTaggingTest.test_device_tagging ... FAILED
{0} tempest.api.compute.servers.test_device_tagging.DeviceTaggingTestV2_42.test_device_tagging ... FAILED
{0} tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_resize_volume_backed_server_confirm ... FAILED
{0} tempest.scenario.test_shelve_instance.TestShelveInstance.test_shelve_volume_backed_instance ... FAILED
{0} tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_create_ebs_image_and_check_boot ... FAILED
{0} tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern ... FAILED
~~~

To avoid this situation, we should introduce an option to assign the availability zone for nova instance and cinder volume.

This topic
Version-Release number of selected component (if applicable):
RHOSP13.

How reproducible:
Always.

Steps to Reproduce:
1. Deploy overcloud
2. Set availability zone in cinder. Nova should be the default.
3. Run the listed tests in tempest.

Actual results:
All test cases failed.

Expected results:
Those test cases should be passed.

Additional info:
This issue is being discussed in upstream launchpad, https://bugs.launchpad.net/tempest/+bug/1647999
However, the discussed gerrit focuses on scenario cases only.

Comment 4 Martin Kopec 2019-08-06 13:22:41 UTC
Created attachment 1601017 [details]
verification output

The Fixed in version package contains the fix for the issue, I attached a console output.

Comment 5 Martin Kopec 2019-08-06 13:23:14 UTC
Based on my previous comment (#4) I'm marking this as VERIFIED.

Comment 7 errata-xmlrpc 2019-09-21 11:23:21 UTC
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/RHEA-2019:2811