Bug 2184673 - Bootstrap a cluster using cephadm-ansible module 'cephadm_bootstrap' with docker fails
Summary: Bootstrap a cluster using cephadm-ansible module 'cephadm_bootstrap' with doc...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.1z2
Assignee: Guillaume Abrioux
QA Contact: Mohit Bisht
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-05 11:53 UTC by Vinayak Papnoi
Modified: 2023-07-17 18:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6381 0 None None None 2023-04-05 11:54:36 UTC
Red Hat Issue Tracker RHCEPHQE-8144 0 None None None 2023-04-05 11:53:24 UTC

Description Vinayak Papnoi 2023-04-05 11:53:24 UTC
Created attachment 1955879 [details]
Failure observed while starting docker service

Description of problem:

While performing bootstrap of a cluster using cephadm ansible playbook, it fails with below error.

2023-03-31 21:33:54,710 (cephci.test_remove_cluster) [DEBUG] - cephci.ceph.ceph.py:1507 - b'    RuntimeError: Failed command: systemctl start ceph-40e5fcea-d02d-11ed-876c-fa163ec411a9: Failed to start ceph-40e5fcea-d02d-11ed-876c-fa163ec411a9.service: Unit docker.service not found.'

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

16.2.10-160

How reproducible:

5/5


Steps to Reproduce:
1. Bootstrap a cluster using cephadm ansible playbook


Actual results:

Failed to start ceph-40e5fcea-d02d-11ed-876c-fa163ec411a9.service: Unit docker.service not found.'

Expected results:

Bootstrap should finish successfully.

Additional info:

Comment 1 Scott Ostapovicz 2023-07-12 12:15:22 UTC
Missed the 6.1 z1 window.  Retargeting to 6.1 z2.


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