Bug 1765230 - [ceph-ansible]Ceph-mds -allow multimds task is failing
Summary: [ceph-ansible]Ceph-mds -allow multimds task is failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 3.3
Assignee: Guillaume Abrioux
QA Contact: Vasishta
Erin Donnelly
URL:
Whiteboard:
Depends On: 1645379
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2019-10-24 14:51 UTC by tserlin
Modified: 2019-12-19 17:59 UTC (History)
14 users (show)

Fixed In Version: RHEL: ceph-ansible-3.2.32-1.el7cp Ubuntu: ceph-ansible_3.2.32-2redhat1
Doc Type: Bug Fix
Doc Text:
.`ceph_release` in no longer automatically being reset to `ceph_stable_release` when `ceph_repository` is set to `rhcs` Previously, `ceph_release` was automatically being reset to `ceph_stable_release` even when `ceph_repository` was set to `rhcs` in the `all.yml` file. `ceph_stable_release` is not needed when using the `rhcs` repository, and was being set to the automatic default value `dummy`. This caused the `allow multi mds` task to fail with the error `has no attribute` because `ceph_release_num` has no key `dummy`. With this update, `ceph_release` is no longer reset when `ceph_repository` is set to `rhcs`, and the task `allow multi mds` can be executed properly.
Clone Of: 1645379
Environment:
Last Closed: 2019-12-19 17:58:49 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:4353 0 None None None 2019-12-19 17:59:02 UTC

Comment 8 errata-xmlrpc 2019-12-19 17:58:49 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-2019:4353
Note You need to log in before you can comment on or make changes to this bug.