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.
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.
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
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.
this is more a bug than RFE, it will land in 17.
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
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