Bug 1858706 - radosgw-admin lc list returns error after upgrade to 4.1
Summary: radosgw-admin lc list returns error after upgrade to 4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 4.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: z1
: 4.1
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-20 06:56 UTC by Manjunatha
Modified: 2023-12-15 18:30 UTC (History)
14 users (show)

Fixed In Version: ceph-14.2.8-89.el8cp, ceph-14.2.8-89.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-04 18:48:43 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 46677 0 None None None 2020-07-22 18:41:40 UTC
Red Hat Issue Tracker RHCEPH-7675 0 None None None 2023-10-06 21:13:00 UTC
Red Hat Product Errata RHBA-2020:3322 0 None None None 2020-08-04 18:48:54 UTC

Description Manjunatha 2020-07-20 06:56:35 UTC
Customer completed an upgrade from Ceph 3.3 to 4.1, since the upgrade they receive an error:
$ radosgw-admin lc list 
>ERROR: failed to list objs: (5) Input/output error

We would expect to receive the LC list

All PGs are in Active+clean status

Where are you experiencing the behavior? What environment?
This is happening on the customer's staging environment 

When does the behavior occur? Frequency? Repeatedly? At certain times?
Every time we type the command since the upgrade was successfully completed

What information can you provide around timeframes and the business impact?
This is holding the customer back from upgrading the production environment.

Comment 10 errata-xmlrpc 2020-08-04 18:48:43 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 4.1 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-2020:3322


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