Bug 2116689 - bootstrap with apply-spec does not return fail exit code with a failure
Summary: bootstrap with apply-spec does not return fail exit code with a failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.0
Assignee: Adam King
QA Contact: Manisha Saini
Masauso Lungu
URL:
Whiteboard:
: 2114882 (view as bug list)
Depends On:
Blocks: 2118541 2126050
TreeView+ depends on / blocked
 
Reported: 2022-08-09 07:41 UTC by Sunil Kumar Nagaraju
Modified: 2023-03-20 18:57 UTC (History)
5 users (show)

Fixed In Version: ceph-17.2.3-24.el9cp
Doc Type: Bug Fix
Doc Text:
.`cephadm` returns non-zero code when `--apply-spec` option fails during bootstrap Previously, `cephadm` bootstrap always returned code `0` if the operation was complete. If there were any failures in the deployment using the `--apply-spec` option, it would not reflect any failures in the return code. With this fix, `cephadm` returns a non-zero value when applying specification fails during bootstrap.
Clone Of:
: 2118541 (view as bug list)
Environment:
Last Closed: 2023-03-20 18:57:13 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-5023 0 None None None 2022-08-09 07:55:54 UTC
Red Hat Product Errata RHBA-2023:1360 0 None None None 2023-03-20 18:57:55 UTC

Comment 10 Adam King 2022-10-04 02:20:58 UTC 
*** Bug 2114882 has been marked as a duplicate of this bug. ***
Comment 17 errata-xmlrpc 2023-03-20 18:57:13 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 Ceph Storage 6.0 Bug Fix update), 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-2023:1360
Note You need to log in before you can comment on or make changes to this bug.