- Users - oVirt List Archives

install python package ovirt_imageio for Ovirt 4.3
by Grace Chen 21 Oct '21

21 Oct '21

I want to use python script running from a host to automate the remote kvm manager's vm backup. Our ovirt version is 4.3. I have installed ovirt-imageio-daemon on the host I tried to yum install ovirt-imageio-client (we use yum), it couldn't find the package. error message: Loaded plugins: ulninfo, vdsmupgrade, versionlock ovirt-4.3 | 3.0 kB 00:00:00 ovirt-4.3-extra | 3.0 kB 00:00:00 ovirt-master-snapshot | 3.0 kB 00:00:00 ovirt-master-snapshot-static | 3.0 kB 00:00:00 No package ovirt-imageio-client available. I tried to copy folder ovirt_imageio from ovirt-imageio to my python library directory, it could not compile the c file "ioutil.c" Can anybody help me install the python package? Am I installing on the correct place, do I need to use the python script only on the host that installed the kvm manager?

3 6

oVirt 4.4.8 Hyperconverged deploy failed
by dvx.mellin＠gmail.com 21 Oct '21

21 Oct '21

Hi everyone, I'm trying to deploy a hyperconverged ovirt cluster, but the the wizard in cockpit failed at the first step with the error "FQDN is not reachable". The goal is to have 3 nodes, with hosted engine on gluster FS. Here is the relevant information : - CentOS 8.4 - ovirt 4.4.8 - 2 network interfaces (1 for storage, 1 for production) The packages installed : cockpit-ovirt-dashboard, vdsm-gluster, ovirt-host, ovirt-engine-appliance, gluster-ansible-roles # rpm -qa | grep ovirt ovirt-imageio-client-2.2.0-1.el8.x86_64 ovirt-host-dependencies-4.4.8-1.el8.x86_64 ovirt-vmconsole-1.0.9-1.el8.noarch python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-provider-ovn-driver-1.2.34-1.el8.noarch ovirt-host-4.4.8-1.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-imageio-daemon-2.2.0-1.el8.x86_64 ovirt-hosted-engine-ha-2.4.8-1.el8.noarch ovirt-hosted-engine-setup-2.5.3-1.el8.noarch ovirt-engine-appliance-4.4-20210826223909.1.el8.x86_64 cockpit-ovirt-dashboard-0.15.1-1.el8.noarch python3-ovirt-engine-sdk4-4.4.15-1.el8.x86_64 ovirt-ansible-collection-1.6.2-1.el8.noarch ovirt-imageio-common-2.2.0-1.el8.x86_64 I didn't use the ovirt44-release package because we have to use our local repo. So we have cloned all necessary repo. Every package installation was passed without any issues. The /etc/hosts contains every FQDN/IP for the storage network (which is not exposed to the public), and the DNS server is reachable to respond to public FQDN. Passwordless connection is installed and works perfectly with sotrage and production FQDN. If you need more information, please tell me. Thanks in advance for your help. Regards

1 1

Hosted Engine Deployment failure
by Raj P 21 Oct '21

21 Oct '21

Hi, I ma tryinf to deploy hosted engine and keeps on failing with following errors. Am new to oVirt and unabe to figure out what the issues is? any help would be very much appreciated. [ INFO ] TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> 192.168.222.214]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': repomd.xml parser error: Parse error at line: 68 (xmlParseStartTag: invalid element name\n)", "rc": 1, "results": []} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.214] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}

4 6

[ANN] oVirt 4.4.9 is now generally available
by Sandro Bonazzola 21 Oct '21

21 Oct '21

oVirt 4.4.9 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.9 , as of October 20th, 2021. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important! Known issues Please note qemu-kvm, shipped outside oVirt, is affected by BZ#1999141 <https://bugzilla.redhat.com/show_bug.cgi?id=1999141> - migration fails with: "qemu-kvm: get_pci_config_device: Bad config data: i=0x9a read: 3 device: 2 cmask: ff wmask: 0 w1cmask:0" It has been detected to wait for a fix before building oVirt Node update as it includes qemu-kvm. If you haven’t updated to qemu-kvm 6 yet please don’t update it. Upgraded systems will NOT be able to migrate VMs anywhere else, not even once the issue is fixed. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.9 Release? This update is the ninth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.4 - CentOS Linux (or similar) 8.4 - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream 8 Some of the RFEs with high user impact are listed below: - Bug 1999563 <https://bugzilla.redhat.com/show_bug.cgi?id=1999563> - [RFE] Add a unique number to each panel in Grafana Some of the Bugs with high user impact are listed below: - Bug 2002178 <https://bugzilla.redhat.com/show_bug.cgi?id=2002178> - Deploying ovirt HCI fail due to glusterfs-selinux package missing - Bug 1928704 <https://bugzilla.redhat.com/show_bug.cgi?id=1928704> - Host deploy events does not have proper correlation-id - Bug 1980315 <https://bugzilla.redhat.com/show_bug.cgi?id=1980315> - Configure Grafana in hosted-engine setup by default - Bug 2001465 <https://bugzilla.redhat.com/show_bug.cgi?id=2001465> - Missing obsoletes for java bindings removal - Bug 2003441 <https://bugzilla.redhat.com/show_bug.cgi?id=2003441> - dnf rollback is broken - Bug 1985973 <https://bugzilla.redhat.com/show_bug.cgi?id=1985973> - Remove the abort snapshot behavior - Bug 2008850 <https://bugzilla.redhat.com/show_bug.cgi?id=2008850> - Repositories: Replace the usage of community modules with command invocation - Bug 1964522 <https://bugzilla.redhat.com/show_bug.cgi?id=1964522> - Allow both automatic detection of IP version available as well as manual configuration - Bug 2010658 <https://bugzilla.redhat.com/show_bug.cgi?id=2010658> - AAA LDAP extension is querying DNS with ANY request - Bug 2015121 <https://bugzilla.redhat.com/show_bug.cgi?id=2015121> - VM with thin disk on block storage pause during backup - Bug 2002284 <https://bugzilla.redhat.com/show_bug.cgi?id=2002284> - Replacing calling of specific gluster module with direct command execution in cluster_upgrade role - Bug 1990268 <https://bugzilla.redhat.com/show_bug.cgi?id=1990268> - No ability to change iso with virtio drivers when installing a virtual machine with windows - Bug 1870563 <https://bugzilla.redhat.com/show_bug.cgi?id=1870563> - Ovirt Node 4.4.1 says kickstart insufficient on disk formatting - Bug 1845271 <https://bugzilla.redhat.com/show_bug.cgi?id=1845271> - Better documentation for host ssh requirements - Bug 1993575 <https://bugzilla.redhat.com/show_bug.cgi?id=1993575> - Missing documentation: HOWTO recover from a corrupted hosted engine meta data file oVirt Appliance has been updated, including: - oVirt 4.4.9: https://www.ovirt.org/release/4.4.9/ - CentOS Stream 8 latest updates See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Stream 8 - oVirt Node NG will be available shortly, as it’s currently waiting for a fix of BZ#1999141 <https://bugzilla.redhat.com/show_bug.cgi?id=1999141> Additional resources: - Read more about the oVirt 4.4.9 release highlights: https://www.ovirt.org/release/4.4.9/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.9/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

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