Bug 2250052

Summary:	`default-node-count` validation fails if a user do `validation run` following the document.
Product:	Red Hat OpenStack	Reporter:	Joanne O'Flynn <joflynn>
Component:	openstack-tripleo-validations	Assignee:	Jiri Podivin <jpodivin>
Status:	CLOSED ERRATA	QA Contact:	Nobody <nobody>
Severity:	low	Docs Contact:
Priority:	low
Version:	17.1 (Wallaby)	CC:	jbadiapa, jjoyce, jschluet, mariel, rhayakaw, slinaber, tvignaud
Target Milestone:	z4	Keywords:	Bugfix, Triaged
Target Release:	17.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-validations-14.3.2-17.1.20240709110808.2b526f8.el9ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2242088	Environment:
Last Closed:	2024-11-21 09:39:01 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:	2242088
Bug Blocks:

Description Joanne O'Flynn 2023-11-16 12:19:16 UTC

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

Description of problem:

`default-node-count` validation fails if a user do `validation run` following the document.

There are sections in the document `Installing and managing Red Hat OpenStack Platform with director`[1] of OSP17.1 in the following order:

11.2. Provisioning bare metal overcloud nodes

11.3.5. Validating your overcloud configuration

11.3.6. Creating your overcloud


The section "11.3.5. Validating your overcloud configuration" mentions `validation run --group pre-deployment`.

On the other hand, the `pre-deployment` group has the validation `default-node-count`.
As far as I checked  /usr/share/ansible/roles/default_node_count/tasks/main.yml, `default-node-count` expects that the provisioning state is `available`.

However, as I wrote in the above, before a user run `validation run --group pre-deployment` by following "11.3.5. Validating your overcloud configuration", the provisioning state is already `active`. It is because the node provisioning is completed in  "11.2. Provisioning bare metal overcloud nodes".

Is it possible to fix this?

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/installing_and_managing_red_hat_openstack_platform_with_director/index#proc_validating-your-overcloud-configuration_ironic_provisioning

Comment 1 Juan Badia Payno 2024-06-10 12:42:34 UTC

Moved to z4

Comment 12 errata-xmlrpc 2024-11-21 09:39:01 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 (RHOSP 17.1.4 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/RHBA-2024:9974