Bug 2262052 - default multisite zonegroup creation should contain realm
Summary: default multisite zonegroup creation should contain realm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.15.0
Assignee: Parth Arora
QA Contact: Shivam Durgbuns
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-31 06:01 UTC by Parth Arora
Modified: 2024-07-18 04:25 UTC (History)
5 users (show)

Fixed In Version: 4.15.0-141
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-19 15:32:27 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 562 0 None open Bug 2262052: object: fix the deafult multisite zonegroup creation 2024-01-31 16:07:54 UTC
Red Hat Product Errata RHSA-2024:1383 0 None None None 2024-03-19 15:32:30 UTC

Description Parth Arora 2024-01-31 06:01:05 UTC
Description of problem (please be detailed as possible and provide log
snippests):

default multisite zonegroup creation should contain realm,
2024-01-30 20:21:53.822971 E | ceph-object-controller: failed to reconcile CephObjectStore "object-ns/other-tls-test-store". failed to create object store deployments: failed to configure multisite for object store: failed create ceph multisite for object-store ["other-tls-test-store"]: failed to create ceph ["zone" "--rgw-zone=other-tls-test-store" "unable to initialize zonegroup other-tls-test-store: (2) No such file or directory. "] %!!(MISSING)q(MISSING), for reason %!!(MISSING)q(MISSING): exit status 2


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 2 Parth Arora 2024-01-31 06:02:42 UTC
Fix upstream: https://github.com/rook/rook/pull/13655

Comment 3 Travis Nielsen 2024-01-31 16:48:21 UTC
This is needed for 4.15 as was discovered when backporting the related change to 4.14 with BZ 2254547, see [1].

Neha, could we get a QE ack?

[1] https://github.com/red-hat-storage/rook/pull/559

Comment 4 Elad 2024-02-06 13:17:03 UTC
Hi Parth, would you be able to provide the steps for verifying the fix?

Comment 11 errata-xmlrpc 2024-03-19 15:32:27 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & 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/RHSA-2024:1383

Comment 12 Red Hat Bugzilla 2024-07-18 04:25:32 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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