Description of problem: When building a hyperconverged pod with ovirt-node, the Gluster Deployment fails to complete with error message: TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [vh2.core.xxxxxx.net] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Cannot use /dev/sdb: device is rejected by filter config\n", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} Earlier in the playbook, it skips over removing the LVM filter: TASK [gluster.infra/roles/backend_setup : Remove the existing LVM filter] ****** skipping: [vh2.core.xxxxxxx.net] Manually removing the filter from /etc/lvm/lvm.conf prior to starting the playbook allows the Gluster Deployment to process properly. Version-Release number of selected component (if applicable): 4.4.9 How reproducible: Everytime Steps to Reproduce: 1. Install node(s) with ovirt-node 2. Run Hyperconverged Hosted Engine Setup in Cockpit Actual results: Deployment Fails Expected results: Deployment Succeeds Additional info:
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Is this issue occured in fresh deployment?
(In reply to Gobinda Das from comment #2) > Is this issue occured in fresh deployment? Yes a fresh deployment. I tried it both with a 3-node and single node configuration and both attempts ran into the issue with the LVM filter not being removed. I also did notice that once the deployment is complete, it does properly restore the LVM filter with both the OS PV and the Gluster PV.
Can you check vdsm-python package installed to check. please share the o/p of command 'rpm -q vdsm-python'
(In reply to Ritesh Chikatwar from comment #4) > Can you check vdsm-python package installed to check. please share the o/p > of command 'rpm -q vdsm-python' Type.. Can you check vdsm-python package installed, please share the o/p of command 'rpm -q vdsm-python'
(In reply to Ritesh Chikatwar from comment #5) > (In reply to Ritesh Chikatwar from comment #4) > > Can you check vdsm-python package installed to check. please share the o/p > > of command 'rpm -q vdsm-python' > > Type.. > Can you check vdsm-python package installed, please share the o/p of > command 'rpm -q vdsm-python' vdsm-python-4.40.90.4-1.el8.noarch (This is stock install of ovirt-node 4.4.9)
Can you share the deployment log when this issue occurred. You can find the deployment logs on node at this location (/var/log/cockpit/ovirt-dashboard/) file name will be gluster-deployment.log
(In reply to Ritesh Chikatwar from comment #7) > Can you share the deployment log when this issue occurred. You can find the > deployment logs on node at this location (/var/log/cockpit/ovirt-dashboard/) > file name will be gluster-deployment.log Unfortunately, the system is not available any longer as we completed our oVirt evaluation and it will be a few weeks or months before we revisit the system when we setup the production implementation.
Okay no problem, I will close this ticket now whenever you are ready with prod implementation, if you face the same issue again please re-open ticket and attach the logs which i requested in previous comment. I will take a look on the log and help. Is that sounds good ?
(In reply to Jay Cochran from comment #8) > (In reply to Ritesh Chikatwar from comment #7) > > Can you share the deployment log when this issue occurred. You can find the > > deployment logs on node at this location (/var/log/cockpit/ovirt-dashboard/) > > file name will be gluster-deployment.log > > Unfortunately, the system is not available any longer as we completed our > oVirt evaluation and it will be a few weeks or months before we revisit the > system when we setup the production implementation. The requested log is not available as system is no longer exists. I would suggest please try with fresh installation if you face same issue again please re-open the case & also attach log on node at this location (/var/log/cockpit/ovirt-dashboard/) file name will be gluster-deployment.log Thanks Ritesh