- Users - oVirt List Archives

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

23 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 23 Sep '20

23 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 23 Sep '20

23 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 22 Sep '20

22 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