Bug 1843569 - [ceph-ansible] : switch from rpm to containerized - playbook failed when initiated second time as noup was not unset
Summary: [ceph-ansible] : switch from rpm to containerized - playbook failed when init...
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
medium
medium
Target Milestone: z1
: 4.1
Assignee: Guillaume Abrioux
QA Contact: Ameena Suhani S H
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-03 15:00 UTC by Vasishta
Modified: 2020-07-20 14:21 UTC (History)
10 users (show)

Fixed In Version: ceph-ansible-4.0.24-1.el8cp, ceph-ansible-4.0.24-1.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-20 14:21:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 5418 0 None closed switch_to_containers: don't set noup flag 2020-09-02 07:45:32 UTC
Red Hat Product Errata RHSA-2020:3003 0 None None None 2020-07-20 14:21:59 UTC

Description Vasishta 2020-06-03 15:00:24 UTC 
Description of problem:
re-initiated switch-from-non-containerized-to-containerized-ceph-daemons.yml, playbook failed waiting for waiting for clean pg. Actually noup flag was not unset

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

How reproducible:
Tried Twice, faced twice

Steps to Reproduce:
1. Configure a non-containerized cluster, run switch-from-non-containerized-to-containerized-ceph-daemons.yml twice.


Actual results:
Playbook fails as noup flag was not unset

Expected results:
Playbook must not fail
Comment 9 Ameena Suhani S H 2020-07-14 07:45:38 UTC 
Verified using 
Ceph Ansible Version: 4.0.25-1.el7cp.noarch
Comment 11 errata-xmlrpc 2020-07-20 14:21:41 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:3003
Note You need to log in before you can comment on or make changes to this bug.