Bug 1806814 - [ceph-ansible] add-osd.yml sets noup and then restart osds in containerized environment
Summary: [ceph-ansible] add-osd.yml sets noup and then restart osds in containerized e...
Keywords:
Status: CLOSED DUPLICATE of bug 1816023
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 3.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 3.3
Assignee: ceph-docs@redhat.com
QA Contact: Tejas
URL:
Whiteboard:
: 1809198 1813886 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-25 05:13 UTC by James Biao
Modified: 2023-12-15 17:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: add-osd.yml sets noup and then restart osds in containerized environment Consequence: playbook will never be successful because of the osd is 'noup' Workaround (if any): use the main playbook with --limit osds instead of add-osd.yml Result:
Clone Of:
Environment:
Last Closed: 2020-09-21 02:45:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-8047 0 None None None 2023-12-15 17:28:07 UTC

Description James Biao 2020-02-25 05:13:25 UTC
Description of problem:

add-osd.yml always sets noup and calls handler to restart osds. As expect, the restarted osd will never be up and the playbook hangs then timeout.

by manually unset noup, the playbook will continue and eventually succeed.
it happens 100% in containerized deployment

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

How reproducible:
always

Steps to Reproduce:
1. run add-osd.yml in containerized deployment
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Guillaume Abrioux 2020-03-03 09:24:27 UTC
*** Bug 1809198 has been marked as a duplicate of this bug. ***

Comment 5 Guillaume Abrioux 2020-03-16 13:52:14 UTC
*** Bug 1813886 has been marked as a duplicate of this bug. ***

Comment 9 James Biao 2020-09-21 02:45:44 UTC

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


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