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

Bug 1891197

Summary:	nova-event-callback validation doesn't validate vif_plugging_timeout_check properly
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-tripleo-validations	Assignee:	Gaël Chamoulaud <gchamoul>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	aschultz, cjeanner, gchamoul, jjoyce, jschluet, slinaber, tvignaud
Target Milestone:	z3	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openstack-tripleo-validations-11.3.2-1.20200916153436.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 18:37:11 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:

Description Alex Stupnikov 2020-10-24 09:38:16 UTC

Description of problem:

puppet-nova sets vif_plugging_timeout to 300 seconds by default. In tripleo validations vif_plugging_timeout_value_min is set to 300 seconds [1]

But appropriate check [2] seem to contain a typo: check "Check Nova configuration values" should fail if vif_plugging_timeout_value_min is greater than actual sets vif_plugging_timeout, but actual code tells it to fail if it is greater than or equal.

It looks like a minor bug.

[1]
https://github.com/openstack/tripleo-validations/blob/stable/train/playbooks/nova-event-callback.yaml#L24

[2]
https://github.com/openstack/tripleo-validations/blob/stable/train/roles/nova_event_callback/tasks/main.yml#L19
Version-Release number of selected component (if applicable):

Comment 2 Artom Lifshitz 2020-11-02 17:21:54 UTC

*** Bug 1867049 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2020-12-15 18:37:11 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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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-2020:5413