Bug 1654525

Summary:	heat_tempest_plugin.tests.scenario.test_volumes.VolumeBackupRestoreIntegrationTest.test_cinder_volume_create_backup_restore was run even if cinder-backup is not configured.
Product:	Red Hat OpenStack	Reporter:	Keigo Noha <knoha>
Component:	python-heat-tests-tempest	Assignee:	Rabi Mishra <ramishra>
Status:	CLOSED ERRATA	QA Contact:	Arik Chernetsky <achernet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	jschluet, knoha, ramishra
Target Milestone:	z6	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-heat-tests-tempest-0.3.0-1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1688076 (view as bug list)		Environment:
Last Closed:	2019-04-30 17:23:43 UTC	Type:	Bug
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:
Bug Blocks:	1688076

Description Keigo Noha 2018-11-29 01:35:54 UTC

Description of problem:
heat_tempest_plugin.tests.scenario.test_volumes.VolumeBackupRestoreIntegrationTest.test_cinder_volume_create_backup_restore was run even if cinder-backup is not configured.
Running this test case without cinder-backup causes:
1. A stack with DELETE_FAILED status.
2. User can not delete the case until the user changes the status of volume resource created
in mariadb database directly. 


Version-Release number of selected component (if applicable):
Current heat_tests_tempest

How reproducible:
Everytime when user runs the tests.

Steps to Reproduce:
1. Deploy undercloud and overcloud without cinder-backup
2. Configure tempest with heat_plugins section.
3. Run tempest.

Actual results:
The test scenario was run and causes stack cannot be deleted.

Expected results:
The test scenario should not be run if cinder-backup is not configured.

Additional info:

Comment 9 errata-xmlrpc 2019-04-30 17:23:43 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/RHBA-2019:0926