Bug 1597930 - [backport] luminous: osd: change log level when withholding pg creation
Summary: [backport] luminous: osd: change log level when withholding pg creation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 3.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: z1
: 3.1
Assignee: Josh Durgin
QA Contact: ceph-qe-bugs
Bara Ancincova
URL:
Whiteboard:
Depends On:
Blocks: 1584264
TreeView+ depends on / blocked
 
Reported: 2018-07-04 00:25 UTC by Vikhyat Umrao
Modified: 2021-12-10 16:38 UTC (History)
5 users (show)

Fixed In Version: RHEL: ceph-12.2.5-46.el7cp Ubuntu: ceph_12.2.5-31redhat1
Doc Type: Bug Fix
Doc Text:
.PGs stuck activating now appear in the OSD log at the default log level Placement groups (PGs) that are stuck activating due to hard limits on PGs per OSD now appear in the OSD log at the default log level, so this situation is easier to diagnose.
Clone Of:
Environment:
Last Closed: 2018-11-09 00:59:17 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-2651 0 None None None 2021-12-10 16:38:01 UTC
Red Hat Product Errata RHBA-2018:3530 0 None None None 2018-11-09 01:00:30 UTC

Description Vikhyat Umrao 2018-07-04 00:25:16 UTC
Description of problem:
backport: luminous: osd: change log level when withholding pg creation 
https://github.com/ceph/ceph/pull/22839

Version-Release number of selected component (if applicable):
Red Hat Ceph Storage 3

This came from the bug - https://bugzilla.redhat.com/show_bug.cgi?id=1597425

Comment 12 errata-xmlrpc 2018-11-09 00:59:17 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, 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-2018:3530


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