- Users - oVirt List Archives

Installed oVirt 4.4.2 on CentOS 8
by info＠worldhostess.com 24 Sep '20

24 Sep '20

New oVirt basic installation on Centos 8 as a physical server. The default Data center in an uninitialized state This is my first working installation and I have no idea what to do next. Anyone knows a step by step guide for fresh install? Any advice will be appreciated.

2 1

oVirt - Gluster Node Offline but Bricks Active
by Jeremey Wise 24 Sep '20

24 Sep '20

oVirt engine shows one of the gluster servers having an issue. I did a graceful shutdown of all three nodes over weekend as I have to move around some power connections in prep for UPS. Came back up.. but.... [image: image.png] And this is reflected in 2 bricks online (should be three for each volume) [image: image.png] Command line shows gluster should be happy. [root@thor engine]# gluster peer status Number of Peers: 2 Hostname: odinst.penguinpages.local Uuid: 83c772aa-33cd-430f-9614-30a99534d10e State: Peer in Cluster (Connected) Hostname: medusast.penguinpages.local Uuid: 977b2c1d-36a8-4852-b953-f75850ac5031 State: Peer in Cluster (Connected) [root@thor engine]# # All bricks showing online [root@thor engine]# gluster volume status Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick thorst.penguinpages.local:/gluster_br icks/data/data 49152 0 Y 11001 Brick odinst.penguinpages.local:/gluster_br icks/data/data 49152 0 Y 2970 Brick medusast.penguinpages.local:/gluster_ bricks/data/data 49152 0 Y 2646 Self-heal Daemon on localhost N/A N/A Y 50560 Self-heal Daemon on odinst.penguinpages.loc al N/A N/A Y 3004 Self-heal Daemon on medusast.penguinpages.l ocal N/A N/A Y 2475 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick thorst.penguinpages.local:/gluster_br icks/engine/engine 49153 0 Y 11012 Brick odinst.penguinpages.local:/gluster_br icks/engine/engine 49153 0 Y 2982 Brick medusast.penguinpages.local:/gluster_ bricks/engine/engine 49153 0 Y 2657 Self-heal Daemon on localhost N/A N/A Y 50560 Self-heal Daemon on odinst.penguinpages.loc al N/A N/A Y 3004 Self-heal Daemon on medusast.penguinpages.l ocal N/A N/A Y 2475 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: iso Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick thorst.penguinpages.local:/gluster_br icks/iso/iso 49156 49157 Y 151426 Brick odinst.penguinpages.local:/gluster_br icks/iso/iso 49156 49157 Y 69225 Brick medusast.penguinpages.local:/gluster_ bricks/iso/iso 49156 49157 Y 45018 Self-heal Daemon on localhost N/A N/A Y 50560 Self-heal Daemon on odinst.penguinpages.loc al N/A N/A Y 3004 Self-heal Daemon on medusast.penguinpages.l ocal N/A N/A Y 2475 Task Status of Volume iso ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick thorst.penguinpages.local:/gluster_br icks/vmstore/vmstore 49154 0 Y 11023 Brick odinst.penguinpages.local:/gluster_br icks/vmstore/vmstore 49154 0 Y 2993 Brick medusast.penguinpages.local:/gluster_ bricks/vmstore/vmstore 49154 0 Y 2668 Self-heal Daemon on localhost N/A N/A Y 50560 Self-heal Daemon on medusast.penguinpages.l ocal N/A N/A Y 2475 Self-heal Daemon on odinst.penguinpages.loc al N/A N/A Y 3004 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks [root@thor engine]# gluster volume heal data engine iso vmstore [root@thor engine]# gluster volume heal data info Brick thorst.penguinpages.local:/gluster_bricks/data/data Status: Connected Number of entries: 0 Brick odinst.penguinpages.local:/gluster_bricks/data/data Status: Connected Number of entries: 0 Brick medusast.penguinpages.local:/gluster_bricks/data/data Status: Connected Number of entries: 0 [root@thor engine]# gluster volume heal engine Launching heal operation to perform index self heal on volume engine has been successful Use heal info commands to check status. [root@thor engine]# gluster volume heal engine info Brick thorst.penguinpages.local:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick odinst.penguinpages.local:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick medusast.penguinpages.local:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 [root@thor engine]# gluster volume heal vmwatore info Volume vmwatore does not exist Volume heal failed. [root@thor engine]# So not sure what to do with oVirt Engine to make it happy again. -- p <jeremey.wise(a)gmail.com>enguinpages

6 20

Gluster Name too long
by Jeremey Wise 24 Sep '20

24 Sep '20

Deployment on three node cluster using oVirt HCI wizard. I think this is a bug where it needs to do either a pre-flight name length validation, or increase valid field length. I avoid using /dev/sd# as those can change. And the wizard allows for this change to a more explicit devices Ex: /dev/mapper/Samsung_SSD_850_PRO_512GB_S250NXAGA15787L Error: TASK [gluster.infra/roles/backend_setup : Create a LV thinpool for similar device types] *** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thin_pool_create.yml:239 failed: [thorst.penguinpages.local] (item={'vgname': 'gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'thinpoolname': 'gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" is too long.\n Full LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" is too long.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tmeta\" length 130 is not supported.\n Internal error: LV name \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L/gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L_tdata\" length 130 is not supported.\n", "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L", "vgname": "gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L"}, "msg": "Creating logical volume 'None' failed", "rc": 5} failed: [medusast.penguinpages.local] (item={'vgname': 'gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306', 'thinpoolname': 'gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Internal error: LV name \"gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306/gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306\" length 130 is not supported.\n", "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306", "vgname": "gluster_vg_SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306"}, "msg": "Creating logical volume 'None' failed", "rc": 5} changed: [odinst.penguinpages.local] => (item={'vgname': 'gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137', 'thinpoolname': 'gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137', 'poolmetadatasize': '3G'}) => {"ansible_loop_var": "item", "changed": true, "item": {"poolmetadatasize": "3G", "thinpoolname": "gluster_thinpool_gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137", "vgname": "gluster_vg_Micron_1100_MTFDDAV512TBN_17401F699137"}, "msg": ""} I will revert back to /dev/sd# for now... but this should be cleaned up. Attached is YAML file for deployment of cluster -- p <jeremey.wise(a)gmail.com>enguinpages

3 2

Host has to be reinstalled
by Jeremey Wise 23 Sep '20

23 Sep '20

Trying to repair / clean up HCI deployment so it is HA and ready for "production". I have gluster now showing three bricks all green Now I just have error on node.. and of course the node which is hosting the ovirt-engine # (as I can not send images to this forum... I will move to a breadcrumb posting) Compute -> Hosts -> "thor" (red exclamation) "Host has to be reinstalled" To fix gluster... i had to reinstall "vdsm-gluster" But what package does this error need to be reviewed / fixed with? -- penguinpages

2 1

CLI for HCI setup
by Michael Thomas 23 Sep '20

23 Sep '20

Is there a CLI for setting up a hyperconverged environment with glusterfs? The docs that I've found detail how to do it using the cockpit interface[1], but I'd prefer to use a cli similar to 'hosted-engine --deploy' if it is available. Thanks, --Mike [1]https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying…

3 2

info on iSCSI connection setup in oVirt 4.4
by Gianluca Cecchi 23 Sep '20

23 Sep '20

Hello, supposing to have a node that connects to an iSCSI storage domain in oVirt 4.4, is there any particular requirement in the configuration of the network adapter (ifcfg-eno1 file) when I pre-configure the server OS? Eg, do I need to have it managed by NetworkManager in 4.4? Can I instead set NM_CONTROLLED=no for this controller? Thanks in advance, Gianluca

3 3

Question on "Memory" column/field in Virtual Machines list/table in ovirt GUI
by KISHOR K 23 Sep '20

23 Sep '20

Hi, Memory field/column for few of VMs in our ovirt (Compute -> Virtual Machines -> Memory column) shows more than 90%. But, when I checked (from free and also other commands) the actual "used" memory by those VMs, it is less than 60%. What I see (from free -h) is that ovirt seems to be considering both "used" + "buff/cache" memory and is reporting the same in GUI. Isn't it the "available" memory that should be considered, because that is the actual memory available and cache memory is something that is adjusted every time? :~> free -h total used free shared buff/cache available Mem: 15Gi 6.8Gi 724Mi 310Mi 8.1Gi 9.2Gi Swap: 0B 0B 0B Can someone help to answer. Thanks ! /Kishore

2 8

console breaks with signed SSL certs
by Philip Brown 23 Sep '20

23 Sep '20

Chrome didnt want to talk AT ALL to ovirt with self-signed certs (Because HSTS is enabled) So I installed signed wildcard certs to the engine, and the nodes, following http://187.1.81.65/ovirt-engine/docs/manual/en-US/html/Administration_Guide… and https://cockpit-project.org/guide/172/https.html and chrome is happy now... except that suddenly, consoles refuse to work. and there are no useful errors that I see, other than "Unable to connect to the graphic server" from the remote viewer app. I see someone not too long ago had the exact same problem, in https://www.mail-archive.com/users@ovirt.org/msg58814.html but.. no answer was given to him? Help please -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

3 6

oVirt - vdo: ERROR - Device /dev/sd excluded by a filter
by Jeremey Wise 22 Sep '20

22 Sep '20

[image: image.png] vdo: ERROR - Device /dev/sdc excluded by a filter [image: image.png] Other server vdo: ERROR - Device /dev/mapper/nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001p1 excluded by a filter. All systems when I go to create VDO volume on blank drives.. I get this filter error. All disk outside of the HCI wizard setup are now blocked from creating new Gluster volume group. Here is what I see in /dev/lvm/lvm.conf |grep filter [root@odin ~]# cat /etc/lvm/lvm.conf |grep filter filter = ["a|^/dev/disk/by-id/lvm-pv-uuid-e1fvwo-kEfX-v3lT-SKBp-cgze-TwsO-PtyvmC$|", "a|^/dev/disk/by-id/lvm-pv-uuid-mr9awW-oQH5-F4IX-CbEO-RgJZ-x4jK-e4YZS1$|", "r|.*|"] [root@odin ~]# ls -al /dev/disk/by-id/ total 0 drwxr-xr-x. 2 root root 1220 Sep 18 14:32 . drwxr-xr-x. 6 root root 120 Sep 18 14:32 .. lrwxrwxrwx. 1 root root 9 Sep 18 22:40 ata-INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 ata-INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 ata-INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 9 Sep 18 14:32 ata-Micron_1100_MTFDDAV512TBN_17401F699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 ata-WDC_WDS100T2B0B-00YS70_183533804564 -> ../../sdc lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-name-cl-home -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-name-cl-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-name-cl-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 11 Sep 18 16:40 dm-name-gluster_vg_sdb-gluster_lv_data -> ../../dm-11 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-name-gluster_vg_sdb-gluster_lv_engine -> ../../dm-6 lrwxrwxrwx. 1 root root 11 Sep 18 16:40 dm-name-gluster_vg_sdb-gluster_lv_vmstore -> ../../dm-12 lrwxrwxrwx. 1 root root 10 Sep 18 23:35 dm-name-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../dm-3 lrwxrwxrwx. 1 root root 10 Sep 18 23:49 dm-name-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001p1 -> ../../dm-4 lrwxrwxrwx. 1 root root 10 Sep 18 14:32 dm-name-vdo_sdb -> ../../dm-5 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-uuid-LVM-GpvYIuypEfrR7nEDn5uHPenKwjrsn4ADc49gc6PWLRBCoJ2B3JC9tDJejyx5eDPT -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-uuid-LVM-GpvYIuypEfrR7nEDn5uHPenKwjrsn4ADOMNJfgcat9ZLOpcNO7FyG8ixcl5s93TU -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-uuid-LVM-GpvYIuypEfrR7nEDn5uHPenKwjrsn4ADzqPGk0yTQ19FIqgoAfsCxWg7cDMtl71r -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Sep 18 16:40 dm-uuid-LVM-ikNfztYY7KGT1SI2WYXPz4DhM2cyTelOq6Om5comvRFWJDbtVZAKtE5YGl4jciP9 -> ../../dm-6 lrwxrwxrwx. 1 root root 11 Sep 18 16:40 dm-uuid-LVM-ikNfztYY7KGT1SI2WYXPz4DhM2cyTelOqVheASEgerWSEIkjM1BR3us3D9ekHt0L -> ../../dm-11 lrwxrwxrwx. 1 root root 11 Sep 18 16:40 dm-uuid-LVM-ikNfztYY7KGT1SI2WYXPz4DhM2cyTelOQz6vXuivIfup6cquKAjPof8wIGOSe4Vz -> ../../dm-12 lrwxrwxrwx. 1 root root 10 Sep 18 23:35 dm-uuid-mpath-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../dm-3 lrwxrwxrwx. 1 root root 10 Sep 18 23:49 dm-uuid-part1-mpath-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../dm-4 lrwxrwxrwx. 1 root root 10 Sep 18 14:32 dm-uuid-VDO-472035cc-8d2b-40ac-afe9-fa60b62a887f -> ../../dm-5 lrwxrwxrwx. 1 root root 10 Sep 18 14:32 lvm-pv-uuid-e1fvwo-kEfX-v3lT-SKBp-cgze-TwsO-PtyvmC -> ../../dm-5 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 lvm-pv-uuid-mr9awW-oQH5-F4IX-CbEO-RgJZ-x4jK-e4YZS1 -> ../../sda2 lrwxrwxrwx. 1 root root 13 Sep 18 14:32 nvme-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Sep 18 14:32 nvme-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 13 Sep 18 14:32 nvme-SPCC_M.2_PCIe_SSD_AA000000000000002458 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Sep 18 14:32 nvme-SPCC_M.2_PCIe_SSD_AA000000000000002458-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-0ATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-0ATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-0ATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 9 Sep 18 14:32 scsi-0ATA_Micron_1100_MTFD_17401F699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-0ATA_WDC_WDS100T2B0B-_183533804564 -> ../../sdc lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-1ATA_INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-1ATA_INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-1ATA_INTEL_SSDSC2BB080G4_BTWL40350DXP080KGN-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 9 Sep 18 14:32 scsi-1ATA_Micron_1100_MTFDDAV512TBN_17401F699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-1ATA_WDC_WDS100T2B0B-00YS70_183533804564 -> ../../sdc lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-35001b448b9608d90 -> ../../sdc lrwxrwxrwx. 1 root root 9 Sep 18 14:32 scsi-3500a07511f699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-355cd2e404b581cc0 -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-355cd2e404b581cc0-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-355cd2e404b581cc0-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Sep 18 23:35 scsi-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../dm-3 lrwxrwxrwx. 1 root root 10 Sep 18 23:49 scsi-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001-part1 -> ../../dm-4 lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-SATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-SATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 scsi-SATA_INTEL_SSDSC2BB08_BTWL40350DXP080KGN-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 9 Sep 18 14:32 scsi-SATA_Micron_1100_MTFD_17401F699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 scsi-SATA_WDC_WDS100T2B0B-_183533804564 -> ../../sdc lrwxrwxrwx. 1 root root 9 Sep 18 22:40 wwn-0x5001b448b9608d90 -> ../../sdc lrwxrwxrwx. 1 root root 9 Sep 18 14:32 wwn-0x500a07511f699137 -> ../../sdb lrwxrwxrwx. 1 root root 9 Sep 18 22:40 wwn-0x55cd2e404b581cc0 -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 18 22:40 wwn-0x55cd2e404b581cc0-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Sep 18 22:40 wwn-0x55cd2e404b581cc0-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Sep 18 23:35 wwn-0xvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 -> ../../dm-3 lrwxrwxrwx. 1 root root 10 Sep 18 23:49 wwn-0xvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001-part1 -> ../../dm-4 lrwxrwxrwx. 1 root root 15 Sep 18 14:32 wwn-nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001-part1 -> ../../nvme0n1p1 [root@odin ~]# ls -al /dev/disk/by-id/ So filter notes three objects: lvm-pv-uuid-e1fvwo.... -> dm-5 ->vdo_sdb (used by HCI for all the three gluster base volumes ) lvm-pv-uuid-mr9awW... -> sda2 -> boot volume [root@odin ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 74.5G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 73.5G 0 part ├─cl-root 253:0 0 44.4G 0 lvm / ├─cl-swap 253:1 0 7.5G 0 lvm [SWAP] └─cl-home 253:2 0 21.7G 0 lvm /home sdb 8:16 0 477G 0 disk └─vdo_sdb 253:5 0 2.1T 0 vdo ├─gluster_vg_sdb-gluster_lv_engine 253:6 0 100G 0 lvm /gluster_bricks/engine ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb_tmeta 253:7 0 1G 0 lvm │ └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb-tpool 253:9 0 2T 0 lvm │ ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb 253:10 0 2T 1 lvm │ ├─gluster_vg_sdb-gluster_lv_data 253:11 0 1000G 0 lvm /gluster_bricks/data │ └─gluster_vg_sdb-gluster_lv_vmstore 253:12 0 1000G 0 lvm /gluster_bricks/vmstore └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb_tdata 253:8 0 2T 0 lvm └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb-tpool 253:9 0 2T 0 lvm ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb 253:10 0 2T 1 lvm ├─gluster_vg_sdb-gluster_lv_data 253:11 0 1000G 0 lvm /gluster_bricks/data └─gluster_vg_sdb-gluster_lv_vmstore 253:12 0 1000G 0 lvm /gluster_bricks/vmstore sdc 8:32 0 931.5G 0 disk nvme0n1 259:0 0 953.9G 0 disk ├─nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 253:3 0 953.9G 0 mpath │ └─nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001p1 253:4 0 953.9G 0 part └─nvme0n1p1 So I don't think this is LVM filtering things Multipath showing weird treatment of the NVMe drive.. but that is outside this converstation [root@odin ~]# multipath -l nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-00000001 dm-3 NVME,SPCC M.2 PCIe SSD size=954G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 0:1:1:1 nvme0n1 259:0 active undef running [root@odin ~]# Where is getting this filter. I have done gdisk /dev/sdc ( new 1TB Drive) and shows no partition. I even did a full dd if=/dev/zero and no change. I reloaded OS on system to get through wizard setup. Now that all three nodes are in the HCI cluster.. all six drives (2 x 1TB in each server) are now locked from any use due to this error about filter. Ideas? -- jeremey.wise(a)gmail.com

5 14

oVirt - KVM QCow2 Import
by Jeremey Wise 22 Sep '20

22 Sep '20

I rebuilt my lab environment. And their are four or five VMs that really would help if I did not have to rebuild. oVirt as I am now finding when it creates infrastructure, sets it out such that I cannot just use older means of placing .qcow2 files in folders and .xml files in other folders.... and they show up on services restarting. How do I import VMs from files? I found this article but implies VM is running: https://www.ovirt.org/develop/release-management/features/virt/KvmToOvirt.h… https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/ht… I need a way to import a file. Even if it means temporarily hosting on "KVM on one of the hosts to then bring in once it is up. Thanks -- penguinpages

4 8

Upgrade Ovirt from 4.2 to 4.4 on CentOS7.4
by tiziano.pacioni＠par-tec.it 22 Sep '20

22 Sep '20

Hi everyone, I am writing for support regarding the ovirt upgrade. I am using Ovirt with version 4.2 on CentOS 7.4 operating system. The latest release of the Ovirt engine is 4.4 which is available for CentOS 8.Can I upgrade without upgrading the operating system to centos8? I would not be wrong but it is not possible to switch from Centos7 to Centos8 .....Can anyone give me some advice?Thank you all!!!

2 1

VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").
by Gilboa Davara 22 Sep '20

22 Sep '20

Hello all (and happy new year), (Note: Also reported as https://bugzilla.redhat.com/show_bug.cgi?id=1880251) Self hosted engine, single node, NFS. Attempted to install CentOS over an existing Fedora VM with one host device (USB printer). Reboot failed, trying to boot from a non-existent CDROM. Tried shutting the VM down, failed. Tried powering off the VM, failed. Dropped cluster to global maintenance, reboot host + engine (was planning to upgrade it anyhow...), VM still stuck. When trying to power off the VM, the following message can be found the in engine.log: 2020-09-18 07:58:51,439+03 INFO [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-42) [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand internal: false. Entities affected : ID: b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with role type USER 2020-09-18 07:58:51,441+03 WARN [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-42) [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the status 'RebootInProgress' virtual machine 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but it isn't. 2020-09-18 07:58:51,594+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-42) [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID: USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host: <UNKNOWN>, User: gilboa@internal-authz). My question is simple: Pending a solution to the bug, can I somehow drop the state of the VM? It's currently holding a sizable disk image and a USB device I need (printer). As it's my private VM cluster, I have no problem dropping the site completely for maintenance. Thanks, Gilboa

4 9

Cannot import VM disks from previously detached storage domain
by Strahil Nikolov 22 Sep '20

22 Sep '20

Hello All, I would like to ask how to proceed further. Here is what I have done so far on my ovirt 4.3.10: 1. Set in maintenance and detached my Gluster-based storage domain 2. Did some maintenance on the gluster 3. Reattached and activated my Gluster-based storage domain 4. I have imported my ISOs via the Disk Import tab in UI Next I tried to import the VM Disks , but they are unavailable in the disk tab So I tried to import the VM: 1. First try - import with partial -> failed due to MAC conflict 2. Second try - import with partial , allow MAC reassignment -> failed as VM id exists -> recommends to remove the original VM 3. I tried to detach the VMs disks , so I can delete it - but this is not possible as the Vm already got a snapshot. What is the proper way to import my non-OS disks (data domain is slower but has more space which is more suitable for "data") ? Best Regards, Strahil Nikolov

2 5

Fail install SHE ovirt-engine from backupfile (4.3 -> 4.4)
by francesco＠shellrent.com 22 Sep '20

22 Sep '20

Hi Everyone, In a test environment I'm trying to deploy a single node self hosted engine 4.4 on CentOS 8 from a 4.3 backup. The actual setup is: - node1 with CentOS7, oVirt 4.3 with a working SH engine. The data domain is a local NFS; - node2 with CentOS8, where we are triyng to deploy the engine starting from the node1 engine backup - host1, with CentOS78, running a couple of VMs (4.3) I'm following the guide: https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_to… Everything seems working fine, the engine on the node1 is in maintenance:global mode and the ovirt-engine service i stopped. The deploy on the node2 stucks in the following error: TASK [ovirt.hosted_engine_setup : Wait for OVF_STORE disk content] [ ERROR ] {'msg': 'non-zero return code', 'cmd': "vdsm-client Image prepare storagepoolID=06c58622-f99b-11ea-9122-00163e1bbc93 storagedomainID=2a4a3cce-f2f6-4ddd-b337-df5ef562f520 imageID=e48a66dd-74c9-43eb-890e-778e9c4ee8db volumeID=06bb5f34-112d-4214-91d2-53d0bdb84321 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 6023764f-5547-4b23-92ca-422eafdf3f87.ovf", 'stdout': '', 'stderr': "vdsm-client: Command Image.prepare with args {'storagepoolID': '06c58622-f99b-11ea-9122-00163e1bbc93', 'storagedomainID': '2a4a3cce-f2f6-4ddd-b337-df5ef562f520', 'imageID': 'e48a66dd-74c9-43eb-890e-778e9c4ee8db', 'volumeID': '06bb5f34-112d-4214-91d2-53d0bdb84321'} failed:\n(code=309, message=Unknown pool id, pool not connected: ('06c58622-f99b-11ea-9122-00163e1bbc93',))\ntar: This does not look like a tar archive\ntar: 6023764f-5547-4b23-92ca-422eafdf3f87.ovf: Not found in archive\ntar: Exiting with failure status due to previous errors", 'rc': 2, 'start': '2020-09-21 17:14:17.293090', 'end': '2020-09-21 17:14:17.644253', 'delta': '0:00:00.351163', 'changed': True, 'failed': True, 'invocation': {'module_args': {'warn': False, '_raw_params': "vdsm-client Image prepare storagepoolID=06c58622-f99b-11ea-9122-00163e1bbc93 storagedomainID=2a4a3cce-f2f6-4ddd-b337-df5ef562f520 imageID=e48a66dd-74c9-43eb-890e-778e9c4ee8db volumeID=06bb5f34-112d-4214-91d2-53d0bdb84321 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 6023764f-5547-4b23-92ca-422eafdf3f87.ovf", '_uses_shell': True, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable ': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ["vdsm-client: Command Image.prepare with args {'storagepoolID': '06c58622-f99b-11ea-9122-00163e1bbc93', 'storagedomainID': '2a4a3cce-f2f6-4ddd-b337-df5ef562f520', 'imageID': 'e48a66dd-74c9-43eb-890e-778e9c4ee8db', 'volumeID': '06bb5f34-112d-4214-91d2-53d0bdb84321'} failed:", "(code=309, message=Unknown pool id, pool not connected: ('06c58622-f99b-11ea-9122-00163e1bbc93',))", 'tar: This does not look like a tar archive', 'tar: 6023764f-5547-4b23-92ca-422eafdf3f87.ovf: Not found in archive', 'tar: Exiting with failure status due to previous errors'], '_ansible_no_log': False, 'attempts': 12, 'item': {'name': 'OVF_STORE', 'image_id': '06bb5f34-112d-4214-91d2-53d0bdb84321', 'id': 'e48a66dd-74c9-43eb-890e-778e9c4ee8db'}, 'ansible_loop_var': 'item', '_ansible_item_label': {'name': 'OVF_STORE', 'image_id': '06bb5f34-112d-4214-91d2-53d0bdb84321', 'id': 'e48a66dd-74c9-43eb-890e-778e9c4ee8db'}} [ ERROR ] {'msg': 'non-zero return code', 'cmd': "vdsm-client Image prepare storagepoolID=06c58622-f99b-11ea-9122-00163e1bbc93 storagedomainID=2a4a3cce-f2f6-4ddd-b337-df5ef562f520 imageID=750428bd-1273-467f-9b27-7f6fe58a446c volumeID=1c89c678-f883-4e61-945c-5f7321add343 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 6023764f-5547-4b23-92ca-422eafdf3f87.ovf", 'stdout': '', 'stderr': "vdsm-client: Command Image.prepare with args {'storagepoolID': '06c58622-f99b-11ea-9122-00163e1bbc93', 'storagedomainID': '2a4a3cce-f2f6-4ddd-b337-df5ef562f520', 'imageID': '750428bd-1273-467f-9b27-7f6fe58a446c', 'volumeID': '1c89c678-f883-4e61-945c-5f7321add343'} failed:\n(code=309, message=Unknown pool id, pool not connected: ('06c58622-f99b-11ea-9122-00163e1bbc93',))\ntar: This does not look like a tar archive\ntar: 6023764f-5547-4b23-92ca-422eafdf3f87.ovf: Not found in archive\ntar: Exiting with failure status due to previous errors", 'rc': 2, 'start': '2020-09-21 17:16:26.030343', 'end': '2020-09-21 17:16:26.381862', 'delta': '0:00:00.351519', 'changed': True, 'failed': True, 'invocation': {'module_args': {'warn': False, '_raw_params': "vdsm-client Image prepare storagepoolID=06c58622-f99b-11ea-9122-00163e1bbc93 storagedomainID=2a4a3cce-f2f6-4ddd-b337-df5ef562f520 imageID=750428bd-1273-467f-9b27-7f6fe58a446c volumeID=1c89c678-f883-4e61-945c-5f7321add343 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 6023764f-5547-4b23-92ca-422eafdf3f87.ovf", '_uses_shell': True, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable ': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ["vdsm-client: Command Image.prepare with args {'storagepoolID': '06c58622-f99b-11ea-9122-00163e1bbc93', 'storagedomainID': '2a4a3cce-f2f6-4ddd-b337-df5ef562f520', 'imageID': '750428bd-1273-467f-9b27-7f6fe58a446c', 'volumeID': '1c89c678-f883-4e61-945c-5f7321add343'} failed:", "(code=309, message=Unknown pool id, pool not connected: ('06c58622-f99b-11ea-9122-00163e1bbc93',))", 'tar: This does not look like a tar archive', 'tar: 6023764f-5547-4b23-92ca-422eafdf3f87.ovf: Not found in archive', 'tar: Exiting with failure status due to previous errors'], '_ansible_no_log': False, 'attempts': 12, 'item': {'name': 'OVF_STORE', 'image_id': '1c89c678-f883-4e61-945c-5f7321add343', 'id': '750428bd-1273-467f-9b27-7f6fe58a446c'}, 'ansible_loop_var': 'item', '_ansible_item_label': {'name': 'OVF_STORE', 'image_id': '1c89c678-f883-4e61-945c-5f7321add343', 'id': '750428bd-1273-467f-9b27-7f6fe58a446c'}} For the "domain data" steps, I created the same folder "/data" on the node2 server that should be used as NFS domain data (and, the playbook added correctly the storage): Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: Please specify the nfs version you would like to use (auto, v3, v4, v4_0, v4_1, v4_2)[auto]: Please specify the full shared storage connection path to use (example: host:/path): node2-server.tld:/data If needed, specify additional mount options for the connection to the hosted-engine storagedomain (example: rsize=32768,wsize=32768) []: [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Wait for the storage interface to be up] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add iSCSI storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add Fibre Channel storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Get storage domain details] [ INFO ] ok: [localhost]

2 1

How to discover why a VM is getting suspended without recovery possibility?
by Vinícius Ferrão 22 Sep '20

22 Sep '20

Hello, I’m an Exchange Server VM that’s going down to suspend without possibility of recovery. I need to click on shutdown and them power on. I can’t find anything useful on the logs, except on “dmesg” of the host: [47807.747606] *** Guest State *** [47807.747633] CR0: actual=0x0000000000050032, shadow=0x0000000000050032, gh_mask=fffffffffffffff7 [47807.747671] CR4: actual=0x0000000000002050, shadow=0x0000000000000000, gh_mask=fffffffffffff871 [47807.747721] CR3 = 0x00000000001ad002 [47807.747739] RSP = 0xffffc20904fa3770 RIP = 0x0000000000008000 [47807.747766] RFLAGS=0x00000002 DR7 = 0x0000000000000400 [47807.747792] Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000 [47807.747821] CS: sel=0x9100, attr=0x08093, limit=0xffffffff, base=0x000000007ff91000 [47807.747855] DS: sel=0x0000, attr=0x08093, limit=0xffffffff, base=0x0000000000000000 [47807.747889] SS: sel=0x0000, attr=0x08093, limit=0xffffffff, base=0x0000000000000000 [47807.747923] ES: sel=0x0000, attr=0x08093, limit=0xffffffff, base=0x0000000000000000 [47807.747957] FS: sel=0x0000, attr=0x08093, limit=0xffffffff, base=0x0000000000000000 [47807.747991] GS: sel=0x0000, attr=0x08093, limit=0xffffffff, base=0x0000000000000000 [47807.748025] GDTR: limit=0x00000057, base=0xffff80817e7d5fb0 [47807.748059] LDTR: sel=0x0000, attr=0x10000, limit=0x000fffff, base=0x0000000000000000 [47807.748093] IDTR: limit=0x00000000, base=0x0000000000000000 [47807.748128] TR: sel=0x0040, attr=0x0008b, limit=0x00000067, base=0xffff80817e7d4000 [47807.748162] EFER = 0x0000000000000000 PAT = 0x0007010600070106 [47807.748189] DebugCtl = 0x0000000000000000 DebugExceptions = 0x0000000000000000 [47807.748221] Interruptibility = 00000009 ActivityState = 00000000 [47807.748248] *** Host State *** [47807.748263] RIP = 0xffffffffc0c65024 RSP = 0xffff9252bda5fc90 [47807.748290] CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040 [47807.748318] FSBase=00007f46d462a700 GSBase=ffff9252ffac0000 TRBase=ffff9252ffac4000 [47807.748351] GDTBase=ffff9252ffacc000 IDTBase=ffffffffff528000 [47807.748377] CR0=0000000080050033 CR3=000000105ac8c000 CR4=00000000001627e0 [47807.748407] Sysenter RSP=0000000000000000 CS:RIP=0010:ffffffff8f196cc0 [47807.748435] EFER = 0x0000000000000d01 PAT = 0x0007050600070106 [47807.748461] *** Control State *** [47807.748478] PinBased=0000003f CPUBased=b6a1edfa SecondaryExec=00000ceb [47807.748507] EntryControls=0000d1ff ExitControls=002fefff [47807.748531] ExceptionBitmap=00060042 PFECmask=00000000 PFECmatch=00000000 [47807.748561] VMEntry: intr_info=00000000 errcode=00000006 ilen=00000000 [47807.748589] VMExit: intr_info=00000000 errcode=00000000 ilen=00000001 [47807.748618] reason=80000021 qualification=0000000000000000 [47807.748645] IDTVectoring: info=00000000 errcode=00000000 [47807.748669] TSC Offset = 0xfffff9b8c8d943b6 [47807.748699] TPR Threshold = 0x00 [47807.748715] EPT pointer = 0x000000105cd5601e [47807.748735] PLE Gap=00000080 Window=00001000 [47807.748755] Virtual processor ID = 0x0003 So something really went crazy. The VM is going down at least two times a day for the last 5 days. At first I thought it would be an hardware issue, so I restarted the VM on other host, and the same thing happened. About the VM it’s configured with 10 CPUs, 48GB of RAM running oVirt 4.3.10 with iSCSI storage to a FreeNAS box, where the VM disks are running; there are a 300GB disc for C:\ and 2TB disk for D:\. Any ideia on how to start troubleshooting it? Thanks,

3 11

hosted engine migration
by 董青龙 22 Sep '20

22 Sep '20

Hi all, I have an ovirt4.3.10.4 environment of 2 hosts. Normal vms in this environment could be migrated, but the hosted engine vm could not be migrated. Anyone can help? Thanks a lot! hosts status: normal vm migration: hosted engine vm migration:

4 27

in ovirt-engine all host show the status at "non-responsive"
by momokch＠yahoo.com.hk 22 Sep '20

22 Sep '20

hello everyone, I apologize for asking what is probably a very basic question. i have 4 hosts running on the ovirt-engine, but on the last week the alert show all the hosts status has gone to non responsive like the following statement Host 1 became non responsive. It has no power management configured. Please check the host status, manually reboot it, and click "Confirm Host Has Been Rebooted" all the storage, vm, cannot detect on the ovirt-engine, does anyone face this before? and also the alert also show ""Engine's certification has expired at 2020-08-18. Please renew the engine's certification"" is it related to the hosts become non-responsive??? i have already regenerate the ovirt-engine cert from the previous post: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/ZI5WNU6OB6FZMQ… Yours Sincerely, school it

2 5

Upgrading self-Hosted engine from 4.3 to oVirt 4.4
by Adam Xu 22 Sep '20

22 Sep '20

Hi ovirt I just try to upgrade a self-Hosted engine from 4.3.10 to 4.4.1.4. I followed the step in the document: https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3 the old 4.3 env has a FC storage as engine storage domain and I have created a new FC storage vv for the new storage domain to be used in the next steps. I backup the old 4.3 env and prepare a total new host to restore the env. in charter 4.4 step 8, it said: "During the deployment you need to provide a new storage domain. The deployment script renames the 4.3 storage domain and retains its data." it does rename the old storage domain. but it didn't let me choose a new storage domain during the deployment. So the new enigne just deployed in the new host's local storage and can not move to the FC storage domain. Can anyone tell me what the problem is? Thanks -- Adam Xu

2 13

AAA Extension mapping could not be found
by dominique.deschenes＠gcgenicom.com 21 Sep '20

21 Sep '20

I tried to use AAA mapping. but I have this message Sep 21, 2020 2:12:05 PM org.ovirt.engine.exttool.aaa.AAAServiceImpl run INFO: Iteration: 0 Sep 21, 2020 2:12:05 PM org.ovirt.engine.exttool.core.ExtensionsToolExecutor main SEVERE: Extension mapping could not be found Sep 21, 2020 2:12:05 PM org.ovirt.engine.exttool.core.ExtensionsToolExecutor main FINE: Exception: org.ovirt.engine.core.extensions.mgr.ConfigurationException: Extension mapping could not be found at org.ovirt.engine.core.extensions-manager//org.ovirt.engine.core.extensions.mgr.ExtensionsManager.getExtensionByName(ExtensionsManager.java:286) at org.ovirt.engine.core.extensions-tool//org.ovirt.engine.exttool.aaa.AAAServiceImpl$AAAProfile.<init>(AAAServiceImpl.java:846) at org.ovirt.engine.core.extensions-tool//org.ovirt.engine.exttool.aaa.AAAServiceImpl$Action.lambda$static$3(AAAServiceImpl.java:154) at org.ovirt.engine.core.extensions-tool//org.ovirt.engine.exttool.aaa.AAAServiceImpl$Action.execute(AAAServiceImpl.java:417) at org.ovirt.engine.core.extensions-tool//org.ovirt.engine.exttool.aaa.AAAServiceImpl.run(AAAServiceImpl.java:686) at org.ovirt.engine.core.extensions-tool//org.ovirt.engine.exttool.core.ExtensionsToolExecutor.main(ExtensionsToolExecutor.java:121) at org.jboss.modules.Module.run(Module.java:352) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:593) it's like it can't find for my mapping.properties file I followed the Howto on this page. https://www.ovirt.org/develop/release-management/features/infra/aaa_faq.html Here my config : tail /etc/ovirt-engine/extensions.d/local.lan-authn.properties ovirt.engine.aaa.authn.authz.plugin ovirt.engine.extension.name = local.lan-authn ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine.extension.aaa.ldap ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engine.extension.aaa.ldap.AuthnExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authn ovirt.engine.aaa.authn.profile.name = local.lan ovirt.engine.aaa.authn.authz.plugin = local.lan ovirt.engine.aaa.authn.mapping.plugin = mapping config.profile.file.1 = ../aaa/local.lan.properties tail /etc/ovirt-engine/extensions.d/mapping.properties ovirt.engine.extension.name = mapping ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.misc ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.misc.mapping.MappingExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Mapping config.mapUser.type = regex config.mapUser.regex.pattern = ^(?<user>[^@]*)$ config.mapUser.regex.replacement = ${user}(a)domain.com config.mapUser.regex.mustMatch = false

2 1

New install
by info＠worldhostess.com 21 Sep '20

21 Sep '20

I have an issue with new installation. The server name is changing all the time and it keep disconnecting me. Plus it is impossible to log in as admin. The install went through without any issues, but it seems something is wrong. Server: engine01.xxxx.com Log in with your server user account. Server: node01.xxxx.com Log in with your server user account.

1 0

i cannot access to ovirt-engine with this error"sun.security.validator.validatorexception: pkix path validation failed: java.security.cert.certpathvalidatorexception: timestamp check failed
by momokch＠yahoo.com.hk 20 Sep '20

20 Sep '20

hello everyone, I apologize for asking what is probably a very basic question. when i login to my ovirt-engine webpage, the page show "sun.security.validator.validatorexception: pkix path validation failed: java.security.cert.certpathvalidatorexception: timestamp check failed" does anyone face it before and how to solve it the site is normal before which error message is just show near a month Yours Sincerely, school it

3 3

routing policy problem in ovirt 4.4
by g.vasilopoulos＠uoc.gr 19 Sep '20

19 Sep '20

Hello I created a cluster of ovirt 4.4 with 5 servers, I have a diferent gateway, ovirtmgmt and display network. In 4.4 routing is managed from network manager. Network manager seems to "forget" and recreate the route each time. So I cannot connect to the virtual machines console unless I run a ping for about a minute on the display network ip of the hypervisor, so network manager "wakes up" and "recreates" the route. I use this work around but it is not something that a user can do. What is the proper way to do this ? Thank you

3 3

OVirt HCI Setup Wizard - Drive specification Ignored
by Jeremey Wise 19 Sep '20

19 Sep '20

Greetings: 3 x servers each server has 1 x 512GB ssd 2 x 1TB SSD JBOD Goal: use HCI disk setup wizard to deploy initial structure Each server has disk scanning in as different /dev/sd# and so trying to use more clear /dev/mapper/<disk ID> As such I set this per table below: # Select each server and set each drive <<<<<<<<<<Double Check drive device ID as they do NOT match up per host # I transitioned to /dev/mapper object to avoid unclearness of /dev/sd# thor /dev/sdc /dev/mapper/Samsung_SSD_850_PRO_512GB_S250NXAGA15787L odin /dev/sdb /dev/mapper/Micron_1100_MTFDDAV512TBN_17401F699137 medusa /dev/sdb /dev/mapper/SAMSUNG_SSD_PM851_mSATA_512GB_S1EWNYAF609306 # Note that drives need to be completely clear of any partition or file system [root@thor /]# gdisk /dev/sdc GPT fdisk (gdisk) version 1.0.3 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): x Expert command (? for help): z About to wipe out GPT on /dev/sdc. Proceed? (Y/N): y GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Blank out MBR? (Y/N): y [image: image.png] [image: image.png] But deployment fails with Error: <snip> TASK [gluster.infra/roles/backend_setup : Filter none-existing devices] ******** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/get_vg_groupings.yml:38 ok: [thorst.penguinpages.local] => {"ansible_facts": {"gluster_volumes_by_groupname": {}}, "changed": false} ok: [odinst.penguinpages.local] => {"ansible_facts": {"gluster_volumes_by_groupname": {}}, "changed": false} ok: [medusast.penguinpages.local] => {"ansible_facts": {"gluster_volumes_by_groupname": {}}, "changed": false} TASK [gluster.infra/roles/backend_setup : Make sure thick pvs exists in volume group] *** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thick_lv_create.yml:37 TASK [gluster.infra/roles/backend_setup : update LVM fact's] ******************* task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thick_lv_create.yml:83 skipping: [thorst.penguinpages.local] => {"changed": false, "skip_reason": "Conditional result was False"} skipping: [odinst.penguinpages.local] => {"changed": false, "skip_reason": "Conditional result was False"} skipping: [medusast.penguinpages.local] => {"changed": false, "skip_reason": "Conditional result was False"} TASK [gluster.infra/roles/backend_setup : Create thick logical volume] ********* task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thick_lv_create.yml:90 failed: [medusast.penguinpages.local] (item={'vgname': ' gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'lvname': 'gluster_lv_engine', 'size': '1000G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L\" not found.\n Cannot process volume group gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "1000G", "vgname": "gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L"}, "msg": "Volume group gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L does not exist.", "rc": 5} changed: [thorst.penguinpages.local] => (item={'vgname': ' gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'lvname': 'gluster_lv_engine', 'size': '1000G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": true, "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "1000G", "vgname": "gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L"}, "msg": ""} failed: [odinst.penguinpages.local] (item={'vgname': 'gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L', 'lvname': 'gluster_lv_engine', 'size': '1000G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L\" not found.\n Cannot process volume group gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "1000G", "vgname": "gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L"}, "msg": "Volume group gluster_vg_Samsung_SSD_850_PRO_512GB_S250NXAGA15787L does not exist.", "rc": 5} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* medusast.penguinpages.local : ok=23 changed=5 unreachable=0 failed=1 skipped=34 rescued=0 ignored=0 odinst.penguinpages.local : ok=23 changed=5 unreachable=0 failed=1 skipped=34 rescued=0 ignored=0 thorst.penguinpages.local : ok=30 changed=9 unreachable=0 failed=0 skipped=29 rescued=0 ignored=0 Please check /var/log/cockpit/ovirt-dashboard/gluster-deployment.log for more informations. ############ Why is oVirt ignoring when I set (and double check explicite device call for deployment? Attached is the ansible file it creates and then one I had to edit to correct what wizard should have built it as. -- p <jeremey.wise(a)gmail.com>enguinpages

3 5

New oVirt Install - Host Engine Deployment Fails
by mblanton＠vnet.net 18 Sep '20

18 Sep '20

I am attempting a new oVirt install. I have two nodes installed (with oVirt Node 4.4). I have NFS shared storage for the hosted engine. Both nodes are Dell quad core Xeon CPUs with 32GB of RAM. Both have been hypervisors before, XCP-NG and Proxmox. However I'm very interested to learn oVirt now. The hosted engine deployment (through cockpit) fails during the "Finish" stage. I do see the initial files created on the NFS storage. [ INFO ] TASK [ovirt.hosted_engine_setup : Convert CPU model name] [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 16, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n# - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n"} 2020-09-13 17:39:56,507+0000 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute '' \n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_targ et_hosted_engine_vm.yml': line 105, column 16, but may\nbe elsewhere in the file depending on the exact syntax problem.\ n\nThe offending line appears to be:\n\n# - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be bo th 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n" }, "ansible_task": "Convert CPU model name", "ansible_type": "task", "status": "FAILED", "task_duration": 1 } I can see the host engine is created and running locally on the node. I can event SSH into the HostedEngineLocal instance. [root@ovirt-node01]# virsh --readonly list Id Name State ----------------------------------- 1 HostedEngineLocal running Looking at the "Convert CPU model name" task: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/task… set_fact: cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}" server_cpu_dict is good, I can find that in the logs, cluster_cpu is undefined. But this is normal correct? The Cluster CPU type is "undefined" until the first host is added to the cluster. The error makes it seems that server_cpu_dict and not cluster_cpu.type is the problem. I'm not sure this is really the problem, but that is the only undefined variable I can find. Any advice or recommendation is appreciated -Thanks in advance

5 8

Re: Random hosts disconnects
by Artur Socha 18 Sep '20

18 Sep '20

Hi Anton, I am not sure if changing this value would fix the issue. Defaults are pretty high. For example vdsHeartbeatInSeconds=30seconds, vdsTimeout=180seconds, vdsConnectionTimeout=20seconds. Do you still have relevant logs from the affected hosts: * /var/logs/vdsm/vdsm.log* * /var/logs/vdsm/supervdsm.log* Please look for any jsonrpc errors ie. write/read errors or (connection) timeouts. Storage related warnings/errors might also be relevant. Plus system logs if possible: *journalctl -f /usr/share/vdsm/vdsmd* *journalctl -f /usr/sbin/libvirtd* In order to get system logs from particular time period please combine it with the following example using -S -U options: *journalctl -S "2020-01-12 07:00:00" -U "2020-01-12 07:15:00" * I haven't a clue what to look there for besides any warnings/errors or anything else that seems .... unusual. Artur On Thu, Sep 17, 2020 at 8:09 AM Anton Louw via Users <users(a)ovirt.org> wrote: > > > Hi Everybody, > > > > Did some digging around, and saw a few things regarding “vdsHeartbeatInSeconds” > > I had a look at the properties file located at /etc/ovirt-engine/engine-config/engine-config.properties, and do not see an entry for “vdsHeartbeatInSeconds.type=Integer”. > > Seeing as these data centers are geographically split, could the “vdsHeartbeatInSeconds” potentially be the issue? Is it safe to increase this value after I add “vdsHeartbeatInSeconds.type=Integer” into my engine-config.properties file? > > > > Thanks > > > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > *From:* Anton Louw via Users <users(a)ovirt.org> > *Sent:* 16 September 2020 09:01 > *To:* users(a)ovirt.org > *Subject:* [ovirt-users] Random hosts disconnects > > > > > > Hi All, > > > > I have a strange issue in my oVirt environment. I currently have a > standalone manager which is running in VMware. In my oVirt environment, I > have two Data Centers. The manager is currently sitting on the same subnet > as DC1. Randomly, hosts in DC2 will say “Not Responding” and then 2 seconds > later, the hosts will activate again. > > > > The strange thing is, when the manager was sitting on the same subnet as > DC2, hosts in DC1 will randomly say “Not Responding” > > > > I have tried going through the logs, but I cannot see anything out of the > ordinary regarding why the hosts would drop connection. I have attached the > engine.log for anybody that would like to do a spot check. > > > > Thanks > > > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > [image: F] <https://www.facebook.com/voxtelecomZA> > > > > [image: T] <https://www.twitter.com/voxtelecom> > > > > [image: I] <https://www.instagram.com/voxtelecomza> > > > > [image: L] <https://www.linkedin.com/company/voxtelecom> > > > > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > > > > > [image: #VoxBrand] > <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > > > *Disclaimer* > > The contents of this email are confidential to the sender and the intended > recipient. Unless the contents are clearly and entirely of a personal > nature, they are subject to copyright in favour of the holding company of > the Vox group of companies. Any recipient who receives this email in error > should immediately report the error to the sender and permanently delete > this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > > > _______________________________________________ > 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/EJL246IPBGEHI… > -- Artur Socha Senior Software Engineer, RHV Red Hat

2 1