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

Bug 1569613

Summary:	compute.min_compute_nodes not discovered by tempestconf
Product:	Red Hat OpenStack	Reporter:	Attila Fazekas <afazekas>
Component:	python-tempestconf	Assignee:	Arx Cruz <acruz>
Status:	CLOSED ERRATA	QA Contact:	Martin Kopec <mkopec>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	acruz, udesale, whayutin
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:49:31 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:	1622011
Bug Blocks:

Description Attila Fazekas 2018-04-19 15:03:06 UTC

The live migration test are only running if tempest expect more than 1 hypervisor (or nova host with compute binary).

When tempestconf gets admin credentials it has the ability to guess this option properly, so please implement this.

Comment 1 Arx Cruz 2018-06-07 15:28:00 UTC

Fixed in https://github.com/openstack/python-tempestconf/commit/9be036cf1fa6b4992a29fa815c3dedd8650b9625

Comment 2 Martin Kopec 2018-08-14 06:40:22 UTC

The patch with a fix has been merged to master branch. The fix will be included in python-tempestconf-2.0.0 package released soon.
Until a package containing the fix is built, moving to POST state.

Comment 5 Martin Kopec 2018-10-26 10:11:24 UTC

The python-tempestconf-2.0.0-0.20180821043805.d7db90e.el7ost package contains the wanted ability. It's available in 2018-10-25.3 puddle and it's also available via latest symlink.

Comment 8 errata-xmlrpc 2019-01-11 11:49:31 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:0045