Bug 1540137 - Ceph-ansible containerized purge failing in "resolve parent device" task
Summary: Ceph-ansible containerized purge failing in "resolve parent device" task
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 2.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 2.5
Assignee: Guillaume Abrioux
QA Contact: Parikshith
URL:
Whiteboard:
Depends On: 1541060
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-30 10:51 UTC by Parikshith
Modified: 2018-02-21 19:48 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-ansible-3.0.23-1.el7cp Ubuntu: ceph-ansible_3.0.23-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1541060 (view as bug list)
Environment:
Last Closed: 2018-02-21 19:48:14 UTC
Embargoed:


Attachments (Terms of Use)
docker-purge.log (125.27 KB, text/plain)
2018-01-30 10:51 UTC, Parikshith
no flags Details
Purge-docker logs (242.87 KB, text/plain)
2018-02-01 14:34 UTC, Parikshith
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 2362 0 None closed purge: fix resolve parent device task 2020-06-11 13:22:38 UTC
Github ceph ceph-ansible pull 2372 0 None closed purge-docker: fix ceph-osd-zap name container 2020-06-11 13:22:38 UTC
Red Hat Product Errata RHBA-2018:0340 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.5 bug fix and enhancement update 2018-02-22 00:50:32 UTC

Description Parikshith 2018-01-30 10:51:12 UTC
Created attachment 1388271 [details]
docker-purge.log

Description of problem:
Ceph-ansible containerized purge failing in "resolve parent device" task

Version-Release number of selected component (if applicable):
ceph-ansible-3.0.21-1
ceph -v : 10.2.10-15

How reproducible:


Steps to Reproduce:
1. Install rhcs 2.5 cluster on containers. 
2. Purge the cluster: ran "ansible-playbook purge-docker-cluster.yml -u ubuntu -vv" 

Actual results:
Purge Failed in the TASK [resolve parent device], with below error:
failed: [magna076] (item=/dev/sdb1) => {"changed": true, "cmd": "$(lsblk --nodeps -no pkname \"/dev/sdb1\")", "delta": "0:00:00.005439", "end": "2018-01-30 10:05:19.035226", "failed": true, "item": "/dev/sdb1", 
"msg": "non-zero return code", "rc": 127, "start": "2018-01-30 10:05:19.029787", "stderr": "/bin/sh: sdb: command not found", "stderr_lines": ["/bin/sh: sdb: command not found"], "stdout": "", "stdout_lines": []
}
failed: [magna044] (item=/dev/sdc1) => {"changed": true, "cmd": "$(lsblk --nodeps -no pkname \"/dev/sdc1\")", "delta": "0:00:00.005375", "end": "2018-01-30 10:05:19.108314", "failed": true, "item": "/dev/sdc1", 
"msg": "non-zero return code", "rc": 127, "start": "2018-01-30 10:05:19.102939", "stderr": "/bin/sh: sdc: command not found", "stderr_lines": ["/bin/sh: sdc: command not found"], "stdout": "", "stdout_lines": []
}
failed: [magna053] (item=/dev/sdb1) => {"changed": true, "cmd": "$(lsblk --nodeps -no pkname \"/dev/sdb1\")", "delta": "0:00:00.005483", "end": "2018-01-30 10:05:19.088745", "failed": true, "item": "/dev/sdb1", 
"msg": "non-zero return code", "rc": 127, "start": "2018-01-30 10:05:19.083262", "stderr": "/bin/sh: sdb: command not found", "stderr_lines": ["/bin/sh: sdb: command not found"], "stdout": "", "stdout_lines": []
}
failed: [magna064] (item=/dev/sdd1) => {"changed": true, "cmd": "$(lsblk --nodeps -no pkname \"/dev/sdd1\")", "delta": "0:00:00.005382", "end": "2018-01-30 10:05:19.040819", "failed": true, "item": "/dev/sdd1", 
"msg": "non-zero return code", "rc": 127, "start": "2018-01-30 10:05:19.035437", "stderr": "/bin/sh: sdd: command not found", "stderr_lines": ["/bin/sh: sdd: command not found"], "stdout": "", "stdout_lines": []
}

Additional info:

I Have attached complete logs. (-vv)

Comment 8 Parikshith 2018-02-01 14:34:19 UTC
Created attachment 1389534 [details]
Purge-docker logs

Comment 13 Guillaume Abrioux 2018-02-02 21:21:06 UTC
fixed in v3.0.23

Comment 22 errata-xmlrpc 2018-02-21 19:48:14 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/RHBA-2018:0340


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