October 2021 - Users - oVirt List Archives

Host is not added in known_hosts
by admin＠foundryserver.com 20 Oct '21

20 Oct '21

ok I am setting up the gluster file system. I have the following completed - able to ssh into all three hosts from host1 without password prompting. - on each host I have host file entries for host{x}.private.net - on public dns, I have host{x}1.fg.net - each host has a public nic and private nic. - I have all three hosts added in the dashboard - I am able to ping all three on private and public nic from host1 When I go to add the hosts in the setup, it looks like 2 and 3 are fine with no errors, but host1 entry gives me "Host is not added in known_hosts" error. I am doing this setup from host1. It feels like there is a link to being on host1 and host1 having the error. I am still google fooing as we speak to try and find an error. The only thing I have not done, is setup host 2 and 3 to be able to ssh into all the other boxes. Any thoughts would be greatly appreciated. Happy to share screen shots if it would help. Brad

3 4

fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by dhanaraj.ramesh＠yahoo.com 20 Oct '21

20 Oct '21

Hi Team I'm trying to setup 3 node Gluster + ovirt setup with latest stable 4.4.8 version but while deploying the gluster from cokpit getting below error what could be the reason TASK [gluster.infra/roles/backend_setup : Set Gluster specific SeLinux context on the bricks] *** failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* beclovkvma01.bec. lab : ok=53 changed=14 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1 beclovkvma02.bec. lab : ok=52 changed=13 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1 beclovkvma03.bec. lab : ok=52 changed=13 unreachable=0 failed=1 skipped=116 rescued=0 ignored=1

6 11

Engine backup / restore
by duparchy＠esrf.fr 20 Oct '21

20 Oct '21

Hi, I'm testing Backup / Restore of the engine. Once the engine is restored ; how to resync the engine database with the "reality" of the Storage Domains ? (I'm talking about anything that could have been done after the engine backup : Deleted / Created VMs ; Snapshots taken since the backup, etc.. I'm on 4.3, Oracle LVM context. My Tests : - Create a snapshot of some random VM. Say VM-1 - Enable that VM preview and start it on a host. - Stop OLVM engine server. - Start a full backup copy of that OLVM engine (That backup being a snapshot taken, say, yesterday. Our test OLVM engine being a VM running in another separate virltualization infrastucture.) The restored OLVM does not show the existence of the VM-1 snapshot. It only shows the VM running on the active instance. No snapshot. I tried Storage Domain / Scan disks. No refresh to be seen.

3 3

Re: Ceph integration
by Sandro Bonazzola 20 Oct '21

20 Oct '21

Il giorno mer 20 ott 2021 alle ore 10:09 samuel.xhu(a)horebdata.cn < samuel.xhu(a)horebdata.cn> ha scritto: > Great, sounds very interesting. I will give a try. > > How about the stability of this approach to use Ceph RBD? Can we call it > prodouction-ready or just experimental? > I'll let the storage team to reply to this, but it seems stable enough for production to me. +Eyal Shenitzky <eshenitz(a)redhat.com> ? > > ------------------------------ > Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed > (成就他人) > > > *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> > *Date:* 2021-10-20 10:04 > *To:* samuel.xhu(a)horebdata.cn > *CC:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Re: Ovirt VM started with the most recent > snapshot with the current disk missing > > > Il giorno mer 20 ott 2021 alle ore 09:59 samuel.xhu(a)horebdata.cn < > samuel.xhu(a)horebdata.cn> ha scritto: > >> Thanks for the tip. I will then upgrade to 4.4. >> >> By the way, how about the progress of the support of Ceph storage for >> Ovirt? Proxmox has a very good successful story of integrating Ceph, and we >> hope Ovirt would soon catch up. >> > > I wrote a blog about it here: > https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente… > > > > >> >> best regards, >> >> samuel >> >> ------------------------------ >> Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed >> (成就他人) >> >> >> *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> >> *Date:* 2021-10-20 09:16 >> *To:* Xiaoyu Hu <samuel.xhu(a)gmail.com> >> *CC:* oVirt Users <users(a)ovirt.org> >> *Subject:* [ovirt-users] Re: Ovirt VM started with the most recent >> snapshot with the current disk missing >> >> >> Il giorno dom 17 ott 2021 alle ore 13:57 Xiaoyu Hu <samuel.xhu(a)gmail.com> >> ha scritto: >> >>> Dear Ovirt folks, >>> >>> I am faced with a very strange situation with Ovirt 4.3. A virtual >>> machine has two snapshots and a working disk, with the former two snapshots >>> being read only and the working one read-write. After an unplanned power >>> outage, a virtual machine can only be started with the recent snapshot, and >>> the actual working disk is missing in the Ovirt UI. I can see the disk >>> still exists in the backend storage, but it seems not Ovirt does not know >>> it. Thus the VM lose the recent data on the missing disk. >>> >>> Does any one know whether this is a known bug in Ovirt 4.3, or is there >>> a method to resotre the missing working disk back to the virtuanl machine? >>> Otherwise i am faced with a terrible data loss issue on Ovirt >>> >> Hi, oVirt 4.3 reached the end of life a long time ago. I would recommend >> upgrading to oVirt 4.4 as soon as practical. >> >> >> >>> best regards, >>> >>> Samuel >>> _______________________________________________ >>> 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/N7JVXAU5MLAG5… >>> >> >> >> -- >> >> 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.* >> >> >> > > -- > > 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.* > > > -- 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.*

2 1

Re: Ovirt VM started with the most recent snapshot with the current disk missing
by Sandro Bonazzola 20 Oct '21

20 Oct '21

Il giorno mer 20 ott 2021 alle ore 09:59 samuel.xhu(a)horebdata.cn < samuel.xhu(a)horebdata.cn> ha scritto: > Thanks for the tip. I will then upgrade to 4.4. > > By the way, how about the progress of the support of Ceph storage for > Ovirt? Proxmox has a very good successful story of integrating Ceph, and we > hope Ovirt would soon catch up. > I wrote a blog about it here: https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente… > > best regards, > > samuel > > ------------------------------ > Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed > (成就他人) > > > *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> > *Date:* 2021-10-20 09:16 > *To:* Xiaoyu Hu <samuel.xhu(a)gmail.com> > *CC:* oVirt Users <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: Ovirt VM started with the most recent > snapshot with the current disk missing > > > Il giorno dom 17 ott 2021 alle ore 13:57 Xiaoyu Hu <samuel.xhu(a)gmail.com> > ha scritto: > >> Dear Ovirt folks, >> >> I am faced with a very strange situation with Ovirt 4.3. A virtual >> machine has two snapshots and a working disk, with the former two snapshots >> being read only and the working one read-write. After an unplanned power >> outage, a virtual machine can only be started with the recent snapshot, and >> the actual working disk is missing in the Ovirt UI. I can see the disk >> still exists in the backend storage, but it seems not Ovirt does not know >> it. Thus the VM lose the recent data on the missing disk. >> >> Does any one know whether this is a known bug in Ovirt 4.3, or is there a >> method to resotre the missing working disk back to the virtuanl machine? >> Otherwise i am faced with a terrible data loss issue on Ovirt >> > Hi, oVirt 4.3 reached the end of life a long time ago. I would recommend > upgrading to oVirt 4.4 as soon as practical. > > > >> best regards, >> >> Samuel >> _______________________________________________ >> 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/N7JVXAU5MLAG5… >> > > > -- > > 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.* > > > -- 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.*

2 1

prod network glitch after reboot lab server
by Dominique D 20 Oct '21

20 Oct '21

Hi, I have two ovirt environments on the same network. 2 switches (10G switch for storage and 1G switch for data / management) 1) Prod environment: 3 oVirt 4.4.6 nodes (1 port 10G per node for storage gluster and 1 port 1G for data / management) 2) Lab environment 2 oVirt nodes 4.4.6 (1 Port 10G per node for storage gluster and 1 port 1G for data / management) The storage is on the same vlan and subnet for both environments. When I restart one of my lab servers, I have communication cuts/glitch on my production ovirt clusters. I even had server reboots. Do you know why ? Here somes log : VDSM ovnode1.telecom.lan command SpmStatusVDS failed: Connection timeout for host 'ovnode1.telecom.lan', last response arrived 42479 ms ago. Host ovnode1.telecom.lan is not responding. It will stay in Connecting state for a grace period of 88 seconds and after that an attempt to fence the host will be issued. Invalid status on Data Center Default. Setting Data Center status to Non Responsive (On host ovnode1.telecom.lan, Error: Network error during communication with the Host.). Host ovnode1.telecom.lan cannot access the Storage Domain(s) datassd attached to the Data Center Default. Setting Host state to Non-Operational.

2 1

Ovirt VM started with the most recent snapshot with the current disk missing
by Xiaoyu Hu 20 Oct '21

20 Oct '21

Dear Ovirt folks, I am faced with a very strange situation with Ovirt 4.3. A virtual machine has two snapshots and a working disk, with the former two snapshots being read only and the working one read-write. After an unplanned power outage, a virtual machine can only be started with the recent snapshot, and the actual working disk is missing in the Ovirt UI. I can see the disk still exists in the backend storage, but it seems not Ovirt does not know it. Thus the VM lose the recent data on the missing disk. Does any one know whether this is a known bug in Ovirt 4.3, or is there a method to resotre the missing working disk back to the virtuanl machine? Otherwise i am faced with a terrible data loss issue on Ovirt best regards, Samuel

3 2

Can't access ovirtengine
by mohammed.abuhajar＠edugrade.se 20 Oct '21

20 Oct '21

Hi I have installed oVirt 4.4.8 och hosted-engine. The installation har done without error, but I am not able to access ovirtengine. When I check the status of engine it seems everything is ok and up. Any idea? //Mohammed

2 1

Q: oVirt guest agent + spice-vdagent on Debian 11 Bullseye
by Andrei Verovski 20 Oct '21

20 Oct '21

Hi, Anyone have compiled these deb packages for Debian 11 Bullseye? oVirt guest agent + spice-vdagent Packages from Buster can’t be installed on Bullseye because of broken libnl dependencies. Thanks in advance. Andrei

2 1

GPG key <infra@ovirt.org> expired since April ?
by Fredrik Arneving 20 Oct '21

20 Oct '21

Hi, According to output pasted below it seems that the GPG key used to sign installation media has expired 2021-04-03. Why is new installation ISO signed 7 days ago with a key that has been expired for almost 6 months? Is this correct? My main question though is if this iso is authentic? $ ll -h ovirt-node-ng-installer-4.4.8-2021090310.el8.iso* -rw-r--r--. 1 fredde fredde 1.9G Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso -rw-r--r--. 1 fredde fredde 32 Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum -rw-r--r--. 1 fredde fredde 490 Oct 1 14:48 ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum.sig $ gpg --list-keys oVirt pub rsa2048 2014-03-30 [SC] [expired: 2021-04-03] 31A5D7837FAD7CB286CD3469AB8C4F9DFE590CB7 uid [ expired] oVirt <infra(a)ovirt.org> $ gpg --verify-files *.sig gpg: assuming signed data in 'ovirt-node-ng-installer-4.4.8-2021090310.el8.iso.md5sum' gpg: Signature made Thu 23 Sep 2021 02:41:24 PM CEST gpg: using RSA key AB8C4F9DFE590CB7 gpg: Good signature from "oVirt <infra(a)ovirt.org>" [expired] gpg: Note: This key has expired! Primary key fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 $ cat *.md5sum e75ac6f671c666140a205e6eab3d0c4a $ md5sum ovirt-node-ng-installer-4.4.8-2021090310.el8.iso e75ac6f671c666140a205e6eab3d0c4a ovirt-node-ng-installer-4.4.8-2021090310.el8.iso BR /F

2 2