Created attachment 1351609 [details] File contains contents of inventory file, all.yml, Failure message snippet, ansible-playbook log Description of problem: Containerized osd disk preparation failing when osd_auto_discovery is set to true. Version-Release number of selected component (if applicable): ceph-ansible-3.0.10-2.el7cp.noarch ansible-2.4.1.0-1.el7ae.noarch ceph-3.0-rhel-7-docker-candidate-69814-20171110190200 How reproducible: 1/1 Steps to Reproduce: 1. Configure ceph-ansible to initialize containerized cluster having at least one osd node for which osd_auto_discovery set to true 2. run ansible-playbook Actual results: TASK [ceph-osd : automatic prepare ceph containerized osd disk collocated] failed: [magna012] (item=/dev/sdd) => {"changed": true, "cmd": "docker run --net=host --pid=host --privileged=true --name=ceph-osd-prepare-magna012-sdd -v /etc/ceph:/etc/ceph -v /var/lib/ceph/:/var/lib/ceph/ -v /dev:/dev -v /etc/localtime:/etc/localtime:ro -e DEBUG=verbose -e CLUSTER=a_1 -e CEPH_DAEMON=OSD_CEPH_DISK_PREPARE -e OSD_DEVICE=/dev/sdd -e OSD_BLUESTORE=0 -e OSD_FILESTORE=1 -e OSD_DMCRYPT=0 -e OSD_JOURNAL_SIZE=5120 brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhceph:ceph-3.0-rhel-7-docker-candidate-69814-20171110190200", ... "failed": true, ... (Please refer attachment for larger log snippet) Expected results: OSD disk preparation must be successful when osd auto discovery set to true Additional info: Please let me know if anything has been missed
Please send me the output of "parted --script /dev/sdd print" Thanks.
$ sudo parted --script /dev/sdd print Error: /dev/sdd: unrecognised disk label Model: ATA Hitachi HUA72201 (scsi) Disk /dev/sdd: 1000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags:
@Ken, there is a fix for ceph-ansible AND ceph-container. So QE should also test with the last container image.
Working fine with - ceph-3.0-rhel-7-docker-candidate-78841-20171115231319 and ceph-ansible-3.0.12-1.el7cp.noarch. Moving to VERIFIED state.
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/RHBA-2017:3387