Bug 1822599 - ceph-ansible fails adding a new odd when crush_rule_config is enabled
Summary: ceph-ansible fails adding a new odd when crush_rule_config is enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 4.1
Assignee: Guillaume Abrioux
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-09 13:15 UTC by Guillaume Abrioux
Modified: 2020-05-19 17:33 UTC (History)
9 users (show)

Fixed In Version: ceph-ansible-4.0.19-1.el8cp, ceph-ansible-4.0.19-1.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-19 17:33:19 UTC
Embargoed:
hyelloji: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 5261 0 None closed osd: fix monitor_name error when scaling out OSDs 2020-06-23 11:33:07 UTC
Red Hat Product Errata RHSA-2020:2231 0 None None None 2020-05-19 17:33:47 UTC

Description Guillaume Abrioux 2020-04-09 13:15:44 UTC
Description of problem:

ceph-ansible fails to add a new odd when crush_rule_config is enabled.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. deploy a cluster using ceph-ansible v4.0.18 and enable crush_rule_config
2. try adding a new osd using the main playbook with --limit

Actual results:
ceph-ansible fails on task "insert new default crush rule into daemon to prevent restart"

Expected results:
ceph-ansible doesn't fail.

Comment 9 Vasishta 2020-04-29 09:39:03 UTC
Working fine with ceph-ansible-4.0.22-1.el7cp.noarch
Moving to VERIFIED state.

Comment 11 errata-xmlrpc 2020-05-19 17:33:19 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/RHSA-2020:2231


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