Bug 1809198

Summary:	add-osd.yml playbook fails because flag noup is set after osds are started
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Guillaume Abrioux <gabrioux>
Component:	Ceph-Ansible	Assignee:	Guillaume Abrioux <gabrioux>
Status:	CLOSED DUPLICATE	QA Contact:	Vasishta <vashastr>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.3	CC:	aschoen, ceph-eng-bugs, gmeno, nthomas, ykaul
Target Milestone:	z5
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-03 09:24:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Guillaume Abrioux 2020-03-02 15:02:13 UTC

Description of problem:
add-osd.yml playbook fails because flag noup is set after osds are started

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

How reproducible:
100%

Steps to Reproduce:
1. Deploy an RHCS 3.x cluster
2. Try to add an OSD using add-osd.yml

Actual results:

The playbook fails at the following task:

TASK [ceph-osd : wait for all osd to be up] ************************************
task path: /home/jenkins-build/build/workspace/ceph-ansible-nightly-luminous-centos-container-stable-3.2-add_osds/roles/ceph-osd/tasks/main.yml:92
Sunday 01 March 2020  22:14:23 +0000 (0:00:00.086)       0:02:08.736 ********** 
FAILED - RETRYING: wait for all osd to be up (60 retries left).

This is because noup flag is set.


Expected results:

The playbook doesn't fail and the new OSD is properly added to the cluster.

Comment 1 Guillaume Abrioux 2020-03-03 09:24:27 UTC


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