Bug 1927796 - successful tripleo_deploy run with --standalone and --output-only exits with non 0 exit code
Summary: successful tripleo_deploy run with --standalone and --output-only exits with ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Alpha
: 16.2 (Train on RHEL 8.4)
Assignee: Martin Schuppert
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks: 1925999
TreeView+ depends on / blocked
 
Reported: 2021-02-11 14:41 UTC by Martin Schuppert
Modified: 2021-09-15 07:12 UTC (History)
4 users (show)

Fixed In Version: python-tripleoclient-12.3.2-2.20210130011045.62fd486.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-15 07:11:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 771762 0 None MERGED [train-only] Set rc = 0 for successful standalone/output-only action 2021-02-18 08:13:54 UTC
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:12:21 UTC

Description Martin Schuppert 2021-02-11 14:41:11 UTC 
Description of problem:

Right now when --standalone and --output-only is used
with a successful action, the rc is still set to
rc = 1


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 6 errata-xmlrpc 2021-09-15 07:11:47 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 (RHOSP) 16.2 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-2021:3483
Note You need to log in before you can comment on or make changes to this bug.