May 2021 - Users - oVirt List Archives

Error while deploying Hyperconverged oVirt 4.3.3(el7) + GlusterFS
by techbreak＠icloud.com 31 May '21

31 May '21

As title, we want to use 3 hosts with hyperconverged solution of oVirt. We installed oVirt and Gluster as reported in the guide https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… When we try to deploy, we get some errors which we cannot figure out. ============================================================== gdeploy creates as configuration rules: hc_nodes: hosts: virtnodetest-0-0: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G virtnodetest-0-1: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G virtnodetest-0-2: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G vars: gluster_infra_disktype: JBOD gluster_set_selinux_labels: true gluster_infra_fw_ports: - 2049/tcp - 54321/tcp - 5900/tcp - 5900-6923/tcp - 5666/tcp - 16514/tcp gluster_infra_fw_permanent: true gluster_infra_fw_state: enabled gluster_infra_fw_zone: public gluster_infra_fw_services: - glusterfs gluster_features_force_varlogsizecheck: false cluster_nodes: - virtnodetest-0-0 - virtnodetest-0-1 - virtnodetest-0-2 gluster_features_hci_cluster: '{{ cluster_nodes }}' gluster_features_hci_volumes: - volname: engine brick: /gluster_bricks/engine/engine arbiter: 0 - volname: isostorage brick: /gluster_bricks/isostorage/isostorage arbiter: 0 - volname: vmstorage brick: /gluster_bricks/vmstorage/vmstorage arbiter: 0 ========================================================================= The system returns this error: PLAY [Setup backend] *********************************************************** TASK [Gathering Facts] ********************************************************* ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [Check if valid hostnames are provided] *********************************** changed: [virtnodetest-0-1] => (item=virtnodetest-0-1) changed: [virtnodetest-0-1] => (item=virtnodetest-0-0) changed: [virtnodetest-0-1] => (item=virtnodetest-0-2) TASK [Check if provided hostnames are valid] *********************************** ok: [virtnodetest-0-1] => { "changed": false, "msg": "All assertions passed" } ok: [virtnodetest-0-0] => { "changed": false, "msg": "All assertions passed" } ok: [virtnodetest-0-2] => { "changed": false, "msg": "All assertions passed" } TASK [Check if /var/log has enough disk space] ********************************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if the /var is greater than 15G] *********************************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if disks have logical block size of 512B] ************************** skipping: [virtnodetest-0-1] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-0] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-2] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) TASK [Check if logical block size is 512 bytes] ******************************** skipping: [virtnodetest-0-1] => (item=Logical Block Size) skipping: [virtnodetest-0-0] => (item=Logical Block Size) skipping: [virtnodetest-0-2] => (item=Logical Block Size) TASK [Get logical block size of VDO devices] *********************************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if logical block size is 512 bytes for VDO devices] **************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/firewall_config : Start firewalld if not already started] *** ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [gluster.infra/roles/firewall_config : check if required variables are set] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/firewall_config : Open/Close firewalld ports] ******** ok: [virtnodetest-0-2] => (item=2049/tcp) ok: [virtnodetest-0-1] => (item=2049/tcp) ok: [virtnodetest-0-0] => (item=2049/tcp) ok: [virtnodetest-0-2] => (item=54321/tcp) ok: [virtnodetest-0-0] => (item=54321/tcp) ok: [virtnodetest-0-1] => (item=54321/tcp) ok: [virtnodetest-0-2] => (item=5900/tcp) ok: [virtnodetest-0-1] => (item=5900/tcp) ok: [virtnodetest-0-0] => (item=5900/tcp) ok: [virtnodetest-0-2] => (item=5900-6923/tcp) ok: [virtnodetest-0-0] => (item=5900-6923/tcp) ok: [virtnodetest-0-1] => (item=5900-6923/tcp) ok: [virtnodetest-0-2] => (item=5666/tcp) ok: [virtnodetest-0-1] => (item=5666/tcp) ok: [virtnodetest-0-0] => (item=5666/tcp) ok: [virtnodetest-0-2] => (item=16514/tcp) ok: [virtnodetest-0-1] => (item=16514/tcp) ok: [virtnodetest-0-0] => (item=16514/tcp) TASK [gluster.infra/roles/firewall_config : Add/Delete services to firewalld rules] *** ok: [virtnodetest-0-1] => (item=glusterfs) ok: [virtnodetest-0-0] => (item=glusterfs) ok: [virtnodetest-0-2] => (item=glusterfs) TASK [gluster.infra/roles/backend_setup : Check if vdsm-python package is installed or not] *** changed: [virtnodetest-0-2] changed: [virtnodetest-0-1] changed: [virtnodetest-0-0] TASK [gluster.infra/roles/backend_setup : Remove the existing LVM filter] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check that the multipath.conf exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Ensure that multipathd services is enabled if not] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Ensure that multipathd services is running] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create /etc/multipath/conf.d if doesn't exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Get the UUID of the devices] ********* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check that the blacklist.conf exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create blacklist template content] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Add wwid to blacklist in blacklist.conf file] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Reload multipathd] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Gather facts to determine the OS distribution] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for debian systems.] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for RHEL systems.] *** ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [gluster.infra/roles/backend_setup : Install python-yaml package for Debian systems] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Initialize vdo_devs array] *********** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record VDO devices (if any)] ********* skipping: [virtnodetest-0-1] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-0] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-2] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) TASK [gluster.infra/roles/backend_setup : Configure lvm thinpool extend threshold] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Configure lvm thinpool extend percentage] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vdo block device exists] **** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : set fact if it will at least install 1 vdo device] *** TASK [gluster.infra/roles/backend_setup : Install VDO dependencies] ************ skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : set fact about vdo installed deps] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Enable and start vdo service] ******** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create VDO with specified size] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set VDO maxDiscardSize as 16M] ******* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Stop VDO volumes] ******************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Start VDO volumes] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if valid disktype is provided] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for JBOD] ****** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for RAID] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set VG physical extent size for RAID] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : include_tasks] *********************** included: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/get_vg_groupings.yml for virtnodetest-0-1, virtnodetest-0-0, virtnodetest-0-2 TASK [gluster.infra/roles/backend_setup : Group devices by volume group name, including existing devices] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vg block device exists] ***** changed: [virtnodetest-0-0] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) changed: [virtnodetest-0-1] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) changed: [virtnodetest-0-2] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) TASK [gluster.infra/roles/backend_setup : Filter none-existing devices] ******** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** ok: [virtnodetest-0-1] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:18:33.575598', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.009901', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 12:18:33.565697'}) ok: [virtnodetest-0-0] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 10:52:56.886693', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.008123', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 10:52:56.878570'}) ok: [virtnodetest-0-2] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:25:24.420710', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.007307', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 12:25:24.413403'}) TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** skipping: [virtnodetest-0-1] => (item={u'key': u'gluster_vg_sdb', u'value': []}) skipping: [virtnodetest-0-0] => (item={u'key': u'gluster_vg_sdb', u'value': []}) skipping: [virtnodetest-0-2] => (item={u'key': u'gluster_vg_sdb', u'value': []}) TASK [gluster.infra/roles/backend_setup : update LVM fact's] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if thick-lv block devices exists] *** changed: [virtnodetest-0-0] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) changed: [virtnodetest-0-1] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) changed: [virtnodetest-0-2] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** skipping: [virtnodetest-0-1] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:18:37.528159', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.010032', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 12:18:37.518127'}) skipping: [virtnodetest-0-0] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 10:53:00.863436', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.007459', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 10:53:00.855977'}) skipping: [virtnodetest-0-2] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:25:28.261106', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.007818', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 12:25:28.253288'}) TASK [gluster.infra/roles/backend_setup : include_tasks] *********************** included: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/get_vg_groupings.yml for virtnodetest-0-1, virtnodetest-0-0, virtnodetest-0-2 TASK [gluster.infra/roles/backend_setup : Group devices by volume group name, including existing devices] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vg block device exists] ***** TASK [gluster.infra/roles/backend_setup : Filter none-existing devices] ******** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Make sure thick pvs exists in volume group] *** TASK [gluster.infra/roles/backend_setup : update LVM fact's] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create thick logical volume] ********* failed: [virtnodetest-0-1] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " WARNING: Device for PV gx6iUE-369Z-3FDP-aRUQ-Wur0-1Xhf-v4g79j not found or rejected by a filter.\n Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} failed: [virtnodetest-0-0] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} failed: [virtnodetest-0-2] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* virtnodetest-0-0 : ok=19 changed=3 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 virtnodetest-0-1 : ok=20 changed=4 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 virtnodetest-0-2 : ok=19 changed=3 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 Please check /var/log/cockpit/ovirt-dashboard/gluster-deployment.log for more informations. ====================================================================== How can we resolve this issue?

4 7

Creating Snapshots failed
by jb 31 May '21

31 May '21

Hello Community, since I upgrade our cluster to ovirt 4.4.6.8-1.el8 I'm not able anymore to create snapshots on certain VMs. For example I have two debian 10 VMs, from one I can make a snapshot, and from other one not. Both are up to date and uses the same qemu-guest-agent versions. I tried to create snapshots over API and on web gui, both gives the same result. In the attachment you found a snipped from the engine.log. Any help would be wonderful! Regards, Jonathan

2 3

oVirt 2021 Spring survey responses are now available
by Sandro Bonazzola 31 May '21

31 May '21

Thanks to the 133 participants in the oVirt 2021 Spring survey! The survey is now over and results are publicly available at [1]. [1] https://docs.google.com/forms/d/1RcSzRQ2YmB2U3MNlWk0YqTVFdGYIdguk46K2A-DZEv… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

Where to get the vm config file ?
by tommy 28 May '21

28 May '21

Thanks.

3 2

After upgrade only 1/3 hosts is running Node 4.4.6
by Jayme 28 May '21

28 May '21

I updated my three server HCI cluster from 4.4.5 to 4.4.6. All hosts updated successfully and rebooted and are active. I notice that only one host out of the three is actually running oVirt node 4.4.6 and the other two are running 4.4.5. If I check for upgrade in admin it shows no upgrades available. Why are two hosts still running 4.4.5 after being successfully upgraded/rebooted and how can I get them on 4.4.6 if no upgrades are being found?

2 6

[ANN] oVirt 4.4.7 First Release Candidate is now available for testing
by Lev Veyde 28 May '21

28 May '21

oVirt 4.4.7 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 First Release Candidate for testing, as of May 27th, 2021. This update is the seventh in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.7 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.7 (redeploy in case of already being on 4.4.7). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.7/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

unable to login cockpit using root after upgrading to 4.4.6
by dhanaraj.ramesh＠yahoo.com 28 May '21

28 May '21

Hi Team, after upgrading ovirt node from 4.4.5 to 4.4.6, unale to login to the cockpit using root, but could able to login via ssh. please check whether this is considered as bug

13 21

CPU usage question
by David Johnson 28 May '21

28 May '21

Hi everyone, I am slowly working the performance bottlenecks out of my rack, and ran into this puzzling scenario. Ovirt shows CPU usage at over 50%. Windows shows CPU usage between 5 and 15 % The backing store is TrueNAS NFS on a 10 GBit lan. I am seeing just under 1 GBit throughput on the storage network for this operation (create database). Am I reading this correctly that my system is bottlenecking on the CPU used to handle the Windows disk IO over TCP/IP ? Thanks *David Johnson* Screenshot of pertinent metrics: [image: image.png] <https://www.linkedin.com/in/pojoguy/> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> <https://maxistechnology.com/> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>

2 1

Unable to migrate VMs
by Jayme 27 May '21

27 May '21

I have a three node oVirt 4.4.5 cluster running oVirt node hosts. Storage is mix of GlusterFS and NFS. Everything has been running smoothly, but the other day I noticed many VMs had invalid snapshots. I run a script to export OVA for VMs for backup purposes, exports seemed to have been fine but snapshots failed to delete at the end. I was able to manually delete the snapshots through oVirt admin GUI without any errors/warnings and the VMs have been running fine and can restart them without problems. I thought this problem may be due to snapshot bug which is supposedly fixed in oVirt 4.4.6. I decided to start upgrading cluster to 4.4.6 and am now having a problem with VMs not being able to migrate. When I migrate any VM (doesn't seem to matter which host to and from) the process starts but stops at 0-1%. Eventually after 15-30 minutes or more the tasks are all completed by the VM is not migrated. I am unable to migrate any VMs and as such I cannot place any host in maintenance mode. I've attaching some VDSM logs from source and destination hosts, these were after initiating a migration of a single VM I'm seeing some errors in the logs regarding the migration stalling, but not able to determine why its stalling. 2021-05-27 17:10:22,167+0000 INFO (jsonrpc/4) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:10:31,118+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:31,118+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 190.035 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:33,827+0000 INFO (jsonrpc/5) [throttled] Current getAllVmStats: {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': 'Up', '2b87204f-f695-474a-9f08-47b85fcac366': 'Up', '26332421-54a3-4afc-90e7-551a7e314c80': 'Up', '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': 'Up', 'beeefe06-78a0-4e14-a932-cc8d734d542d': 'Up', '7e5156de-649d-4904-9092-21a699242a37': 'Migration Source'} (throttledlog:104) 2021-05-27 17:10:37,186+0000 INFO (jsonrpc/5) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:10:41,120+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:41,120+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 200.037 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:51,121+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:51,121+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 210.039 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:52,211+0000 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:11:01,123+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:11:01,123+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 220.041 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814)ats return={'86245648-abd8-46e3-9c10-432e8788a074': {'code': 0, 'lastCheck': '1.6', 'delay': '0.00353497', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=::1,35010, task_id=c4e65f55-1367-41d3-9bf6-f357a382df4a (api:54) 2021-05-27 17:09:33,156+0000 INFO (jsonrpc/2) [api.host] START getStats() from=::ffff:10.11.0.219,54952 (api:48)

1 2

Ovirt 4.4.6.8-1 upload ova as template to multiple hosts
by Don Dupuis 27 May '21

27 May '21

I have a single ovirt manager and 2 ovirt hosts, each has a local storage domain. I am using the upload_ova_as_template.py and my template upload works on a single host but not both. If I use the gui method, there is the option of "clone" and putting in a new name for the template. This seems to work most of the time, but it has failed a couple of times also. I would like to add the same "clone" and "name" option to the upload_ova_as_temple.py. What is the best way to do this since I need to have unique UUIDs for the template disks? This is a unique setup in the fact that I can't use shared storage and this should be doable as I was able to do it in the ovirt gui. Thanks Don

2 7

what does dwh db contain?
by Nathanaël Blanchet 27 May '21

27 May '21

Hello, I need to understand which user removed a vm 2 months ago, but I can't recover such info into engine.log (that default rotate is 20). I gave a quick look to the dwh database: I'm able to find the removal date, but not the associated user. Is there a way to get this information? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0

Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by Jeff Bailey 27 May '21

27 May '21

If it's the same problem that I ran into then it's the latest version of edk2-ovmf. I'm not sure why it was pushed into the repos without a fixed libvirt to go with it. On 5/25/2021 7:20 AM, Nur Imam Febrianto wrote: > > Hi, > > This morning I have a problem that suddenly my Host (Using Centos 8 > Stream, not oVirt Node) showing error with Cpu Compatibility. It says > my CPU doesn’t have Haswell-noTSX and spec_ctrl flag. After > downgrading the kernel back from 4.18.0 – 305 to 4.18.0 – 301.1 and > rollback yum update, it working again. Do anybody having same issue ? > > I’m using Xeon E5-2695v4 with cluster compatibility Secure Intel > Haswell. Using oVirt 4.4.6 on CentOS Stream host. > > Thanks before. > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7R7SFBOPQL5S6…

4 7

Live ("any") disk migration between storages KILLS a virtual machine with Windows (UEFI) !!!
by Patrick Lomakin 27 May '21

27 May '21

The weekend went horribly. I created a second storage domain in order to move all the virtual machines to a higher performance RAID array (From RAID6 to RAID10). My mistake was trying to move two Windows domain controllers from one storage domain to another. The problem is that when I "live" moved the virtual machine disk between storage domains, my Windows Server 2019 virtual machines worked fine until the next reboot. After a reboot, the machine just won't start and throws an error - Status: 0xc0000428 - The digital signature for this file couldn't be verified. Moving back to the "old" domain doesn't help. None of the procedures with VMs worked (Re-create boot area, turn on kernel flag - bcdedit.exe /set nointegritychecks on). I am ready to help and interested in developing Ovirt. I can also provide more information to developers if needed.

3 5

Re: Parent checkpoint ID does not match the actual leaf checkpoint
by Nir Soffer 27 May '21

27 May '21

On Sun, Jul 19, 2020 at 5:38 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > Thanks to previous answers, I was able to make backups. Unfortunately, we > had some infrastructure issues and after the host reboots new problems > appeared. I am not able to do any backup using the commands that worked > yesterday. I looked through the logs and there is something like this: > > 2020-07-17 15:06:30,644+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-54) > [944a1447-4ea5-4a1c-b971-0bc612b6e45e] Failed to execute VM backup > operation 'StartVmBackup': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to StartVmBackupVDS, error = > Checkpoint Error: {'parent_checkpoint_id': None, 'leaf_checkpoint_id': > 'cd078706-84c0-4370-a6ec-654ccd6a21aa', 'vm_id': > '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', 'reason': '*Parent checkpoint ID > does not match the actual leaf checkpoint*'}, code = 1610 (Failed with > error unexpected and code 16) > > It looks like engine sent: parent_checkpoint_id: None This issue was fix in engine few weeks ago. Which engine and vdsm versions are you testing? > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performVmBackupOperation(StartVmBackupCommand.java:368) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.runVmBackup(StartVmBackupCommand.java:225) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performNextOperation(StartVmBackupCommand.java:199) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at > java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > > > And the last error is: > > 2020-07-17 15:13:45,835+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-14) > [f553c1f2-1c99-4118-9365-ba6b862da936] Failed to execute VM backup > operation 'GetVmBackupInfo': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to GetVmBackupInfoVDS, error > = No such backup Error: {'vm_id': '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', > 'backup_id': 'bf1c26f7-c3e5-437c-bb5a-255b8c1b3b73', 'reason': '*VM > backup not exists: Domain backup job id not found: no domain backup job > present'*}, code = 1601 (Failed with error unexpected and code 16) > > This is likely a result of the first error. If starting backup failed the backup entity is deleted. > (these errors are from full backup) > > Like I said this is very strange because everything was working correctly. > > > Regards > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/S3PLYPOZGT6TL… >

3 4

Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by k.gunasekhar＠non.keysight.com 27 May '21

27 May '21

I also end up with the same problem today. How did rollback yum i see many yum updates in the yum history. Here is what the error says. The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_IvyBridge, spec_ctrl. Please update the host CPU microcode or change the Cluster CPU Type.

2 1

Adding a 4th compute host to a HCI environment
by David White 27 May '21

27 May '21

Hello, Is there documentation anywhere for adding a 4th compute-only host to an existing HCI cluster? I did the following earlier today: - Installed RHEL 8.4 onto the new (4th) host - Setup an NFS share on the host - Attached the NFS share to oVirt as a new storage domain - I then turned the NFS share into a "backup domain" - Once that was done, I installed ovirt-release44.rpm, followed by some ovirt packages: - yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - yum install cockpit-ovirt-dashboard vdsm-gluster ovirt-host - I then logged into the oVirt Manager Web UI, navigated to Hosts, and clicked on New - I successfully added the new host to the cluster Once this was all done, load average on all 3 of my original HCI nodes started to go through the roof. I've seen servers' load average go through the roof before when NFS shares are down, so I suspect that something happened to the NFS share when I went to add the host as a compute node. In an effort to get things stabilized, I wound up yanking the new host out of oVirt, as well as the NFS share, at which point things did stabilize again. My goal here: - Setup the host as a compute-only host (don't participate in the gluster cluster) - Setup the NFS share for backup purposes Writing this email and reviewing my bash history, I think one of the places I went wrong was I installed vdsm-gluster. I don't think I need that, do I? Is what I'm trying to do possible? Sent with ProtonMail Secure Email.

1 0

Guest CPU compatibility issues on upgraded host - RHEL 8
by David White 27 May '21

27 May '21

I have oVirt 4.4.6 running on my Engine VM. I also have oVirt 4.4.6 on one of my hosts. The other two hosts are still on oVirt 4.4.5. My issue seems slightly different than the issue(s) other people have described. I'm on RHEL 8 hosts. My Engine VM is running fine on the upgraded host, as is one of my Ubuntu guests. However, it seems like I'm not able to migrate *ANY* other guests over the new host. The oVirt UI just indicates that for whatever reason the upgraded host isn't available / compatible for a VM to be migrated to. I'm not sure how or why this 1 Ubuntu guest VM was able to get migrated, but it looks like its working just fine. I did try: yum downgrade edk2-ovmf Base on other people's comments. But I'm not sure how long to wait, or what else to try, to try to get my upgraded host operational again. Sent with ProtonMail Secure Email.

1 1

issue creating disk with rest api using json format
by Pascal D 26 May '21

26 May '21

I am unable to create disk using JSON however the same query in XML works great. In Json I get the following message back: { "detail": "For correct usage, see: https://ov1.butterflyit.com/ovirt-engine/apidoc#services/disks/methods/add", "reason": "Request syntactically incorrect." } Both use POST /ovirt-engine/api/disks and the content-type is either application/json or application/xml Here is the request in JSON: { "id": "866770c3-acf9-4f67-b72c-05ed241908e4", "name": "mydisk", "description": "test disk", "bootable": false, "shareable": true, "provisioned_size": 10240000000, "interface": "virtio", "format": "cow", "storage_domains": { "storage_domain": { "name": "VMS" } } } And here it is in XML <disk id="866770c3-acf9-4f67-b72c-05ed241908e4"> <bootable>false</bootable> <name>mydisk</name> <description>test Drive</description> <interface>virtio</interface> <provisioned_size>10240000000</provisioned_size> <format>cow</format> <storage_domains> <storage_domain> <name>VMS</name> </storage_domain> </storage_domains> </disk>

2 2

Ovirt 4.4.6.8 High Performance VM quirkiness
by Don Dupuis 26 May '21

26 May '21

I created a high performance vm and everything is fine. I stop the virtual machine and make edits to it and again runs correctly. I shutdown the vm and click the edit tab to look at what I changed and it is now back to the defaults and my edits are gone. Is this now the intended result. I was using the same settings in 4.3 and never exhibited this behavior. What I have observed so for is that I disabled Headless, disabled cpu pinning, and changed numa config. When I shutdown the vm, they revert to default of Headless enabled, cpu pinning is set and the numa config changed. This is not what I expect to happen. Has anyone else noticed this behavior? Thanks Don

2 3

Centos 8 to Centos Stream
by nikkognt＠gmail.com 26 May '21

26 May '21

Hi, in preparation for upgrade of stand alone engine from centos 8 to centos stream, I would like to know if exist a procedure to follow for this operation or I must only follow the instruction on CentOS official site. [1] Best regards Nikkognt [1] https://www.centos.org/centos-stream/

3 5

Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by nsurma＠provmed.net 25 May '21

25 May '21

Hello, I am also having the same issue after upgrading today but with the skylake CPU. Message states the following flag model_Skylake-Server-noTSX-IBRS is missing. Also running Centos 8 stream not the ovirt node. Thanks

1 0

CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by Nur Imam Febrianto 25 May '21

25 May '21

Hi, This morning I have a problem that suddenly my Host (Using Centos 8 Stream, not oVirt Node) showing error with Cpu Compatibility. It says my CPU doesn’t have Haswell-noTSX and spec_ctrl flag. After downgrading the kernel back from 4.18.0 – 305 to 4.18.0 – 301.1 and rollback yum update, it working again. Do anybody having same issue ? I’m using Xeon E5-2695v4 with cluster compatibility Secure Intel Haswell. Using oVirt 4.4.6 on CentOS Stream host. Thanks before. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

1 0

Re: Import Ge0-Replicated Storage Domain fails
by Simon Scott 25 May '21

25 May '21

Just to clarify... Site A has volume data2 which geo-replicates to Site B Site B has volume data1 which geo-replicates to Site A I will look at the engine upgrade and ansible today.

2 1

Cluster stuck in maintenance - Hosts not upgrading as expected
by David White 24 May '21

24 May '21

I have a 3-node hyperconverged cluster with Gluster filesystem running on RHEL 8.3 hosts. It's been stable on oVirt 4.5. Today, I just upgraded the Engine to v4.6. [Screenshot from 2021-05-22 20-29-23.png] I then logged into the oVirt manager, navigated to Compute -> Clusters, and clicked on Upgrade. The Status of the cluster does have an exclamation mark that says "Upgrade Cluster Compatibility Level", but my understanding is, I shouldn't do that until all 3 of my hosts have been upgraded. Looking at active tasks, I see that the first host in my cluster is stuck in "Upgrading". It's now been like this for 3 hours, without any visible progress. If I try to launch a VM that is not configured for high availability, the VM fails to launch, and I get a message about the cluster being in "Maintenance Mode" and that none of the hosts satisfies current scheduling restraints. How do I.... a) Cancel / clear the upgrade and take the cluster out of "maintenance mode" b) Properly upgrade the cluster, since clicking the "Upgrade" button clearly didn't work? Thanks, David Sent with ProtonMail Secure Email.

4 4

What software used to take forever incremental backup from VM?
by annieblackwell77＠gmail.com 24 May '21

24 May '21

Hi there, I want forever incremental backup for over 150+ virtual machines inside oVirt to save more backup space, then restore in case some problem occurs, any good advice?

8 9

cleanup does not cleanup
by lejeczek 24 May '21

24 May '21

Hi guys. -> $ ovirt-hosted-engine-cleanup -q says it ran its stuff, done & dusted yet I see 'ovirtmgmt' bridge remains. Would that be a bug and how to clean it? many thanks, L.

3 3

Problems provisioning 4.4.6 hosted engine
by Sketch 23 May '21

23 May '21

This is a new system is CentOS 8.3, with the oVirt-4.4 repo and all updates applied. When I try to install the hosted engine with my engine backup from 4.3.10, the installation fails with a too many open files error. My 8.3 hosts already had 1M system max files, which is more than any of my CentOS 7/oVirt 4.3 hosts have. I tried increasing it to 2M with no luck, so my suspicion is that the error is on the engine itself? I tried provisioning a new engine just to test, and I get SSH key errors instead of this one. Any suggestions? 2021-05-12 23:09:44,731-0700 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "exception": "Traceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/ansible/executor/task_executor.py\", line 665, in _execute\n result = self._handler.run(task_vars=variables)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/wait_for_connection.py\", line 122, in run\n self._remove_tmp_path(self._connection._shell.tmpdir)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/__init__.py\", line 417, in _remove_tmp_path\n tmp_rm_res = self._low_level_execute_command(cmd, sudoable=False)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/__init__.py\", line 1085, in _low_level_execute_command\n rc, stdout, stderr = self._connection.exec_command(cmd, in_data=in_data, sudoable=sudoable)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/connection/ssh.py\", line 1191, in exec_command\n cmd = self._build_command(*args)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/connection/s sh.py\", line 562, in _build_command\n self.sshpass_pipe = os.pipe()\nOSError: [Errno 24] Too many open files\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/ansible/executor/task_executor.py\", line 147, in run\n res = self._execute()\n File \"/usr/lib/python3.6/site-packages/ansible/executor/task_executor.py\", line 673, in _execute\n self._handler.cleanup()\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/__init__.py\", line 128, in cleanup\n self._remove_tmp_path(self._connection._shell.tmpdir)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/__init__.py\", line 417, in _remove_tmp_path\n tmp_rm_res = self._low_level_execute_command(cmd, sudoable=False)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/action/__init__.py\", line 1085, in _low_level_execute_command\n rc, stdout, stderr = self._connection.exec_command (cmd, in_data=in_data, sudoable=sudoable)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/connection/ssh.py\", line 1191, in exec_command\n cmd = self._build_command(*args)\n File \"/usr/lib/python3.6/site-packages/ansible/plugins/connection/ssh.py\", line 562, in _build_command\n self.sshpass_pipe = os.pipe()\nOSError: [Errno 24] Too many open files\n", "msg": "Unexpected failure during module execution.", "stdout": "" }, "ansible_task": "Wait for the local VM", "ansible_type": "task", "status": "FAILED", "task_duration": 3605 }

3 2

Import to VMware
by Darin Schmidt 21 May '21

21 May '21

Hello, Ive exported an OVA of a server we had made on OVIRT and Im trying to import it to VMware. Its complaining that the ovf:format is incorrect. ovf:format="http://www.gnome.org/~markmc/qcow-image-format.html" That link doesnt resolve to anywhere because it appears its now http://people.gnome.org/~markmc/qcow-image-format.html But I dont know whats supposed to go there nor have I been able to locate anything to help solve this issue. All I really need is access to the files in the, what I assume is, vdmk file that comes along with the ovf file, which mine is called: 154b3d77-d340-4d24-a448-66265c5fb613 So if anything, is there a way to open this vm disk so I can gain access to the files? Thanks

4 10

Error Adding host to cluster
by David Johnson 20 May '21

20 May '21

When I attempt to install a new host to my cluster from the GUI I get this set of errors/warnings, and the install fails. - Host has no default route - The Host CPU does not match the Cluster CPU Tye and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Cascadelake-Server-noTSX. The new host has a brand new bare centos 8 installation on it. It successfully installed from the internet. The *new host* hardware is 48x Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz The *pre-existing host* is 64x Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz If I am reading the ansible logs correctly, ansible is failing to find the *ovirt-hosted-engine-setup* package, which is confusing since I have a separate physical machine for the engine (which I am using to install from), and don't want a self hosted engine. Any advice would be welcome. --- Ansible logs from the most recent failed installation attempt: 2021-05-14 20:18:04,949 - runner_service.services.playbook - DEBUG - cb_event_handler event_data={'uuid': 'fa961926-9a3a-4d9e-a6bf-d53f98645af2', 'counter': 52, 'stdout': 'fatal: [ ovirt-host-04.maxisinc.net] FAILED! => {"changed": false, "failures": ["No package ovirt-hosted-engine-setup available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}', 'start_line': 44, 'end_line': 45, 'runner_ident': '6060ba26-b51b-11eb-ba6e-d8cb8a87894e', 'event': 'runner_on_failed', 'pid': 1742807, 'created': '2021-05-15T01:18:04.947870', 'parent_uuid': 'd8cb8a87-894e-e341-1e1c-0000000001a1', 'event_data': {'playbook': 'ovirt-host-deploy.yml', 'playbook_uuid': 'e5595457-2c74-4525-8d98-e34bf2e0e342', 'play': 'all', 'play_uuid': 'd8cb8a87-894e-e341-1e1c-000000000007', 'play_pattern': 'all', 'task': 'Install ovirt-hosted-engine-setup package', 'task_uuid': 'd8cb8a87-894e-e341-1e1c-0000000001a1', 'task_action': 'yum', 'task_args': '', 'task_path': '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6', 'role': 'ovirt-host-deploy-vdsm', 'host': 'ovirt-host-04.maxisinc.net', 'remote_addr': 'ovirt-host-04.maxisinc.net', 'res': {'msg': 'Failed to install some of the specified packages', 'failures': ['No package ovirt-hosted-engine-setup available.'], 'results': [], 'rc': 1, 'invocation': {'module_args': {'name': ['ovirt-hosted-engine-setup'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot': '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'lock_timeout': 30, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': False, 'changed': False}, 'start': '2021-05-15T01:18:03.800468', 'end': '2021-05-15T01:18:04.947696', 'duration': 1.147228, 'ignore_errors': None, 'event_loop': None, 'uuid': 'fa961926-9a3a-4d9e-a6bf-d53f98645af2'}} 2021-05-14 20:18:04,951 - runner_service.services.playbook - DEBUG - cb_event_handler event_data={'uuid': '1007f755-dee8-407f-999c-b08c8b813ea7', 'counter': 53, 'stdout': '\r\nPLAY RECAP *********************************************************************\r\ novirt-host-04.maxisinc.net : ok=14 changed=1 unreachable=0 failed=1 skipped=2 rescued=0 ignored=0 \r\n', 'start_line': 45, 'end_line': 49, 'runner_ident': '6060ba26-b51b-11eb-ba6e-d8cb8a87894e', 'event': 'playbook_on_stats', 'pid': 1742807, 'created': '2021-05-15T01:18:04.949918', 'parent_uuid': 'e5595457-2c74-4525-8d98-e34bf2e0e342', 'event_data': {'playbook': 'ovirt-host-deploy.yml', 'playbook_uuid': 'e5595457-2c74-4525-8d98-e34bf2e0e342', 'changed': {' ovirt-host-04.maxisinc.net': 1}, 'dark': {}, 'failures': {' ovirt-host-04.maxisinc.net': 1}, 'ignored': {}, 'ok': {' ovirt-host-04.maxisinc.net': 14}, 'processed': {'ovirt-host-04.maxisinc.net': 1}, 'rescued': {}, 'skipped': {'ovirt-host-04.maxisinc.net': 2}, 'artifact_data': {}, 'uuid': '1007f755-dee8-407f-999c-b08c8b813ea7'}} 2021-05-14 20:18:05,147 - runner_service.services.playbook - INFO - Playbook ovirt-host-deploy.yml, UUID=6060ba26-b51b-11eb-ba6e-d8cb8a87894e ended, status=failed 2021-05-14 20:18:05,154 - runner_service.services.playbook - INFO - Playbook ovirt-host-deploy.yml Stats: {'skipped': {' ovirt-host-04.maxisinc.net': 2}, 'ok': {'ovirt-host-04.maxisinc.net': 14}, 'dark': {}, 'failures': {'ovirt-host-04.maxisinc.net': 1}, 'processed': {' ovirt-host-04.maxisinc.net': 1}, 'changed': {'ovirt-host-04.maxisinc.net': 1}} *David Johnson*

4 8

I am trying to setup ovirt hosted engine.
by Ken.Germann＠L3Harris.com 20 May '21

20 May '21

I select eth2 as the default interface for the management network for the VM network. I get this error: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook It appears to be expecting a bridge interface to be setup... Thank You, Ken Germann UNAP IRAD System Administrator Lead Aviation Systems / l3HARRIS Technologies Office: +1-954-732-0391 / Mobile: +1-954-732-0391 l3harris.com<mailto:l3harris.com> / kgermann(a)l3harris.com<mailto:kgermann@l3harris.com> MS F-11A / 1025 W. Nasa Dr. / Melbourne, FL 32919 / USA [rsz_1harriswebpage_rotator] CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

2 5

error: Engine VM IP address is ... what?
by lejeczek 20 May '21

20 May '21

Hi guys. Would anybody be able to decipher this below? [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is different from engine's he_fqdn resolved IP] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Engine VM IP address is while the engine's he_fqdn buster.private.road resolves to 10.3.1.113. If you are using DHCP, check your DHCP reservation configuration"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook many thanks, L.

2 1

vmfex in 4.4.7
by Michal Skrivanek 20 May '21

20 May '21

Hi there, just a heads up that in 4.4.7 we’ll be removing vdsm’s hard dependency on VM-FEX hook. The functionality has been more or less obsoleted by SR-IOV and its usage is minimal these days. With the upgrade the vdsm-hook-vmfex-dev rpm will get automatically uninstalled. If you happen to use it and it works well for you then please "dnf install" it after the upgrade. There is no change in functionality and the hook is not going away, it’s just that in order to not make it mandatory from now on, it gets removed during "dnf upgrade”. Thanks, michal

1 0

Bridge Setup for Ovirt
by ken＠everheartpartners.com 20 May '21

20 May '21

I have 3 network interfaces eth0 for storage eth1 for public network eth2 for the management network Does someone have the example of how to setup the bridge interface network for the hosted engine setup for Ovir 4.3.10 in my case?

1 0

How to create new users other than admin
by gaurav.gohan＠gmail.com 20 May '21

20 May '21

Hello everyone, I am new to ovirt and would like to apologise if this has been asked before. When I created a cluster of ovirt 4.3, I was presented with the option of creating an admin user. However, we would like to assign different login credentials for our employees with different set of rules. I was able to view the users menu under the Administration > Users. Currently we only have an admin user with internal-authz. When clicking on the add button, I only see "internal-authz" and "*" under namespace. Clicking on Go button simply shows admin user again. I created a new role under the Administration > Configure > Roles, however, there is no option to add new user anywhere. Can you please point me to the right steps for adding new users? Thanks

6 11

Unable start self hosted engine after accidental shut down
by Eugène Ngontang 19 May '21

19 May '21

Hi, Our self hosted engine has been accidentally shut down by a teammate and now I'm trying hard to get it back up without success. I've tried the --vm-start command but it says the VM is in WaitForLaunch status. I've set the global maintenance mode but it does nothing. root@milhouse-main ~]# hosted-engine --vm-start VM exists and is down, cleaning up and restarting VM in WaitForLaunch [root@milhouse-main ~]# hosted-engine --set-maintenance --mode=global [root@milhouse-main ~]# hosted-engine --vm-status !! Cluster is in GLOBAL MAINTENANCE mode !! --== Host milhouse-main.envrmnt.local (id: 1) status ==-- conf_on_shared_storage : True Status up-to-date : False Hostname : milhouse-main.envrmnt.local Host ID : 1 Engine status : unknown stale-data Score : 3400 stopped : False Local maintenance : False crc32 : 931b2db9 local_conf_timestamp : 1642052 Host timestamp : 1642052 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=1642052 (Tue May 18 19:52:59 2021) host-id=1 score=3400 vm_conf_refresh_time=1642052 (Tue May 18 19:53:00 2021) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False !! Cluster is in GLOBAL MAINTENANCE mode !! You have new mail in /var/spool/mail/root [root@milhouse-main ~]# hosted-engine --vm-start VM exists and is down, cleaning up and restarting VM in WaitForLaunch [root@milhouse-main ~]# And when I list all vms, I can see the hosted engine is in the Shut Off status and the managed vms are all paused [root@milhouse-main ~]# virsh -r list --all setlocale: No such file or directory Id Name State ---------------------------------------------------- 2 hp_gpu-node11 paused 3 fp_gpu-node5 paused 4 hp_gpu-node10 paused 5 hp_gpu-node7 paused 6 cpu-node3 paused 7 hp_gpu-node5 paused 8 fp_gpu-node1 paused 9 fp_gpu-node0 paused 10 cpu-node1 paused 11 fp_gpu-node6 paused 12 hp_gpu-node8 paused 13 fp_gpu-node10 paused 14 fp_gpu-node4 paused 15 fp_gpu-node9 paused 16 hp_gpu-node4 paused 17 fp_gpu-node15 paused 18 fp_gpu-node8 paused 19 hp_gpu-node0 paused 20 fp_gpu-node14 paused 21 fp_gpu-node2 paused 22 fp_gpu-node11 paused 23 hp_gpu-node9 paused 24 cpu-node2 paused 25 hp_gpu-node1 paused 26 hp_gpu-node2 paused 27 fp_gpu-node12 paused 28 hp_gpu-node3 paused 29 hp_gpu-node6 paused 30 infra-vm paused 31 cpu-node0 paused 32 fp_gpu-node3 paused 33 fp_gpu-node7 paused 34 fp_gpu-node13 paused 35 bigip-16.1x-milhouse paused - HostedEngine shut off [root@milhouse-main ~]# I don't want to reboot the host server, cause I could loose all my VMs. Can someone help here please? Thanks. Regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

4 4

Error Deployment New Hosted Engine on 4.4.1 node
by Dominique D 19 May '21

19 May '21

I have a setup with 3 servers production environment with version 4.4.1 that works very well (gluster and hosted-engine) I prepared a lab with the same setup (with the same ISO) to test a update to (4.4.6) The deployment of the Hyperconverge works but when I want to do hosted-engine --deploy or in the cokpit, at some time the host displays this message and reboot and the engine is not installed. I tried with the latest ISO 4.4.6 (Fresh Install) and I have the same message. Is there a network change with version 8.3 of CentOS? [ 33.785588] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.787183] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.804832] bondscan-yhEyFK: option arp_validate: invalid value (7) [ 33.807568] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.807884] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode broadcast(3) [ 33.809858] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.811003] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.813490] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.815175] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.839036] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode 802.3ad(4) [ 33.841905] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.842628] bondscan-yhEyFK: option lacp_rate: invalid value (2) [ 33.844573] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.846293] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.847492] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.848978] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.871465] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode balance-tlb(5) [ 33.874149] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.874475] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode balance-tlb(5) [ 33.876514] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.877381] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.878554] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.879991] bondscan-yhEyFK: option arp_all_targets: invalid value (2) [ 33.909461] bondscan-yhEyFK: option arp_validate: mode dependency failed, not supported in mode balance-alb(6) [ 33.914593] bondscan-yhEyFK: option xmit_hash_policy: invalid value (6) [ 33.916657] bondscan-yhEyFK: option lacp_rate: mode dependency failed, not supported in mode balance-alb(6) [ 33.920665] bondscan-yhEyFK: option ad_select: invalid value (3) [ 33.927749] bondscan-yhEyFK: option primary_reselect: invalid value (3) [ 33.932404] bondscan-yhEyFK: option fail_over_mac: invalid value (3) [ 33.935589] bondscan-yhEyFK: option arp_all_targets: invalid value(2)

3 5

Gluster volumes not healing (perhaps after host maintenance?)
by David White 18 May '21

18 May '21

I discovered that the servers I purchased did not come with 10Gbps network cards, like I thought they did. So my storage network has been running on a 1Gbps connection for the past week, since I deployed the servers into the datacenter a little over a week ago. I purchased 10Gbps cards, and put one of my hosts into maintenance mode yesterday, prior to replacing the daughter card. It is now back online running fine on the 10Gbps card. All VMs seem to be working, even when I migrate them onto cha2, which is the host I did maintenance on yesterday morning. The other two hosts are still running on the 1Gbps connection, but I plan to do maintenance on them next week. The oVirt manager shows that all 3 hosts are up, and that all of my volumes - and all of my bricks - are up. However, every time I look at the storage, it appears that the self-heal info for 1 of the volumes is 10 minutes, and the self-heal info for another volume is 50+ minutes. This morning is the first time in the last couple of days that I've paid close attention to the numbers, but I don't see them going down. When I log into each of the hosts, I do see everything is connected in gluster. It is interesting to me, in this particular case, though that gluster on cha3 notices the hostname of 10.1.0.10 to be the IP address, and not the hostname (cha1). The host that I did the maintenance on is cha2. [root@cha3-storage dwhite]# gluster peer statusNumber of Peers: 2Hostname: 10.1.0.10Uuid: 87a4f344-321a-48b9-adfb-e3d2b56b8e7bState: Peer in Cluster (Connected)Hostname: cha2-storage.mgt.barredowlweb.comUuid: 93e12dee-c37d-43aa-a9e9-f4740b9cab14State: Peer in Cluster (Connected) When I run `gluster volume heal data`, I see the following: [root@cha3-storage dwhite]# gluster volume heal data Launching heal operation to perform index self heal on volume data has been unsuccessful: Commit failed on cha2-storage.mgt.barredowlweb.com. Please check log file for details. I get the same results if I run the command on cha2, for any volume: [root@cha2-storage dwhite]# gluster volume heal data Launching heal operation to perform index self heal on volume data has been unsuccessful: Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details. [root@cha2-storage dwhite]# gluster volume heal vmstore Launching heal operation to perform index self heal on volume vmstore has been unsuccessful: Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details. I see a lot of stuff like this on cha2 /var/log/glusterfs/glustershd.log: [2021-04-24 11:33:01.319888] I [rpc-clnt.c:1975:rpc_clnt_reconfig] 2-engine-client-0: changing port to 49153 (from 0)[2021-04-24 11:33:01.329463] I [MSGID: 114057] [client-handshake.c:1128:select_server_supported_programs] 2-engine-client-0: Using Program [{Program-name=GlusterFS 4.x v1}, {Num=1298437}, {Version=400}][2021-04-24 11:33:01.330075] W [MSGID: 114043] [client-handshake.c:727:client_setvolume_cbk] 2-engine-client-0: failed to set the volume [{errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.330116] W [MSGID: 114007] [client-handshake.c:752:client_setvolume_cbk] 2-engine-client-0: failed to get from reply dict [{process-uuid}, {errno=22}, {error=Invalid argument}][2021-04-24 11:33:01.330140] E [MSGID: 114044] [client-handshake.c:757:client_setvolume_cbk] 2-engine-client-0: SETVOLUME on remote-host failed [{remote-error=Brick not found}, {errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.330155] I [MSGID: 114051] [client-handshake.c:879:client_setvolume_cbk] 2-engine-client-0: sending CHILD_CONNECTING event [][2021-04-24 11:33:01.640480] I [rpc-clnt.c:1975:rpc_clnt_reconfig] 3-vmstore-client-0: changing port to 49154 (from 0)The message "W [MSGID: 114007] [client-handshake.c:752:client_setvolume_cbk] 3-vmstore-client-0: failed to get from reply dict [{process-uuid}, {errno=22}, {error=Invalid argument}]" repeated 4 times between [2021-04-24 11:32:49.602164] and [2021-04-24 11:33:01.649850][2021-04-24 11:33:01.649867] E [MSGID: 114044] [client-handshake.c:757:client_setvolume_cbk] 3-vmstore-client-0: SETVOLUME on remote-host failed [{remote-error=Brick not found}, {errno=2}, {error=No such file or directory}][2021-04-24 11:33:01.649969] I [MSGID: 114051] [client-handshake.c:879:client_setvolume_cbk] 3-vmstore-client-0: sending CHILD_CONNECTING event [][2021-04-24 11:33:01.650095] I [MSGID: 114018] [client.c:2225:client_rpc_notify] 3-vmstore-client-0: disconnected from client, process will keep trying to connect glusterd until brick's port is available [{conn-name=vmstore-client-0}] How do I further troubleshoot? Sent with ProtonMail Secure Email.

3 5

Re: Gluster Geo-Replication Fails
by Strahil Nikolov 18 May '21

18 May '21

Now to make it perfect , leave it running and analyze the AVCs with semanage. In the end SELINUX will remain working and geo-rep should be running also. I've previously tried the rpm generated from https://github.com/gluster/glusterfs-selinux but it didn't help at that time. If possible, give it a try. Best Regards,Strahil Nikolov On Tue, May 18, 2021 at 16:09, Simon Scott<simon(a)justconnect.ie> wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GB23MBKEQKZNK…

1 0

Re: oVirt deploy new HE Host problem
by Yedidyah Bar David 18 May '21

18 May '21

On Mon, May 17, 2021 at 10:34 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > Hi gentleman, > > > > Hope you had a great weekend. > > Can I assume that you will be able to look into log files this week ? > > > > As per Yedidyah’s comment, I stopped troubleshooting . > > > > Kindly awaiting your reply. Hi Marko, Please upload somewhere all of /var/log from all hosts and the engine, and share a link. Thanks. In particular, you didn't include 'hosted-engine --deploy' logs from /var/log/ovirt-hosted-engine-setup. Also: the attached ovirt-host-deploy log indicates this is on 4.3, which is EOL and unsupported. Best regards, -- Didi

2 1

Gluster Geo-Replication Fails
by simon＠justconnect.ie 18 May '21

18 May '21

Hi All, I have to sites each with 2 x 3 Node clusters. oVirt 4.4.5 with GlusterFS 8.4. On Site A I have a Replica 3 + Arbiter volume that I want to geo-replicate to Site B. I've setup a Replica 3 + Arbiter volume on Site B. All password-less ssh requirements are in place and the Geo-Replication Session has been created successfully. I issue the 'Start' command successfully but the status switches between 'Initializing', 'Active' & 'Failed' within 20 seconds constantly. Can anyone point me in the direction to get this up and running as it is our proposed DR solution. Kind Regards Shimme

3 3

poweroff and reboot with ovirt_vm ansible module
by Nathanaël Blanchet 18 May '21

18 May '21

Hello, is there a way to poweroff or reboot (without stopped and running state) a vm with the ovirt_vm ansible module? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 11

[ANN] Async release for oVirt 4.4.6
by Lev Veyde 18 May '21

18 May '21

oVirt 4.4.6 Async update #3 On May 18th 2021 the oVirt project released an async update to the following packages: - Vdsm 4.40.60.7 - oVirt Node 4.4.6.3 Fixing the following bugs: - Bug 1959945 <https://bugzilla.redhat.com/show_bug.cgi?id=1959945> - [NBDE] RHVH 4.4.6 host fails to startup, without prompting for passphrase - Bug 1955571 <https://bugzilla.redhat.com/show_bug.cgi?id=1955571> - Verify if we still need to omit ifcfg and clevis dracut modules for properly working bridged network - Bug 1950209 <https://bugzilla.redhat.com/show_bug.cgi?id=1950209> - Leaf images used by the VM is deleted by the engine during snapshot merge oVirt Node Changes: - Consume above oVirt updates - Updated to Gluster 8.5 <https://docs.gluster.org/en/latest/release-notes/8.5/> Full diff list: --- ovirt-node-ng-image-4.4.6.2.manifest-rpm 2021-05-14 08:58:12.581488678 +0200 +++ ovirt-node-ng-image-4.4.6.3.manifest-rpm 2021-05-18 13:09:07.858527812 +0200 @@ -220,7 +220,7 @@ -glusterfs-8.4-1.el8.x86_64 -glusterfs-cli-8.4-1.el8.x86_64 -glusterfs-client-xlators-8.4-1.el8.x86_64 -glusterfs-events-8.4-1.el8.x86_64 -glusterfs-fuse-8.4-1.el8.x86_64 -glusterfs-geo-replication-8.4-1.el8.x86_64 -glusterfs-server-8.4-1.el8.x86_64 +glusterfs-8.5-1.el8.x86_64 +glusterfs-cli-8.5-1.el8.x86_64 +glusterfs-client-xlators-8.5-1.el8.x86_64 +glusterfs-events-8.5-1.el8.x86_64 +glusterfs-fuse-8.5-1.el8.x86_64 +glusterfs-geo-replication-8.5-1.el8.x86_64 +glusterfs-server-8.5-1.el8.x86_64 @@ -383,6 +383,6 @@ -libgfapi0-8.4-1.el8.x86_64 -libgfchangelog0-8.4-1.el8.x86_64 -libgfrpc0-8.4-1.el8.x86_64 -libgfxdr0-8.4-1.el8.x86_64 -libglusterd0-8.4-1.el8.x86_64 -libglusterfs0-8.4-1.el8.x86_64 +libgfapi0-8.5-1.el8.x86_64 +libgfchangelog0-8.5-1.el8.x86_64 +libgfrpc0-8.5-1.el8.x86_64 +libgfxdr0-8.5-1.el8.x86_64 +libglusterd0-8.5-1.el8.x86_64 +libglusterfs0-8.5-1.el8.x86_64 @@ -643 +643 @@ -ovirt-node-ng-image-update-placeholder-4.4.6.2-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.6.3-1.el8.noarch @@ -651,2 +651,2 @@ -ovirt-release-host-node-4.4.6.2-1.el8.noarch -ovirt-release44-4.4.6.2-1.el8.noarch +ovirt-release-host-node-4.4.6.3-1.el8.noarch +ovirt-release44-4.4.6.3-1.el8.noarch @@ -754 +754 @@ -python3-gluster-8.4-1.el8.x86_64 +python3-gluster-8.5-1.el8.x86_64 @@ -940,15 +940,15 @@ -vdsm-4.40.60.6-1.el8.x86_64 -vdsm-api-4.40.60.6-1.el8.noarch -vdsm-client-4.40.60.6-1.el8.noarch -vdsm-common-4.40.60.6-1.el8.noarch -vdsm-gluster-4.40.60.6-1.el8.x86_64 -vdsm-hook-ethtool-options-4.40.60.6-1.el8.noarch -vdsm-hook-fcoe-4.40.60.6-1.el8.noarch -vdsm-hook-openstacknet-4.40.60.6-1.el8.noarch -vdsm-hook-vhostmd-4.40.60.6-1.el8.noarch -vdsm-hook-vmfex-dev-4.40.60.6-1.el8.noarch -vdsm-http-4.40.60.6-1.el8.noarch -vdsm-jsonrpc-4.40.60.6-1.el8.noarch -vdsm-network-4.40.60.6-1.el8.x86_64 -vdsm-python-4.40.60.6-1.el8.noarch -vdsm-yajsonrpc-4.40.60.6-1.el8.noarch +vdsm-4.40.60.7-1.el8.x86_64 +vdsm-api-4.40.60.7-1.el8.noarch +vdsm-client-4.40.60.7-1.el8.noarch +vdsm-common-4.40.60.7-1.el8.noarch +vdsm-gluster-4.40.60.7-1.el8.x86_64 +vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch +vdsm-hook-fcoe-4.40.60.7-1.el8.noarch +vdsm-hook-openstacknet-4.40.60.7-1.el8.noarch +vdsm-hook-vhostmd-4.40.60.7-1.el8.noarch +vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch +vdsm-http-4.40.60.7-1.el8.noarch +vdsm-jsonrpc-4.40.60.7-1.el8.noarch +vdsm-network-4.40.60.7-1.el8.x86_64 +vdsm-python-4.40.60.7-1.el8.noarch +vdsm-yajsonrpc-4.40.60.7-1.el8.noarch -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Ovirt Engine -- Connection Refused to all hosts
by Nick Polites 18 May '21

18 May '21

Hi All, I am not sure if my original post is being reviewed before posting but trying again in case it failed to send. I tried logging in this morning to oVrit and see that all of my hosts are unresponsive. I am seeing a connection refused error in the engine logs. I am able to SSH and ping the host from the engine. Any help would be appreciated. 2021-05-15 15:19:21,041Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [] Command 'GetCapabilitiesAsyn cVDSCommand(HostName = hlkvm03, VdsIdAndVdsVDSCommandParametersBase:{hostId='2186eca7-4d9d-482f-b1b7-b63ac46b96aa', vds='Host[hlkvm03,2186eca7-4d9d-482f-b1b7 -b63ac46b96aa]'})' execution failed: java.net.ConnectException: Connection refused ~

3 2

Migrating VMs with templates from 4.2.8 to new 4.4.6 instance
by Pavel Strzinek 17 May '21

17 May '21

Hello, I am having hard time migrating vms based on templates from existing 4.2.8 instance to newly installed 4.4.6 HCI with different storage. When I export VMs and corresponding templates to export NFS storage, detach it from source DC and attach the export storage to a new oVirt environment, the import of templates is failing with error "Failed to import Template XXX to Data Center YYY, Cluster ZZZ". I cannot find anything more specific about the error in logs. Am I missing something? Exporting to OVA and importing back does work, but I want to make use of template thin provisioning.

2 3

oVirt 2021 Spring survey
by Sandro Bonazzola 17 May '21

17 May '21

As we continue to develop oVirt 4.4, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. Please help us to hit the mark by completing this short survey. Survey will close on *May 30th 2021*. If you're managing multiple oVirt deployments with very different use cases or very different deployments you can consider answering this survey multiple times. *Please note the answers to this survey will be publicly accessible*. This survey is under oVirt Privacy Policy available at https://ovirt.org/privacy-policy.html . The survey form is available at https://docs.google.com/forms/d/e/1FAIpQLScdJGoBYxuW-4IsIvZGVpbiEWhmt4O-oAA… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

Re: oVirt deploy new HE Host problem
by Strahil Nikolov 17 May '21

17 May '21

Yes, I did - but I couldn't take a look into them. Best Regards,Strahil Nikolov On Mon, May 10, 2021 at 13:54, Marko Vrgotic<M.Vrgotic(a)activevideo.com> wrote: _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KJCGYLJK4ILZ5…

2 1

Create Brick from Engine host view
by Harry O 16 May '21

16 May '21

When I try to create a single disk brick via host view "storage devices" on engine, I get the following error. Error while executing action Create Brick: Internal Engine Error Failed to create brick lalaf on host hej1.5ervers.lan of cluster Clu1. I want the brick to be single disk no raid, no cache. Is there a way to create it via CLI? Do I need to pull some logs?

2 1

Power management on Dell PowerEdge R320 and R520
by Pavel Strzinek 14 May '21

14 May '21

Hello, I am having trouble configuring fencing on these two servers with iDrac7 module from freshly installed oVirt 4.4.6. I tried drac5, drac7 and ipmilan modules and neither passes the test. I used ipmilan with option "lanplus=1", as noted in previous threads about idrac usage with oVirt/RHEV, but with no success. Also, I am successfully using ipmilan fencing from older oVirt 4.2 on several SuperMicro server nodes. This is the error message in engine.log: 2021-05-14 09:28:41,185+02 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-6) [12faf352-da4a-4b24-9ab9-af54559cecd1] Can not run fence action on host 'onode1', no suitable proxy host was found. I can successfully query the idrac module with ipmitool from command line on the node, using the same credentials.

3 4

[ANN] Async release for oVirt 4.4.6
by Sandro Bonazzola 14 May '21

14 May '21

On May 14th 2021 the oVirt project released an async update to the following packages: - ovirt-hosted-engine-ha-2.4.7 - ovirt-release44-4.4.6.2 - ovirt-engine-4.4.6.8 - oVirt Node 4.4.6.2 Fixing the following bugs: - Bug 1909888 <https://bugzilla.redhat.com/show_bug.cgi?id=1909888> - [RFE] Support multiple IQN in hosted-engine.conf for Active-Active DR setup - Bug 1957253 <https://bugzilla.redhat.com/show_bug.cgi?id=1957253> - [cinderlib] Enable using Managed Block Storage on 4.6 cluster by default - Bug 1958869 <https://bugzilla.redhat.com/show_bug.cgi?id=1958869> - Import VM from export domain fails - the imported VM remains in 'image locked' state oVirt Node Changes: - Consume above oVirt updates - Updated hivex (CVE-2021-3504 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3504>) Full diff list: *--- ovirt-node-ng-image-4.4.6.1.manifest-rpm* *2021-05-11 08:39:44.714649170 +0200**+++ ovirt-node-ng-image-4.4.6.2.manifest-rpm* *2021-05-14 08:58:12.581488678 +0200*@@ -253 +253 @@-hivex-1.3.18-20.module_el8.5.0+746+bbd5d70c.x86_64+hivex-1.3.18-21.el8s.x86_64@@ -638 +638 @@-ovirt-hosted-engine-ha-2.4.6-1.el8.noarch+ovirt-hosted-engine-ha-2.4.7-1.el8.noarch@@ -643 +643 @@-ovirt-node-ng-image-update-placeholder-4.4.6.1-1.el8.noarch+ovirt-node-ng-image-update-placeholder-4.4.6.2-1.el8.noarch@@ -651,2 +651,2 @@-ovirt-release-host-node-4.4.6.1-1.el8.noarch-ovirt-release44-4.4.6.1-1.el8.noarch+ovirt-release-host-node-4.4.6.2-1.el8.noarch+ovirt-release44-4.4.6.2-1.el8.noarch -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

[OLVM] Host non responsive after installation
by alan＠softdrive.co 12 May '21

12 May '21

I am using Oracle Linux Virtualization Manager, following this guide: https://docs.oracle.com/en/virtualization/oracle-linux-virtualization-manag… After adding a host to the engine, the host becomes non responsive due to network errors: engine.log 2021-04-27 14:53:02,255Z ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-32356) [38586e0e] Host installation failed for host 'c97604b3-5774-4260-92fd-633257aa7498', 'GPU2-2': Network error during communication with the host Help resolving this would be much appreciated!

4 9