Description of problem: Install failed TASK [openshift_storage_glusterfs : Create heketi DB volume] when crio and glusterfs used I did hit this failure with docker and glusterfs Version-Release number of the following components: openshift-ansible-3.11.17-1.git.0.5e2a56d.el7.noarch cri-o-1.11.5-2.rhaos3.11.git1c8a4b1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. install OCP v3.11 with cri-o and glusterfs Actual results: Install failed TASK [openshift_storage_glusterfs : Create heketi DB volume] ******************* Sunday 30 September 2018 21:28:34 +0800 (0:00:05.492) 0:32:48.717 ****** fatal: [wmeng1r311glcrio-master-etcd-1.0930-lxj.qe.rhcloud.com]: FAILED! => {"changed": true, "cmd": ["oc", "--config=/tmp/openshift-glusterfs-ansible-e6tuWP/admin.kubeconfig", "rsh", "--namespace=glusterfs", "deploy-heketi-storage-1-df87j", "heketi-cli", "-s", "http://localhost:8080", "--user", "admin", "--secret", "vJDl5s0nu2DVPc1puaVlyZsnexI27OWP3Zk4rwn2XPI=", "setup-openshift-heketi-storage", "--image", "registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7", "--listfile", "/tmp/heketi-storage.json"], "delta": "0:01:02.531070", "end": "2018-09-30 09:29:43.275290", "msg": "non-zero return code", "rc": 255, "start": "2018-09-30 09:28:40.744220", "stderr": "Error: WARNING: This metadata update is NOT backed up.\n /dev/mapper/vg_4f9cd84b81df3dc71c2830267f3ae5d0-lvol0: open failed: No such file or directory\n /dev/vg_4f9cd84b81df3dc71c2830267f3ae5d0/lvol0: not found: device not cleared\n Aborting. Failed to wipe start of new LV.\ncommand terminated with exit code 255", "stderr_lines": ["Error: WARNING: This metadata update is NOT backed up.", " /dev/mapper/vg_4f9cd84b81df3dc71c2830267f3ae5d0-lvol0: open failed: No such file or directory", " /dev/vg_4f9cd84b81df3dc71c2830267f3ae5d0/lvol0: not found: device not cleared", " Aborting. Failed to wipe start of new LV.", "command terminated with exit code 255"], "stdout": "", "stdout_lines": []} Expected results: Install succeeds. Additional info: Please attach logs from ansible-playbook with the -vvv flag
You're saying you hit this issue with docker as well, so it's not just a CRI-O problem?
Looks like this is a dup. closing...
This is not a dup, this is the original BZ. Reopening.
*** Bug 1634763 has been marked as a duplicate of this bug. ***
doh, sorry... closed the wrong one.
This is an issue previously discovered by the CNV team. This does not need to block the release, so closing this as DUPLICATE, *** This bug has been marked as a duplicate of bug 1627104 ***
(In reply to Jose A. Rivera from comment #3) > You're saying you hit this issue with docker as well, so it's not just a > CRI-O problem? sorry. that is a typo. not hit this when docker & glusterfs.