Bug 1883487 - Moving from One RGW per node to Two RGW per node fails while using site.yml playbook with --limit rgws option with ceph-ansible multisite configured on RHCS 4.2 bare metal cluster
Summary: Moving from One RGW per node to Two RGW per node fails while using site.yml p...
Keywords:
Status: CLOSED DUPLICATE of bug 1881313
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 4.*
Assignee: Guillaume Abrioux
QA Contact: Ameena Suhani S H
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-29 11:17 UTC by Manasa
Modified: 2020-09-29 14:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 14:24:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Manasa 2020-09-29 11:17:53 UTC
Description of problem:
moving from One RGW per node to Two RGW per node fails while using site.yml playbook with --limit rgws option with ceph-ansible multisite configured on RHCS 4.2 bare metal cluster


cli used: ansible-playbook site.yml -i hosts --limit rgws

Version-Release number of selected component (if applicable):
ceph version 14.2.11-34.el8cp
ceph-ansible-4.0.34-1.el8cp.noarch
ansible-2.9.13-1.el8ae.noarch


How reproducible:2/2


Steps to Reproduce:
1. Deploy RHCS 4.2 cluster on bare metal.
2. Change the settings in all.yml to add radosgw_num_instances: 2
3. Rerun the site.yml playbook with --limit rgws option

Actual results:
Playbook fails with error and only one rgw instance is found per node.

Expected results:
2 rgw instances are enabled per node.


Additional info:
Attached the inventory, all.yml and ansible log for the error.

Comment 1 RHEL Program Management 2020-09-29 11:17:55 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 3 Guillaume Abrioux 2020-09-29 14:24:03 UTC

*** This bug has been marked as a duplicate of bug 1881313 ***


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