Bug 1788644 - [RFE] [ceph-ansible] : fail site-docker.yml and site.yml if there are no mgr in inventory
Summary: [RFE] [ceph-ansible] : fail site-docker.yml and site.yml if there are no mgr ...
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
low
low
Target Milestone: z4
: 3.3
Assignee: Dimitri Savineau
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-07 16:57 UTC by Vasishta
Modified: 2020-04-06 08:27 UTC (History)
11 users (show)

Fixed In Version: RHEL: ceph-ansible-3.2.40-1.el7cp Ubuntu: ceph-ansible_3.2.40-2redhat1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-06 08:27:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 5052 0 None closed ceph-validate: fail if no mgr host is present 2021-01-20 09:43:39 UTC
Red Hat Product Errata RHBA-2020:1320 0 None None None 2020-04-06 08:27:42 UTC

Description Vasishta 2020-01-07 16:57:02 UTC
Description of problem:
rolling update fails if user misses to add mgrs to inventory before initiating playbook (valid scenario - upgrade from 2.x to 3.x) [1] 
This can be implemented to site.yml or site-docker.yml to alert the user if he misses out adding at least 1 mgr to the inventory

Version-Release number of selected component (if applicable):
ceph-ansible-3.2.38-1.el7cp.noarch

[1] https://github.com/ceph/ceph-ansible/blob/stable-3.2/infrastructure-playbooks/rolling_update.yml#L39-L43

Comment 12 errata-xmlrpc 2020-04-06 08:27:06 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-2020:1320


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