This is the BZ RFE for tracking RHCEPH-350
(In reply to Sebastian Wagner from comment #0) <snip> > > (I just don't want to look into Trello everytime to see this issue) It should be in JIRA. In fact, once we are in JIRA, I expect this Bugzilla to automatically sync into JIRA. So in 5.1, either this item is in JIRA, or you create a Bugzilla and it'll sync into JIRA - in either case, your primary tool is JIRA. (note that regardless, the flow I would expect is this to be an issue upstream, and downstream will just inherit the feature when rebasing, which I assume we'll do for 5.1 or 5.2.
(In reply to Yaniv Kaul from comment #1) > (In reply to Sebastian Wagner from comment #0) > > <snip> > > > > (I just don't want to look into Trello everytime to see this issue) > > It should be in JIRA. In fact, once we are in JIRA, I expect this Bugzilla > to automatically sync into JIRA. I've already seen lots of automated sync-ups with Jira already. I wonder why this hasn't been synced up already. Anyway. > So in 5.1, either this item is in JIRA, or you create a Bugzilla and it'll > sync into JIRA - in either case, your primary tool is JIRA. +1 > (note that regardless, the flow I would expect is this to be an issue > upstream, and downstream will just inherit the feature when rebasing, which > I assume we'll do for 5.1 or 5.2. +1 David is already working on adding CentOS Stream 9 to upstream.
This issue is BLOCKED by Ceph upstream not supporting CentOS 9 Stream.
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 (Moderate: Red Hat Ceph Storage Security, Bug Fix, and Enhancement 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-2022:5997