Bug 1937226 - ansible final message is a bit misleading
Summary: ansible final message is a bit misleading
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 17.0
Assignee: Cédric Jeanneret
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-10 08:01 UTC by Michael Vollmer
Modified: 2022-09-21 12:14 UTC (History)
7 users (show)

Fixed In Version: python-tripleoclient-16.4.1-0.20220705111519.23dbe54.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-21 12:14:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 803194 0 None None None 2021-08-03 10:17:23 UTC
OpenStack gerrit 804858 0 None None None 2021-08-18 13:43:44 UTC
Red Hat Issue Tracker OSP-2638 0 None None None 2022-01-29 05:32:38 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:14:32 UTC

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


Note You need to log in before you can comment on or make changes to this bug.