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

Bug 1937226

Summary:	ansible final message is a bit misleading
Product:	Red Hat OpenStack	Reporter:	Michael Vollmer <mivollme>
Component:	python-tripleoclient	Assignee:	Cédric Jeanneret <cjeanner>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	low	Docs Contact:
Priority:	low
Version:	17.0 (Wallaby)	CC:	cjeanner, drosenfe, hbrock, jslagle, mburns, pweeks, sandro.roth
Target Milestone:	beta	Keywords:	Triaged
Target Release:	17.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-16.4.1-0.20220705111519.23dbe54.el9ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-21 12:14:01 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 Michael Vollmer 2021-03-10 08:01:59 UTC

Description of problem:
After a stack update/or overcloud install the last message is:
"Overcloud Deployed without error"

----

IF there's an error durign deployment the last message is:
"Overcloud Deployed with error"

So the only difference between a successful and fail deployment is "without error" or "with error".

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

How reproducible:
run a stack update on OSP16.1.3

Steps to Reproduce:
1.
2.
3.

Actual results:
"Overcloud Deployed without error"

Expected results:
"Overcloud Deployed Successfully"

Additional info:
I would suggest to change the final message to something different which does not include error when the deployment is successful.

Comment 3 Cédric Jeanneret 2021-08-17 13:26:58 UTC

Upstream master merged - starting the different backports down to stable/train.

Not sure it will hit 16.1 though - would 16.2 be OK? Or, even, 17.0?

Cheers,

C.

Comment 4 Michael Vollmer 2021-08-17 13:33:54 UTC

Cool, thanks!

Yes sure, backport it where you think it makes sense in terms of effort.
For me it doesn't matter.
Best regards
Michael

Comment 5 Cédric Jeanneret 2021-08-17 13:35:26 UTC

Thanks - moving to osp-17.0 RC, it makes more sense, especially seeing the close-to-no-use change it represents, compared to the backport dance it involves ;).

Cheers,

C.

Comment 6 pweeks 2021-08-18 13:40:03 UTC

this is more a bug than RFE, it will land in 17.

Comment 15 David Rosenfeld 2022-07-28 20:31:47 UTC

Message saying Overcloud Deployed successfully is now seen after successful overcloud deploy:

Overcloud Endpoint: https://10.0.0.102:13000
Overcloud Horizon Dashboard URL: https://10.0.0.102:443/dashboard
Overcloud rc file: /home/stack/overcloud-deploy/overcloud/overcloudrc and /home/stack/overcloudrc
Overcloud Deployed successfully
2022-07-27 22:37:26.853 122593 INFO tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Stopping ephemeral heat.
2022-07-27 22:37:26.998 122593 INFO tripleoclient.heat_launcher [-] Pod does not exist: ephemeral-heat
2022-07-27 22:37:32.310 122593 INFO osc_lib.shell [-] END return value: None

Comment 20 errata-xmlrpc 2022-09-21 12:14: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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543