Bug 2109960 - [Rebase] rebase ceph to 17.2.3
Summary: [Rebase] rebase ceph to 17.2.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Distribution
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.0
Assignee: Ken Dreyer (Red Hat)
QA Contact: Aditya Ramteke
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-22 14:29 UTC by Ken Dreyer (Red Hat)
Modified: 2023-03-20 18:57 UTC (History)
1 user (show)

Fixed In Version: ceph-17.2.3-1.el9cp
Doc Type: No Doc Update
Doc Text:
Clone Of:
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-4890 0 None None None 2022-07-22 14:33:43 UTC
Red Hat Product Errata RHBA-2023:1360 0 None None None 2023-03-20 18:57:55 UTC

Description Ken Dreyer (Red Hat) 2022-07-22 14:29:45 UTC 
Description of problem:
RHCEPH 6.0 currently has Ceph v17.2.1. We should rebase to the latest upstream release of Quincy.

Steps to Reproduce:
1. Install RHCEPH 6.0
2. Run "ceph --version"

Expected results:
17.2.2-something
Comment 1 RHEL Program Management 2022-07-22 14:29:51 UTC 
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Comment 2 Ken Dreyer (Red Hat) 2022-08-03 14:42:37 UTC 
v17.2.3 is a small release that fixes a crash with the latest GCC in RHEL 8. I've rebased to that version this week.
Comment 11 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.