- Users - oVirt List Archives

Fw: oVirt SImpleBackup Question
by Nazan CENGİZ 16 Feb '20

16 Feb '20

[cid:image98df9c.PNG@b7f9c784.4aa7c98c]<http://www.havelsan.com.tr> [cid:image9667a6.JPG@2f962998.4ca370f9] Nazan CENGİZ AR-GE MÜHENDİSİ Mustafa Kemal Mahallesi 2120 Cad. No:39 06510 Çankaya Ankara TÜRKİYE [cid:image115b95.PNG@c0175d7a.4da54ba7] +90 312 219 57 87 [cid:image74e7f4.PNG@907db726.4b9c82a5] +90 312 219 57 97 [cid:imagec6bcd8.JPG@c1e96d06.4693cef7] YASAL UYARI: Bu elektronik posta işbu linki kullanarak ulaşabileceğiniz Koşul ve Şartlar dokümanına tabidir. <http://havelsan.com.tr/tr/news/e-posta-yasal-uyari> LEGAL NOTICE: This e-mail is subject to the Terms and Conditions document which can be accessed with this link. <http://havelsan.com.tr/tr/news/e-posta-yasal-uyari> [http://www.havelsan.com.tr/Library/images/mail/email.jpg] Lütfen gerekmedikçe bu sayfa ve eklerini yazdırmayınız / Please consider the environment before printing this email Hello all, I am using for Ovirt https://github.com/zipurman/oVIRT_Simple_Backup project. Agent is successfull backup but restored vm has two problems. Backup agent is running on Zip vm.When I started restore self disk detach on Zip vm. [cid:1704d47f2bd6ad7a1e93] Second problem is new vm created but automated not connected restore disks. I shared config and state. Problems; [cid:1704d47f2bd540563fc2] When Zipurman installed get Zip vm UUID; [cid:1704d47f2bd2ed7ff4f1] Windows 10 için Posta<https://go.microsoft.com/fwlink/?LinkId=550986> ile gönderildi

1 0

hosted-engine --deploy fails after "Wait for the host to be up" task
by Fredy Sanchez 16 Feb '20

16 Feb '20

*Hi all,* *[root@bric-ovirt-1 ~]# cat /etc/*release** CentOS Linux release 7.7.1908 (Core) *[root@bric-ovirt-1 ~]# yum info ovirt-engine-appliance* Installed Packages Name : ovirt-engine-appliance Arch : x86_64 Version : 4.3 Release : 20191121.1.el7 Size : 1.0 G Repo : installed From repo : ovirt-4.3 *Same situation as https://bugzilla.redhat.com/show_bug.cgi?id=1787267 <https://bugzilla.redhat.com/show_bug.cgi?id=1787267>. The error message almost everywhere is some red herring message about ansible* [ INFO ] TASK [ovirt.hosted_engine_setup : Wait for the host to be up] [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false, "deprecations": [{"msg": "The 'ovirt_host_facts' module has been renamed to 'ovirt_host_info', and the renamed one no longer returns ansible_facts", "version": "2.13"}]} [ INFO ] TASK [ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "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"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200126170315-req4qb.log *But the "real" problem seems to be SSH related, as you can see below* *[root@bric-ovirt-1 ovirt-engine]# pwd* /var/log/ovirt-hosted-engine-setup/engine-logs-2020-01-26T17:19:28Z/ovirt-engine *[root@bric-ovirt-1 ovirt-engine]# grep -i error engine.log* 2020-01-26 17:26:50,178Z ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-1) [2341fd23-f0c7-4f1c-ad48-88af20c2d04b] Failed to establish session with host 'bric-ovirt-1.corp.modmed.com': SSH session closed during connection ' root(a)bric-ovirt-1.corp.modmed.com' 2020-01-26 17:26:50,205Z ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot add Host. Connecting to host via SSH has failed, verify that the host is reachable (IP address, routable address etc.) You may refer to the engine.log file for further details.] *The funny thing is that the engine can indeed ssh to bric-ovirt-1 (physical host). See below* *[root@bric-ovirt-1 ovirt-hosted-engine-setup]# cat /etc/hosts* 192.168.1.52 bric-ovirt-engine.corp.modmed.com # temporary entry added by hosted-engine-setup for the bootstrap VM 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 #::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.130.0.50 bric-ovirt-engine bric-ovirt-engine.corp.modmed.com 10.130.0.51 bric-ovirt-1 bric-ovirt-1.corp.modmed.com 10.130.0.52 bric-ovirt-2 bric-ovirt-2.corp.modmed.com 10.130.0.53 bric-ovirt-3 bric-ovirt-3.corp.modmed.com 192.168.0.1 bric-ovirt-1gluster bric-ovirt-1gluster.corp.modmed.com 192.168.0.2 bric-ovirt-2gluster bric-ovirt-2gluster.corp.modmed.com 192.168.0.3 bric-ovirt-3gluster bric-ovirt-3gluster.corp.modmed.com [root@bric-ovirt-1 ovirt-hosted-engine-setup]# *[root@bric-ovirt-1 ~]# ssh 192.168.1.52* Last login: Sun Jan 26 17:55:20 2020 from 192.168.1.1 [root@bric-ovirt-engine ~]# [root@bric-ovirt-engine ~]# *[root@bric-ovirt-engine ~]# ssh bric-ovirt-1* Password: Password: Last failed login: Sun Jan 26 18:17:16 UTC 2020 from 192.168.1.52 on ssh:notty There was 1 failed login attempt since the last successful login. Last login: Sun Jan 26 18:16:46 2020 ################################################################### # UNAUTHORIZED ACCESS TO THIS SYSTEM IS PROHIBITED # # # # This system is the property of Modernizing Medicine, Inc. # # It is for authorized Company business purposes only. # # All connections are monitored and recorded. # # Disconnect IMMEDIATELY if you are not an authorized user! # ################################################################### [root@bric-ovirt-1 ~]# [root@bric-ovirt-1 ~]# [root@bric-ovirt-1 ~]# exit logout Connection to bric-ovirt-1 closed. [root@bric-ovirt-engine ~]# [root@bric-ovirt-engine ~]# *[root@bric-ovirt-engine ~]# ssh bric-ovirt-1.corp.modmed.com <http://bric-ovirt-1.corp.modmed.com>* Password: Last login: Sun Jan 26 18:17:22 2020 from 192.168.1.52 ################################################################### # UNAUTHORIZED ACCESS TO THIS SYSTEM IS PROHIBITED # # # # This system is the property of Modernizing Medicine, Inc. # # It is for authorized Company business purposes only. # # All connections are monitored and recorded. # # Disconnect IMMEDIATELY if you are not an authorized user! # ################################################################### [root@bric-ovirt-1 ~]# exit logout Connection to bric-ovirt-1.corp.modmed.com closed. [root@bric-ovirt-engine ~]# [root@bric-ovirt-engine ~]# [root@bric-ovirt-engine ~]# exit logout Connection to 192.168.1.52 closed. [root@bric-ovirt-1 ~]# *So, what gives? I already disabled all ssh security in the physical host, and whitelisted all potential IPs from the engine using firewalld. Regardless, the engine can ssh to the host as root :-(. Is there maybe another user that's used for the "Wait for the host to be up" SSH test? Yes, I tried both passwords and certificates.* *Maybe what's really happening is that engine is not getting the right IP? bric-ovirt-engine is supposed to get 10.130.0.50, instead it never gets there, getting 192.168.1.52 from virbr0 in bric-ovirt-1. See below.* --== HOST NETWORK CONFIGURATION ==-- Please indicate the gateway IP address [10.130.0.1] Please indicate a nic to set ovirtmgmt bridge on: (p4p1, p5p1) [p4p1]: --== VM CONFIGURATION ==-- You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:17:1d:f8]: How should the engine VM network be configured (DHCP, Static)[DHCP]? static Please enter the IP address to be used for the engine VM []: 10.130.0.50 [ INFO ] The engine VM will be configured to use 10.130.0.50/25 Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM Engine VM DNS (leave it empty to skip) [10.130.0.2,10.130.0.3]: Add lines for the appliance itself and for this host to /etc/hosts on the engine VM? Note: ensuring that this host could resolve the engine VM hostname is still up to you (Yes, No)[No] Yes *[root@bric-ovirt-1 ~]# ip addr* 3: p4p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0a:f7:f1:c6:80 brd ff:ff:ff:ff:ff:ff inet 10.130.0.51/25 brd 10.130.0.127 scope global noprefixroute p4p1 valid_lft forever preferred_lft forever 28: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:25:7b:6f brd ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 brd 192.168.1.255 scope global virbr0 valid_lft forever preferred_lft forever 29: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:25:7b:6f brd ff:ff:ff:ff:ff:ff 30: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:17:1d:f8 brd ff:ff:ff:ff:ff:ff *The newly created engine VM does remain up even after hosted-engine --deploy errors out; just at the wrong IP. I haven't been able to make it get its real IP. At any rate, thank you very much for taking a look at my very long email. Any and all help would be really appreciated.* Cheers, -- Fredy -- *CONFIDENTIALITY NOTICE:* This e-mail message may contain material protected by the Health Insurance Portability and Accountability Act of 1996 and its implementing regulations and other state and federal laws and legal privileges. This message is only for the personal and confidential use of the individuals or organization to whom the message is addressed. If you are an unintended recipient, you have received this message in error, and any reading, distributing, copying or disclosure is unauthorized and strictly prohibited. All recipients are hereby notified that any unauthorized receipt does not waive any confidentiality obligations or privileges. If you have received this message in error, please notify the sender immediately at the above email address and confirm that you have deleted or destroyed the message.

3 7

Re: glusterfs
by Darrell Budic 15 Feb '20

15 Feb '20

Hi Eric- Glad you got thought that part. I don’t use iscsi backed volumes for my gluster storage, so I don’t much advice for you there. I’ve cc’d the ovirt users list back in, someone there may be able to help you futher. It’s good practice to reply to the list and specific people when conversing here, so you might want to watch to be sure you don’t drop the cc: in the future. Re: the storage master, it’s not related to where the VM disks are stored. Once you mange to get a new storage domain setup, you’ll be able to create disks on whichever domain you want, and that is how you determine what VM disk is hooked up to what. You can even have a VM with disks on multiple storage domains, can be good for high performance needs. The SDM may even move around if a domain become unavailable. You may want to check the list archives for discussion on this, I seem to recall some in the past. You also should confirm where the disks for your HA engine are located, they may be on your local raid disk instead of the iscsi disks if the SDM is on a local disk… Good luck, -Darrell > On Feb 14, 2020, at 3:03 PM, <eevans(a)digitaldatatechs.com> <eevans(a)digitaldatatechs.com> wrote: > > I enabled gluster and reinstalled and all went well. I set it for distributed replication so I need 3 nodes. I migrated the rest of my vm's and I am installing the third node shortly. > My biggest concern is getting the storage master on the lun it was previously set to. I get the snapshots on it so I can recover from disaster more easily. > I need it to persistently be on the lun I designate. > Also, I want the luns to be the gluster replication volumes but ther is no mount point in fstab on the machines. > I am new to gluster as well so please be patient with me. > > Eric Evans > Digital Data Services LLC. > 304.660.9080 > > > -----Original Message----- > From: Darrell Budic <budic(a)onholyground.com> > Sent: Friday, February 14, 2020 2:58 PM > To: eevans(a)digitaldatatechs.com > Subject: Re: [ovirt-users] Re: glusterfs > > You don’t even need to clean everything out, unless you need to destroy your old storage to the create new gluster backing bricks. Ovirt has a feature to migrate date between storage domains you can use to move an existing VM disk to a different storage facility. Note that “reinstall” is an option on the Installation menu for hosts, you do not need to remove the host first. It will pretty much just add the vdsm-gluster components in this case, safe to use. Just put it in maintenance first. > > You can certainly start fresh in the manner you describe if you want. > >> On Feb 14, 2020, at 11:56 AM, <eevans(a)digitaldatatechs.com> <eevans(a)digitaldatatechs.com> wrote: >> >> I have already imported a few vm's to see how the import process would go. So, I remove vm's and the current storage domains, and the hosts, then add gluster on the main ovirt node, then add the hosts back, storage back and reimport vm's? >> I want to make sure before I get started. My first go around with Ovirt and want to make sure before I change anything. >> >> Eric Evans >> Digital Data Services LLC. >> 304.660.9080 >> >> >> -----Original Message----- >> From: Darrell Budic <budic(a)onholyground.com> >> Sent: Friday, February 14, 2020 11:54 AM >> To: eevans(a)digitaldatatechs.com >> Cc: users(a)ovirt.org >> Subject: [ovirt-users] Re: glusterfs >> >> You can add it in to a running ovirt cluster, it just isn’t as automatic. First you need to enable Gluster in at the cluster settings level for a new or existing cluster. Then either install/reinstall your nodes, or install gluster manually and add vdsm-gluster packages. You can create a stand alone gluster server set this way, you don’t need any vddm packages, but then you have to create volumes manually. Once you’ve got that done, you can create bricks and volumes in the GUI or by hand, and then add a new storage domain and start using it. There may be ansible for some of this, but I haven’t done it in a while and am not sure what’s available there. >> >> -Darrell >> >>> On Feb 14, 2020, at 8:22 AM, eevans(a)digitaldatatechs.com wrote: >>> >>> I currently have 3 nodes, one is the engine node and 2 Centos 7 hosts, and I plan to add another Centos 7 KVM host once I get all the vm's migrated. I have san storage plus the raid 5 internal disks. All OS are installed on mirrored SAS raid 1. I want to use the raid 5 vd's as exports, ISO and use the 4TB iscsi for the vm's to run on. The iscsi has snapshots hourly and over write weekly. >>> So here is my question: I want to add glusterfs, but after further reading, that should have been done in the initial setup. I am not new to Linux, but new to Ovirt and need to know if I can implement glusterfs now or if it's a start from scratch situation. I really don't want to start over but would like the redundancy. >>> Any advice is appreciated. >>> Eric >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org To unsubscribe send an email to >>> users-leave(a)ovirt.org Privacy >>> Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z7PN44O >>> 7 >>> U2FC4WGIXQAQF3MRKUDJBWZD/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org Privacy >> Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GIJMUPFK >> PWOAXDDUKDGXO2VI2QFI3D6G/ >> > >

3 2

glusterfs
by eevans＠digitaldatatechs.com 14 Feb '20

14 Feb '20

I currently have 3 nodes, one is the engine node and 2 Centos 7 hosts, and I plan to add another Centos 7 KVM host once I get all the vm's migrated. I have san storage plus the raid 5 internal disks. All OS are installed on mirrored SAS raid 1. I want to use the raid 5 vd's as exports, ISO and use the 4TB iscsi for the vm's to run on. The iscsi has snapshots hourly and over write weekly. So here is my question: I want to add glusterfs, but after further reading, that should have been done in the initial setup. I am not new to Linux, but new to Ovirt and need to know if I can implement glusterfs now or if it's a start from scratch situation. I really don't want to start over but would like the redundancy. Any advice is appreciated. Eric

3 3

oVirt profesionaI suport
by Josep Manel Andrés Moscardó 14 Feb '20

14 Feb '20

Hi, I have seen in the website that there are some companies offering support, but from how updated some of them have their website, it doesn't like they are updated. Does anyone know of companies providing professional support right now? And also if someone has experience with Bobcare.... I cannot imaging myself asking the boss "There is a company named Bobcare that are selling oVirt support" Cheers. -- Josep Manel Andrés Moscardó Systems Engineer, IT Operations EMBL Heidelberg T +49 6221 387-8394

2 1

Re: Reimport disks
by Vinícius Ferrão 14 Feb '20

14 Feb '20

Import domain will work. The VM metadata is available on the OVF_STORE container, inside the domain. So even the names and settings come back. Them you gradually start moving the VMs to the Gluster storage. Sent from my iPhone > On 13 Feb 2020, at 11:42, Robert Webb <rwebb(a)ropeguru.com> wrote: > > Off the top of my head, would you use the "Import Domain" option? > > ________________________________________ > From: Christian Reiss <email(a)christian-reiss.de> > Sent: Thursday, February 13, 2020 9:30 AM > To: users > Subject: [ovirt-users] Reimport disks > > Hey folks, > > I created a new cluster with a new engine, everything is green and > running again (3 HCI, Gluster, this time Gluster 7.0 and CentOS7 hosts). > > I do have a backup of the /images/ directory from the old installation. > I tried copying (and preserving user/ permissions) into the new images > gluster dir and trying a domain -> scan to no avail. > > What is the correct way to introduce oVirt to "new" (or unknown) images? > > -Chris. > > -- > with kind regards, > mit freundlichen Gruessen, > > Christian Reiss > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/V7QZ5UZZYTYWG… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q2TV6CGLZYBHC…

2 1

Enabling Libgfapi in 4.3.8 - VMs won't start
by s.panicho＠gmail.com 14 Feb '20

14 Feb '20

Hello, all. I have a 3-node Hyperconverged oVirt 4.3.8 cluster running on CentOS 7.7 hosts. I was investigating poor Gluster performance and heard about libgfapi, so I thought I'd give it a shot. Looking through the documentation, followed by lots of threads and BZ reports, I've done the following to enable it: First, I shut down all VMs except the engine. Then... On the hosts: 1. setsebool -P virt_use_glusterfs on 2. dynamic_ownership=0 in /etc/libvirt/qemu.conf On the engine VM: 1. engine-config -s LibgfApiSupported=true --cver=4.3 2. systemctl restart ovirt-engine VMs now fail to launch. Am I doing this correctly? I should also note that the hosts still have the Gluster domain mounted via FUSE. Here's a relevant bit from engine.log: 2020-02-06T16:38:32.573511Z qemu-kvm: -drive file=gluster://node1.fs.trashnet.xyz:24007/vmstore/781717e5-1cff-43a1-b586-9941503544e8/images/a1d56b14-6d72-4f46-a0aa-eb0870c36bc4/a2314816-7970-49ce-a80c-ab0d1cf17c78,file.debug=4,format=qcow2,if=none,id=drive-ua-a1d56b14-6d72-4f46-a0aa-eb0870c36bc4,serial=a1d56b14-6d72-4f46-a0aa-eb0870c36bc4,werror=stop,rerror=stop,cache=none,discard=unmap,aio=native: Could not read qcow2 header: Invalid argument. The full engine.log from one of the attempts: 2020-02-06 16:38:24,909Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] add VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'(yumcache) to rerun treatment 2020-02-06 16:38:25,010Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-12) [] Rerun VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'. Called from VDS 'node2.ovirt.trashnet.xyz' 2020-02-06 16:38:25,091Z WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-216) [] EVENT_ID: USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM yumcache on Host node2.ovirt.trashnet.xyz. 2020-02-06 16:38:25,166Z INFO [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] Lock Acquired to object 'EngineLock:{exclusiveLocks='[df9dbac4-35c0-40ee-acd4-a1cfc959aa8b=VM]', sharedLocks=''}' 2020-02-06 16:38:25,179Z INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'}), log id: 2107f52a 2020-02-06 16:38:25,181Z INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 2107f52a 2020-02-06 16:38:25,298Z INFO [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] Running command: RunVmCommand internal: false. Entities affected : ID: df9dbac4-35c0-40ee-acd4-a1cfc959aa8b Type: VMAction group RUN_VM with role type USER 2020-02-06 16:38:25,313Z INFO [org.ovirt.engine.core.bll.utils.EmulatedMachineUtils] (EE-ManagedThreadFactory-engine-Thread-216) [] Emulated machine 'pc-q35-rhel7.6.0' which is different than that of the cluster is set for 'yumcache'(df9dbac4-35c0-40ee-acd4-a1cfc959aa8b) 2020-02-06 16:38:25,382Z INFO [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] START, UpdateVmDynamicDataVDSCommand( UpdateVmDynamicDataVDSCommandParameters:{hostId='null', vmId='df9dbac4-35c0-40ee-acd4-a1cfc959aa8b', vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@9774a64'}), log id: 4a83911f 2020-02-06 16:38:25,417Z INFO [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] FINISH, UpdateVmDynamicDataVDSCommand, return: , log id: 4a83911f 2020-02-06 16:38:25,418Z INFO [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] START, CreateVDSCommand( CreateVDSCommandParameters:{hostId='c3465ca2-395e-4c0c-b72e-b5b7153df452', vmId='df9dbac4-35c0-40ee-acd4-a1cfc959aa8b', vm='VM [yumcache]'}), log id: 5e07ba66 2020-02-06 16:38:25,420Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] START, CreateBrokerVDSCommand(HostName = node1.ovirt.trashnet.xyz, CreateVDSCommandParameters:{hostId='c3465ca2-395e-4c0c-b72e-b5b7153df452', vmId='df9dbac4-35c0-40ee-acd4-a1cfc959aa8b', vm='VM [yumcache]'}), log id: 1bfa03c4 2020-02-06 16:38:25,424Z INFO [org.ovirt.engine.core.vdsbroker.builder.vminfo.VmInfoBuildUtils] (EE-ManagedThreadFactory-engine-Thread-216) [] Kernel FIPS - Guid: c3465ca2-395e-4c0c-b72e-b5b7153df452 fips: false 2020-02-06 16:38:25,435Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] VM <?xml version="1.0" encoding="UTF-8"?><domain type="kvm" xmlns:ovirt-tune="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <name>yumcache</name> <uuid>df9dbac4-35c0-40ee-acd4-a1cfc959aa8b</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <iothreads>1</iothreads> <maxMemory slots="16">4194304</maxMemory> <vcpu current="1">16</vcpu> <sysinfo type="smbios"> <system> <entry name="manufacturer">oVirt</entry> <entry name="product">OS-NAME:</entry> <entry name="version">OS-VERSION:</entry> <entry name="serial">HOST-SERIAL:</entry> <entry name="uuid">df9dbac4-35c0-40ee-acd4-a1cfc959aa8b</entry> </system> </sysinfo> <clock offset="variable" adjustment="0"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <features> <acpi/> </features> <cpu match="exact"> <model>EPYC</model> <feature name="ibpb" policy="require"/> <feature name="virt-ssbd" policy="require"/> <topology cores="1" threads="1" sockets="16"/> <numa> <cell id="0" cpus="0" memory="1048576"/> </numa> </cpu> <cputune/> <devices> <input type="tablet" bus="usb"/> <channel type="unix"> <target type="virtio" name="ovirt-guest-agent.0"/> <source mode="bind" path="/var/lib/libvirt/qemu/channels/df9dbac4-35c0-40ee-acd4-a1cfc959aa8b.ovirt-guest-agent.0"/> </channel> <channel type="unix"> <target type="virtio" name="org.qemu.guest_agent.0"/> <source mode="bind" path="/var/lib/libvirt/qemu/channels/df9dbac4-35c0-40ee-acd4-a1cfc959aa8b.org.qemu.guest_agent.0"/> </channel> <controller type="pci" model="pcie-root-port" index="1"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x02" type="pci" multifunction="on"/> </controller> <memballoon model="virtio"> <stats period="5"/> <alias name="ua-27c77007-3a3c-4431-958d-90fd1c7257dd"/> <address bus="0x05" domain="0x0000" function="0x0" slot="0x00" type="pci"/> </memballoon> <controller type="pci" model="pcie-root-port" index="2"> <address bus="0x00" domain="0x0000" function="0x1" slot="0x02" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="9"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x03" type="pci" multifunction="on"/> </controller> <controller type="sata" index="0"> <address bus="0x00" domain="0x0000" function="0x2" slot="0x1f" type="pci"/> </controller> <rng model="virtio"> <backend model="random">/dev/urandom</backend> <alias name="ua-51960005-6b95-47e9-82a7-67d5e0d6cf8a"/> </rng> <controller type="pci" model="pcie-root-port" index="6"> <address bus="0x00" domain="0x0000" function="0x5" slot="0x02" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="15"> <address bus="0x00" domain="0x0000" function="0x6" slot="0x03" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="13"> <address bus="0x00" domain="0x0000" function="0x4" slot="0x03" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="7"> <address bus="0x00" domain="0x0000" function="0x6" slot="0x02" type="pci"/> </controller> <graphics type="vnc" port="-1" autoport="yes" passwd="*****" passwdValidTo="1970-01-01T00:00:01" keymap="en-us"> <listen type="network" network="vdsm-ovirtmgmt"/> </graphics> <controller type="pci" model="pcie-root-port" index="16"> <address bus="0x00" domain="0x0000" function="0x7" slot="0x03" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="12"> <address bus="0x00" domain="0x0000" function="0x3" slot="0x03" type="pci"/> </controller> <video> <model type="qxl" vram="32768" heads="1" ram="65536" vgamem="16384"/> <alias name="ua-8a295e96-40c3-44de-a3b0-1c4a685a5473"/> <address bus="0x00" domain="0x0000" function="0x0" slot="0x01" type="pci"/> </video> <graphics type="spice" port="-1" autoport="yes" passwd="*****" passwdValidTo="1970-01-01T00:00:01" tlsPort="-1"> <channel name="main" mode="secure"/> <channel name="inputs" mode="secure"/> <channel name="cursor" mode="secure"/> <channel name="playback" mode="secure"/> <channel name="record" mode="secure"/> <channel name="display" mode="secure"/> <channel name="smartcard" mode="secure"/> <channel name="usbredir" mode="secure"/> <listen type="network" network="vdsm-ovirtmgmt"/> </graphics> <controller type="pci" model="pcie-root-port" index="5"> <address bus="0x00" domain="0x0000" function="0x4" slot="0x02" type="pci"/> </controller> <controller type="usb" model="qemu-xhci" index="0" ports="8"> <address bus="0x02" domain="0x0000" function="0x0" slot="0x00" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="4"> <address bus="0x00" domain="0x0000" function="0x3" slot="0x02" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="3"> <address bus="0x00" domain="0x0000" function="0x2" slot="0x02" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="11"> <address bus="0x00" domain="0x0000" function="0x2" slot="0x03" type="pci"/> </controller> <controller type="scsi" model="virtio-scsi" index="0"> <driver iothread="1"/> <alias name="ua-d0bf6fcd-7aa2-4658-b7cc-3dac259b7ad2"/> <address bus="0x03" domain="0x0000" function="0x0" slot="0x00" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="8"> <address bus="0x00" domain="0x0000" function="0x7" slot="0x02" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="14"> <address bus="0x00" domain="0x0000" function="0x5" slot="0x03" type="pci"/> </controller> <controller type="pci" model="pcie-root-port" index="10"> <address bus="0x00" domain="0x0000" function="0x1" slot="0x03" type="pci"/> </controller> <controller type="virtio-serial" index="0" ports="16"> <address bus="0x04" domain="0x0000" function="0x0" slot="0x00" type="pci"/> </controller> <channel type="spicevmc"> <target type="virtio" name="com.redhat.spice.0"/> </channel> <controller type="pci" model="pcie-root"/> <interface type="bridge"> <model type="virtio"/> <link state="up"/> <source bridge="vmnet"/> <alias name="ua-ceda0ef6-9139-4e5c-8840-86fe344ecbd3"/> <address bus="0x01" domain="0x0000" function="0x0" slot="0x00" type="pci"/> <mac address="56:6f:91:b9:00:05"/> <mtu size="1500"/> <filterref filter="vdsm-no-mac-spoofing"/> <bandwidth/> </interface> <disk type="file" device="cdrom" snapshot="no"> <driver name="qemu" type="raw" error_policy="report"/> <source file="" startupPolicy="optional"> <seclabel model="dac" type="none" relabel="no"/> </source> <target dev="sdc" bus="sata"/> <readonly/> <alias name="ua-bdf99844-2d02-411b-90bb-671ee26764cb"/> <address bus="0" controller="0" unit="2" type="drive" target="0"/> </disk> <disk snapshot="no" type="network" device="disk"> <target dev="sda" bus="scsi"/> <source protocol="gluster" name="vmstore/781717e5-1cff-43a1-b586-9941503544e8/images/a1d56b14-6d72-4f46-a0aa-eb0870c36bc4/a2314816-7970-49ce-a80c-ab0d1cf17c78"> <host name="node1.fs.trashnet.xyz" port="0"/> <seclabel model="dac" type="none" relabel="no"/> </source> <driver name="qemu" discard="unmap" io="native" type="qcow2" error_policy="stop" cache="none"/> <alias name="ua-a1d56b14-6d72-4f46-a0aa-eb0870c36bc4"/> <address bus="0" controller="0" unit="0" type="drive" target="0"/> <boot order="1"/> <serial>a1d56b14-6d72-4f46-a0aa-eb0870c36bc4</serial> </disk> <lease> <key>df9dbac4-35c0-40ee-acd4-a1cfc959aa8b</key> <lockspace>781717e5-1cff-43a1-b586-9941503544e8</lockspace> <target offset="6291456" path="/rhev/data-center/mnt/glusterSD/node1.fs.trashnet.xyz:_vmstore/781717e5-1cff-43a1-b586-9941503544e8/dom_md/xleases"/> </lease> </devices> <pm> <suspend-to-disk enabled="no"/> <suspend-to-mem enabled="no"/> </pm> <os> <type arch="x86_64" machine="pc-q35-rhel7.6.0">hvm</type> <smbios mode="sysinfo"/> </os> <metadata> <ovirt-tune:qos/> <ovirt-vm:vm> <ovirt-vm:minGuaranteedMemoryMb type="int">512</ovirt-vm:minGuaranteedMemoryMb> <ovirt-vm:clusterVersion>4.3</ovirt-vm:clusterVersion> <ovirt-vm:custom/> <ovirt-vm:device mac_address="56:6f:91:b9:00:05"> <ovirt-vm:custom/> </ovirt-vm:device> <ovirt-vm:device devtype="disk" name="sda"> <ovirt-vm:poolID>2ffaec76-462c-11ea-b155-00163e512202</ovirt-vm:poolID> <ovirt-vm:volumeID>a2314816-7970-49ce-a80c-ab0d1cf17c78</ovirt-vm:volumeID> <ovirt-vm:imageID>a1d56b14-6d72-4f46-a0aa-eb0870c36bc4</ovirt-vm:imageID> <ovirt-vm:domainID>781717e5-1cff-43a1-b586-9941503544e8</ovirt-vm:domainID> </ovirt-vm:device> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:resumeBehavior>kill</ovirt-vm:resumeBehavior> </ovirt-vm:vm> </metadata> </domain> 2020-02-06 16:38:25,455Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] FINISH, CreateBrokerVDSCommand, return: , log id: 1bfa03c4 2020-02-06 16:38:25,494Z INFO [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] FINISH, CreateVDSCommand, return: WaitForLaunch, log id: 5e07ba66 2020-02-06 16:38:25,495Z INFO [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-216) [] Lock freed to object 'EngineLock:{exclusiveLocks='[df9dbac4-35c0-40ee-acd4-a1cfc959aa8b=VM]', sharedLocks=''}' 2020-02-06 16:38:25,533Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-216) [] EVENT_ID: USER_STARTED_VM(153), VM yumcache was started by admin@internal-authz (Host: node1.ovirt.trashnet.xyz). 2020-02-06 16:38:33,300Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-5) [] VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b' was reported as Down on VDS 'c3465ca2-395e-4c0c-b72e-b5b7153df452'(node1.ovirt.trashnet.xyz) 2020-02-06 16:38:33,301Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-5) [] START, DestroyVDSCommand(HostName = node1.ovirt.trashnet.xyz, DestroyVmVDSCommandParameters:{hostId='c3465ca2-395e-4c0c-b72e-b5b7153df452', vmId='df9dbac4-35c0-40ee-acd4-a1cfc959aa8b', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 1f951ea9 2020-02-06 16:38:33,478Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [] Fetched 2 VMs from VDS 'c3465ca2-395e-4c0c-b72e-b5b7153df452' 2020-02-06 16:38:33,545Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-5) [] FINISH, DestroyVDSCommand, return: , log id: 1f951ea9 2020-02-06 16:38:33,546Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-5) [] VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'(yumcache) moved from 'WaitForLaunch' --> 'Down' 2020-02-06 16:38:33,623Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-5) [] EVENT_ID: VM_DOWN_ERROR(119), VM yumcache is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: [2020-02-06 16:38:31.723977] E [MSGID: 108006] [afr-common.c:5323:__afr_handle_child_down_event] 0-vmstore-replicate-0: All subvolumes are down. Going offline until at least one of them comes back up. [2020-02-06 16:38:31.724765] I [io-stats.c:4027:fini] 0-vmstore: io-stats translator unloaded 2020-02-06T16:38:32.573511Z qemu-kvm: -drive file=gluster://node1.fs.trashnet.xyz:24007/vmstore/781717e5-1cff-43a1-b586-9941503544e8/images/a1d56b14-6d72-4f46-a0aa-eb0870c36bc4/a2314816-7970-49ce-a80c-ab0d1cf17c78,file.debug=4,format=qcow2,if=none,id=drive-ua-a1d56b14-6d72-4f46-a0aa-eb0870c36bc4,serial=a1d56b14-6d72-4f46-a0aa-eb0870c36bc4,werror=stop,rerror=stop,cache=none,discard=unmap,aio=native: Could not read qcow2 header: Invalid argument. 2020-02-06 16:38:33,624Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-5) [] add VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'(yumcache) to rerun treatment 2020-02-06 16:38:33,796Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-5) [] Rerun VM 'df9dbac4-35c0-40ee-acd4-a1cfc959aa8b'. Called from VDS 'node1.ovirt.trashnet.xyz' 2020-02-06 16:38:33,899Z WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-223) [] EVENT_ID: USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM yumcache on Host node1.ovirt.trashnet.xyz.

6 11

hosted engine storage does not heal
by g.vasilopoulos＠uoc.gr 13 Feb '20

13 Feb '20

Hello We have a problem with hosted engine storage after updating one host which serves as a gluster server for the engine (the setup is gluster replica 3 with local disks from 3 hypervisors) Volume heal command shows [root@o5-car0118 engine]# gluster volume heal engine info Brick o5-car0118.gfs-int.uoc.gr:/gluster_bricks/engine/engine /a1ecca6f-1487-492d-b9bf-d3fb60f1bc99/images/e3a3ef50-56b6-48b0-a9f8-2d6382e2286e/b6973d5b-cc7a-4abd-8d2d-94f551936a97.meta /a1ecca6f-1487-492d-b9bf-d3fb60f1bc99/images/f5e576d4-eea7-431b-a0f0-f8a557006471/464518c5-f79c-4271-9d97-995981cde2cb.meta Status: Connected Number of entries: 2 Brick o2-car0121.gfs-int.uoc.gr:/gluster_bricks/engine/engine /a1ecca6f-1487-492d-b9bf-d3fb60f1bc99/images/e3a3ef50-56b6-48b0-a9f8-2d6382e2286e/b6973d5b-cc7a-4abd-8d2d-94f551936a97.meta /a1ecca6f-1487-492d-b9bf-d3fb60f1bc99/images/f5e576d4-eea7-431b-a0f0-f8a557006471/464518c5-f79c-4271-9d97-995981cde2cb.meta Status: Connected Number of entries: 2 Brick o9-car0114.gfs-int.uoc.gr:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 On all the gluster servers I notice that the affected directories have date in 1970. [root@o5-car0118 images]# ls -al σύνολο 24 drwxr-xr-x. 23 vdsm kvm 8192 Σεπ 24 12:07 . drwxr-xr-x. 6 vdsm kvm 64 Σεπ 19 2018 .. drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 2bac658f-70ce-4adb-ab68-a0f0c205c70c drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 3034a69c-b5b5-46fa-a393-59ea46635142 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 5538ae6b-ccc6-4861-b71b-6b2c7af2e0ab drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 66dbce25-8863-42b5-904a-484f8e9c225a drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 6c049108-28f7-47d9-8d54-4ac2697dcba8 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 72702607-1896-420d-931a-42c9f01d37f1 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 7c617da4-ab6b-4791-80be-541f5be60dd8 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 902a16d3-6494-4840-a528-b49972f9c332 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 96fd6116-7983-4385-bca6-e6ca8edc94ca drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 abd875cd-96b6-47a6-b6a3-ae35300a21cc drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 add7bc92-1a40-474d-9255-53ac861b75ed drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 b7b06df7-465f-4fc7-a214-033b7dca6bc7 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 c0ecacac-26c6-40d9-87da-af17d9de8d21 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 c4d2d5da-2a15-4735-8919-324ae8372064 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 c7e0c784-bb8e-4024-95df-b6f4267b0208 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 d1f1ff5a-387d-442c-9240-1c58e4d6f8a7 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 d3e172cb-b6dd-4867-a9cd-f4fa006648bc drwxr-xr-x. 2 vdsm kvm 8192 Ιαν 1 1970 e3a3ef50-56b6-48b0-a9f8-2d6382e2286e <----- drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 e477ec02-11ab-4d92-b5fd-44e91fbde7f9 drwxr-xr-x. 2 vdsm kvm 149 Αύγ 2 2019 e839485b-b0be-47f6-9847-b691e02ce9a4 drwxr-xr-x. 2 vdsm kvm 8192 Ιαν 1 1970 f5e576d4-eea7-431b-a0f0-f8a557006471 <----- I think this has something to do with a gluster bug. Is there a way to correct this and heal the volume? Thank you!

3 2

Re: Reimport disks
by Strahil Nikolov 13 Feb '20

13 Feb '20

On February 13, 2020 4:38:06 PM GMT+02:00, Robert Webb <rwebb(a)ropeguru.com> wrote: >Off the top of my head, would you use the "Import Domain" option? > >________________________________________ >From: Christian Reiss <email(a)christian-reiss.de> >Sent: Thursday, February 13, 2020 9:30 AM >To: users >Subject: [ovirt-users] Reimport disks > >Hey folks, > >I created a new cluster with a new engine, everything is green and >running again (3 HCI, Gluster, this time Gluster 7.0 and CentOS7 >hosts). > >I do have a backup of the /images/ directory from the old installation. >I tried copying (and preserving user/ permissions) into the new images >gluster dir and trying a domain -> scan to no avail. > >What is the correct way to introduce oVirt to "new" (or unknown) >images? > >-Chris. > >-- >with kind regards, >mit freundlichen Gruessen, > >Christian Reiss >_______________________________________________ >Users mailing list -- users(a)ovirt.org >To unsubscribe send an email to users-leave(a)ovirt.org >Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/ >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/V7QZ5UZZYTYWG… >_______________________________________________ >Users mailing list -- users(a)ovirt.org >To unsubscribe send an email to users-leave(a)ovirt.org >Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >oVirt Code of Conduct: >https://www.ovirt.org/community/about/community-guidelines/ >List Archives: >https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q2TV6CGLZYBHC… Create a temp storage, then detach and remove. Manually copy the backup to the same directory . Attach again the storage domain and there should be a 'Import VMs' & ' Import templates' tabs in that domain. Then you just need to select VM, pick a cluster and import. Best Regards, Strqhil Nikolov

1 0

Unable to create VMs under ovirt 4.4
by Dirk Streubel 13 Feb '20

13 Feb '20

Hello List, after a few Problems with the package "java-client-kubevirt" and some updates Problems on my Hypervisor and my ovirt-engine i make a totally fresh installation of ovirt 4.4. So, after the new installation i can't create a Linux VM. I get a message that i don't understand: Feb 13 10:44:12 hypervisor vdsm[6644]: WARN Attempting to add an existing net user: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7 Feb 13 10:44:14 hypervisor journal[2698]: the CPU is incompatible with host CPU: Host-CPU stellt nicht die erforderlichen Funktionen bereit: hle, rtm Feb 13 10:44:15 hypervisor vdsm[6644]: WARN Attempting to remove a non existing network: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7 Feb 13 10:44:15 hypervisor vdsm[6644]: WARN Attempting to remove a non existing net user: ovirtmgmt/9ab115dd-1c21-476d-955f-d4164e4bc5c7 So, which function are missing? I don't know what "hle" and "rtm" stands for? And searching with Google get no Results. And it is interesting before the new Installation i was possible to create a Debian and CentOS VM under ovirt 4.4 Regards Dirk

4 4

Reimport disks
by Christian Reiss 13 Feb '20

13 Feb '20

Hey folks, I created a new cluster with a new engine, everything is green and running again (3 HCI, Gluster, this time Gluster 7.0 and CentOS7 hosts). I do have a backup of the /images/ directory from the old installation. I tried copying (and preserving user/ permissions) into the new images gluster dir and trying a domain -> scan to no avail. What is the correct way to introduce oVirt to "new" (or unknown) images? -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 2

Re: Cannot Increase Hosted Engine VM Memory
by Serhiy Morhun 13 Feb '20

13 Feb '20

Hello, did anyone find a resolution for this issue? I'm having exactly the same problem: Hosted Engine VM is running with 5344MB of RAM, when trying to increase to 8192 it would not accept the change because the difference is not divisible by 256. When trying to increase to 8160 the change is accepted but log shows "Hotset memory: changed the amount of memory on VM HostedEngine from 5344 to 5344" at the same time amount of guaranteed memory does increase to 8160 which, in turn, starts generating error messages that VM does not have all the guaranteed RAM. Serhiy Morhun -- *-----------------------------------------------------------------------------------*** *THE INFORMATION CONTAINED IN THIS MESSAGE (E-MAIL AND ANY ATTACHMENTS) IS INTENDED ONLY FOR THE INDIVIDUAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENT(S).* If any reader of this message is not an intended recipient or any agent responsible for delivering it to an intended recipient, you are hereby notified that you have received this document in error, and that any review, dissemination, distribution, copying or other use of this message is prohibited. If you have received this message in error, please notify us immediately by reply e-mail message or by telephone and delete the original message from your e-mail system and/or computer database. Thank you. *-----------------------------------------------------------------------------------* **NOTICE**: *You are advised that e-mail correspondence and attachments between the public and the Ridgewood Board of Education are obtainable by any person who files a request under the NJ Open Public Records Act (OPRA) unless it is subject to a specific OPRA exception. You should have no expectation that the content of e-mails sent to or from school district e-mail addresses, or between the public and school district officials and employees, will remain private.* *-----------------------------------------------------------------------------------*

3 3

Administrative portal host creation installaFailed
by krisibo01＠gmail.com 12 Feb '20

12 Feb '20

Hello, I am a student and as a school project i have to make virtual environment using oVirt.I am still confused how exactly oVirt is working i just installed its engine with the default settings that are recomended in the guide and i am trying ot make a new host with the default data center and cluster. The host is created but it is staying in installFailed mode. http://prntscr.com/r0u2eo I am using the ip address of the device (It is headless server) that has the oVirt-engine. I already checked if the virtualization is enabled in the bios because i thought it might be the problem. When i checked the engine.log file for test1(it is the name of the host i am trying to make) i got this: 2020-02-11 11:21:29,582-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-5) [602685d9-6eb3-415f-b705-f94a76b1f77a] Failed to authenticate session with host 'test1': SSH authentication to 'root(a)192.168.66.1' failed. Please verify provided credentials. Make sure host is configured for password authentication 2020-02-11 11:22:10,555-05 INFO [org.ovirt.engine.core.vdsbroker.RemoveVdsVDSCommand] (default task-5) [2919924c] START, RemoveVdsVDSCommand(HostName = test1, RemoveVdsVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec'}), log id: 32419129 2020-02-11 11:22:10,562-05 INFO [org.ovirt.engine.core.vdsbroker.AddVdsVDSCommand] (default task-5) [2919924c] START, AddVdsVDSCommand(HostName = test1, AddVdsVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec'}), log id: 2697f96 2020-02-11 11:22:10,602-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [2919924c] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Power Management configuration for Host test1. 2020-02-11 11:22:10,652-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-5) [2919924c] EVENT_ID: USER_ADD_VDS(42), Host test1 was added by admin@internal-authz. 2020-02-11 11:22:10,722-05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] Before Installation host 6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec, test1 2020-02-11 11:22:10,785-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] START, SetVdsStatusVDSCommand(HostName = test1, SetVdsStatusVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', status='Installing', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2a396f44 2020-02-11 11:22:10,877-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Connected to host 192.168.66.76 with SSH key fingerprint: SHA256:UPDIq/SAKblGbU7sQ/vAkOiMraW0fmwi/kJ0mX0yanM. 2020-02-11 11:22:12,644-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Initializing. 2020-02-11 11:22:12,776-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment setup. 2020-02-11 11:22:13,436-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment packages setup. 2020-02-11 11:22:28,470-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Programs detection. 2020-02-11 11:22:28,504-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Environment customization. 2020-02-11 11:22:31,715-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Kdump supported. 2020-02-11 11:22:32,182-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Logs at host located at: '/tmp/ovirt-host-deploy-20200211112211-a6mgfh.log'. 2020-02-11 11:22:32,303-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS_WARNING(510), Host test1 installation in progress . Aborted. 2020-02-11 11:22:32,315-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Clean up. 2020-02-11 11:22:32,327-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Pre-termination. 2020-02-11 11:22:32,363-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20200211112232-192.168.66.76-1de230f5.log'. 2020-02-11 11:22:32,633-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host test1. Stage: Termination. 2020-02-11 11:22:32,777-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host test1: Command returned failure code 1 during SSH session 'root(a)192.168.66.76'. 2020-02-11 11:22:32,791-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] Host installation failed for host '6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', 'test1': Host 192.168.66.76 reports unique id which already registered for test 2020-02-11 11:22:32,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] START, SetVdsStatusVDSCommand(HostName = test1, SetVdsStatusVDSCommandParameters:{hostId='6b9ba2e2-f16d-45e3-b44e-ff0eaac6c8ec', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 6fba93de 2020-02-11 11:22:32,831-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-29889) [1de230f5] EVENT_ID: VDS_INSTALL_FAILED(505), Host test1 installation failed. Host 192.168.66.76 reports unique id which already registered for test.

2 1

DataAccessResourceFailureException from one to to the next
by gregor 12 Feb '20

12 Feb '20

After one day I'm not able to login to the ovirt-engine webinterface with the following error message: "org.springframework.dao.DataAccessResourceFailureException: Error retrieving database metadata; nested exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is org.postgresql.util.PSQLException: This connection has been closed." Things I tried which didn't help: - engine: check if the database is up - eninge: reboot - hosts: reboot - engine: xfs_repair Any ideas? regards gregor

2 3

Ovirt with Ceph
by systems＠oisystems.co.uk 11 Feb '20

11 Feb '20

is it possible to crate a storage pool on the same Centos hosts as the Gluster Storage ? if we use Gluster for the Hosted engine and use Ceph for VM's ? it seems Ceph is much more stable than Gluster and I like the way storage is more transparent in Ceph

2 1

Compatibility version for VmPools
by nicolas＠devels.es 11 Feb '20

11 Feb '20

Hi, We recently upgraded to 4.3.8 from 4.1.9. In the update process we set Cluster and DataCenter compatibility versions to 4.3, but now we're facing a problem with VmPools. They cannot be edited and 4.1 as compatibility level is still forcibly set. That means that when new machines are added to the pool, compatibility version 4.1 is set on them and they cannot be started as a message stating the following pops up: Failed to run VM XXX-34 due to a failed validation: [Cannot run VM. The Custom Compatibility Version of VM XXX-34 (4.1) is not supported in Data Center compatibility version 4.3.] (User: admin@internal). Is there a workaround to start those machines, or a way to fix the problem? Thanks.

1 0

Update hosted engine to 4.3.8 from 4.3.7 questions
by d03＠bornfree.org 10 Feb '20

10 Feb '20

I'd like to update my hosted engine to version 4.3.8 from 4.3.7, but have concerns. First, on the hosted engine, yum reports that several packages are version locked. Specifically: 0:ovirt-engine-webadmin-portal-4.3.8.2-1.el7.* 0:ovirt-engine-dwh-4.3.8-1.el7.* 0:ovirt-engine-tools-backup-4.3.8.2-1.el7.* 0:ovirt-engine-restapi-4.3.8.2-1.el7.* 0:ovirt-engine-dbscripts-4.3.8.2-1.el7.* 0:ovirt-engine-4.3.8.2-1.el7.* 0:ovirt-engine-backend-4.3.8.2-1.el7.* 0:ovirt-engine-tools-4.3.8.2-1.el7.* Is this normal and is it okay to proceed with the update? If it is not normal, what can I do to correct the problem? Also, what is the correct procedure to update the engine? Although I tried to read the documentation, I have encountered conflicting documents so I must ask. Sorry. This is how I understand it, but am not confident that it is correct: 1. Enable Global HA Maintenance mode. 2. On the engine, run # yum update ovirt* 3. On the engine, run # engine-setup 4. On the engine, run # yum update 4. Reboot the hosted engine. Is "systemctl reboot" acceptable or do I have to do a "hosted-engine --vm-restart" from a host? 5. Disable Global HA Maintenance mode. Your expert guidance is much appreciated.

3 3

issue connecting 4.3.8 node to nfs domain
by Jorick Astrego 10 Feb '20

10 Feb '20

Hi, Something weird is going on with our ovirt node 4.3.8 install mounting a nfs share. We have a NFS domain for a couple of backup disks and we have a couple of 4.2 nodes connected to it. Now I'm adding a fresh cluster of 4.3.8 nodes and the backupnfs mount doesn't work. (annoying you cannot copy the text from the events view) The domain is up and working ID:f5d2f7c6-093f-46d6-a844-224d92db5ef9 Size:10238 GiB Available:2491 GiB Used:7747 GiB Allocated:3302 GiB Over Allocation Ratio:37% Images:7 Path:*.*.*.*:/data/ovirt NFS Version:AUTO Warning Low Space Indicator:10% (1023 GiB) Critical Space Action Blocker:5 GiB But somehow the node appears to thin thinks it's an LVM volume? It tries to find the VGs volume group but fails... which is not so strange as it is an NFS volume: 2020-02-05 14:17:54,190+0000 WARN (monitor/f5d2f7c) [storage.LVM] Reloading VGs failed (vgs=[u'f5d2f7c6-093f-46d6-a844-224d92db5ef9'] rc=5 out=[] err=[' Volume group "f5d2f7c6-093f-46d6-a844-224d92db5ef9" not found', ' Cannot process volume group f5d2f7c6-093f-46d6-a844-224d92db5ef9']) (lvm:470) 2020-02-05 14:17:54,201+0000 ERROR (monitor/f5d2f7c) [storage.Monitor] Setting up monitor for f5d2f7c6-093f-46d6-a844-224d92db5ef9 failed (monitor:330) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 327, in _setupLoop self._setupMonitor() File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 349, in _setupMonitor self._produceDomain() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 159, in wrapper value = meth(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 367, in _produceDomain self.domain = sdCache.produce(self.sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'f5d2f7c6-093f-46d6-a844-224d92db5ef9',) The volume is actually mounted fine on the node: On NFS server Feb 5 15:47:09 back1en rpc.mountd[4899]: authenticated mount request from *.*.*.*:673 for /data/ovirt (/data/ovirt) On the host mount|grep nfs *.*.*.*:/data/ovirt on /rhev/data-center/mnt/*.*.*.*:_data_ovirt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=*.*.*.*,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=*.*.*.*) And I can see the files: ls -alrt /rhev/data-center/mnt/*.*.*.*:_data_ovirt total 4 drwxr-xr-x. 5 vdsm kvm 61 Oct 26 2016 1ed0a635-67ee-4255-aad9-b70822350706 -rwxr-xr-x. 1 vdsm kvm 0 Feb 5 14:37 __DIRECT_IO_TEST__ drwxrwxrwx. 3 root root 86 Feb 5 14:37 . drwxr-xr-x. 5 vdsm kvm 4096 Feb 5 14:37 .. Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

3 11

Failed to add vm as host (CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION)
by Ritesh Chikatwar 10 Feb '20

10 Feb '20

Hello, error is Host host moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all. Vm is running centos 8: enabled nested virtualization by this way: cat /sys/module/kvm_intel/parameters/nested vi /etc/modprobe.d/kvm-nested.conf ---> Contains options kvm-intel nested=1 options kvm-intel enable_shadow_vmcs=1 options kvm-intel enable_apicv=1 options kvm-intel ept=1 modprobe -r kvm_intel modprobe -a kvm_intel cat /sys/module/kvm_intel/parameters/nested --> 1 Engine Log: https://pastebin.com/hgrwzRhE Ovirt-engine Cluster Version is 4.4 I am running ovirt engine on fedora 30. Cluster CPU Type Intel Nehlam Family. Any thoughts will be appreciated. Rit

2 2

Error while making hosts
by krisibo01＠gmail.com 09 Feb '20

09 Feb '20

Hello, I am a student and as a school project i have to make virtual environment using oVirt. I just installed the oVirt-engine with the recomended configuration in the documentation and when i try to make a new host i got this error: Error while executing action: Cannot add Host. Connecting to host via SSH has failed, verify that the host is reachable (IP address, routable address etc.) You may refer to the engine.log file for further details. When i checked the log file the only thing that was there is that there is: 2020-02-06 03:59:24,594-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-30) [d54ee4df-32c8-474c-b315-51ad1131091a] Failed to establish session with host 'test': SSH connection timed out connecting to 'root(a)10.10.0.20' I was trying to make the host following this steps: Adding a Host to the oVirt Engine 1.Click Compute → Hosts. 2.Click New. 3.Use the drop-down list to select the Data Center and Host Cluster for the new host. 4.Enter the Name and the Hostname of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field. 5.Select an authentication method to use for the Engine to access the host. Enter the root user’s password to use password authentication. Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication. 6.Click the Advanced Parameters button to expand the advanced host settings. i. Optionally disable automatic firewall configuration. ii. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically. 7.Optionally configure Power Management, SPM, Console, Network Provider, and Kernel. See Explanation of Settings and Controls in the New Host and Edit Host Windows for more information. Hosted Engine is used when deploying or undeploying a host for a self-hosted engine deployment. 8.Click OK. The new host displays in the list of hosts with a status of Installing, and you can view the progress of the installation in the details pane. After a brief delay the host status changes to Up.

2 2

Re: Power Management - drac5
by eevans＠digitaldatatechs.com 09 Feb '20

09 Feb '20

I have the same issue on Dell R710's. Power management is optional and I don't use it. It doesn't affect it either way. I am connected to APC Smart UPS 3000. It will not find the apc either. Any other opinions would be welcome. He's right, no documentation about this issue. Eric Evans Digital Data Services LLC. 304.660.9080 -----Original Message----- From: Robert Webb <rwebb(a)ropeguru.com> Sent: Monday, February 03, 2020 12:47 PM To: users <users(a)ovirt.org> Subject: [ovirt-users] Power Management - drac5 I have 3 Dell R410's with iDrac6 Enterprise capability. I am trying to get power management set up but the test will not pass and I am not finding the docs very helpful. I have put in the IP, user name, password, and drac5 as the type. I have tested both with and without secure checked and always get, "Test failed: Internal JSON-RPC error". idrac log shows: 2020 Feb 3 17:41:22 os[19772] root closing session from 192.168.1.12 2020 Feb 3 17:41:17 os[19746] root login from 192.168.1.12 Can someone please guide me in the right direction? _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RKFEK2ORWOODC…

5 5

Re: issue connecting 4.3.8 node to nfs domain
by Jorick Astrego 09 Feb '20

09 Feb '20

On 2/6/20 1:44 PM, Amit Bawer wrote: > > > On Thu, Feb 6, 2020 at 1:07 PM Jorick Astrego <jorick(a)netbulae.eu > <mailto:jorick@netbulae.eu>> wrote: > > Here you go, this is from the activation I just did a couple of > minutes ago. > > I was hoping to see how it was first connected to host, but it doesn't > go that far back. Anyway, the storage domain type is set from engine > and vdsm never try to guess it as far as I saw. I put the host in maintenance and activated it again, this should give you some more info. See attached log. > Could you query the engine db about the misbehaving domain and paste > the results? > > # su - postgres > Last login: Thu Feb 6 07:17:52 EST 2020 on pts/0 > -bash-4.2$ LD_LIBRARY_PATH=/opt/rh/rh-postgresql10/root/lib64/ > /opt/rh/rh-postgresql10/root/usr/bin/psql engine > psql (10.6) > Type "help" for help. > engine=# select * from storage_domain_static where id = > 'f5d2f7c6-093f-46d6-a844-224d92db5ef9' ; engine=# select * from storage_domain_static where id = 'f5d2f7c6-093f-46d6-a844-224d92db5ef9' ; id | storage | storage_name | storage_domain_type | storage_type | storage_domain_format_type | _create_date | _update_date | recoverable | la st_time_used_as_master | storage_description | storage_comment | wipe_after_delete | warning_low_space_indicator | critical_space_action_blocker | first_metadata_device | vg_metadata_device | discard_after_delete | backup | warning_low_co nfirmed_space_indicator | block_size --------------------------------------+--------------------------------------+--------------+---------------------+--------------+----------------------------+-------------------------------+-----------------------------+-------------+--- -----------------------+---------------------+-----------------+-------------------+-----------------------------+-------------------------------+-----------------------+--------------------+----------------------+--------+--------------- ------------------------+------------ f5d2f7c6-093f-46d6-a844-224d92db5ef9 | b8b456f0-27c3-49b9-b5e9-9fa81fb3cdaa | backupnfs | 1 | 1 | 4 | 2018-01-19 13:31:25.899738+01 | 2019-02-14 14:36:22.3171+01 | t | 1530772724454 | | | f | 10 | 5 | | | f | f | 0 | 512 (1 row) Regards, Jorick > > On 2/6/20 11:23 AM, Amit Bawer wrote: >> >> >> On Thu, Feb 6, 2020 at 11:07 AM Jorick Astrego >> <jorick(a)netbulae.eu <mailto:jorick@netbulae.eu>> wrote: >> >> Hi, >> >> Something weird is going on with our ovirt node 4.3.8 install >> mounting a nfs share. >> >> We have a NFS domain for a couple of backup disks and we have >> a couple of 4.2 nodes connected to it. >> >> Now I'm adding a fresh cluster of 4.3.8 nodes and the >> backupnfs mount doesn't work. >> >> (annoying you cannot copy the text from the events view) >> >> The domain is up and working >> >> ID:f5d2f7c6-093f-46d6-a844-224d92db5ef9 >> Size:10238 GiB >> Available:2491 GiB >> Used:7747 GiB >> Allocated:3302 GiB >> Over Allocation Ratio:37% >> Images:7 >> Path:*.*.*.*:/data/ovirt >> NFS Version:AUTO >> Warning Low Space Indicator:10% (1023 GiB) >> Critical Space Action Blocker:5 GiB >> >> But somehow the node appears to thin thinks it's an LVM >> volume? It tries to find the VGs volume group but fails... >> which is not so strange as it is an NFS volume: >> >> >> Could you provide full vdsm.log file with this flow? >> >> >> 2020-02-05 14:17:54,190+0000 WARN (monitor/f5d2f7c) >> [storage.LVM] Reloading VGs failed >> (vgs=[u'f5d2f7c6-093f-46d6-a844-224d92db5ef9'] rc=5 >> out=[] err=[' Volume group >> "f5d2f7c6-093f-46d6-a844-224d92db5ef9" not found', ' >> Cannot process volume group >> f5d2f7c6-093f-46d6-a844-224d92db5ef9']) (lvm:470) >> 2020-02-05 14:17:54,201+0000 ERROR (monitor/f5d2f7c) >> [storage.Monitor] Setting up monitor for >> f5d2f7c6-093f-46d6-a844-224d92db5ef9 failed (monitor:330) >> Traceback (most recent call last): >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 327, in _setupLoop >> self._setupMonitor() >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 349, in _setupMonitor >> self._produceDomain() >> File "/usr/lib/python2.7/site-packages/vdsm/utils.py", >> line 159, in wrapper >> value = meth(self, *a, **kw) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", >> line 367, in _produceDomain >> self.domain = sdCache.produce(self.sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 110, in produce >> domain.getRealDomain() >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 51, in getRealDomain >> return self._cache._realProduce(self._sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 134, in _realProduce >> domain = self._findDomain(sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 151, in _findDomain >> return findMethod(sdUUID) >> File >> "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", >> line 176, in _findUnfetchedDomain >> raise se.StorageDomainDoesNotExist(sdUUID) >> StorageDomainDoesNotExist: Storage domain does not exist: >> (u'f5d2f7c6-093f-46d6-a844-224d92db5ef9',) >> >> The volume is actually mounted fine on the node: >> >> On NFS server >> >> Feb 5 15:47:09 back1en rpc.mountd[4899]: authenticated >> mount request from *.*.*.*:673 for /data/ovirt (/data/ovirt) >> >> On the host >> >> mount|grep nfs >> >> *.*.*.*:/data/ovirt on >> /rhev/data-center/mnt/*.*.*.*:_data_ovirt type nfs >> (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=*.*.*.*,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=*.*.*.*) >> >> And I can see the files: >> >> ls -alrt /rhev/data-center/mnt/*.*.*.*:_data_ovirt >> total 4 >> drwxr-xr-x. 5 vdsm kvm 61 Oct 26 2016 >> 1ed0a635-67ee-4255-aad9-b70822350706 >> -rwxr-xr-x. 1 vdsm kvm 0 Feb 5 14:37 __DIRECT_IO_TEST__ >> drwxrwxrwx. 3 root root 86 Feb 5 14:37 . >> drwxr-xr-x. 5 vdsm kvm 4096 Feb 5 14:37 .. >> >> >> >> >> >> Met vriendelijke groet, With kind regards, >> >> Jorick Astrego >> * >> Netbulae Virtualization Experts * >> ------------------------------------------------------------------------ >> Tel: 053 20 30 270 info(a)netbulae.eu >> <mailto:info@netbulae.eu> Staalsteden 4-3A KvK 08198180 >> Fax: 053 20 30 271 www.netbulae.eu <http://www.netbulae.eu> >> 7547 TA Enschede BTW NL821234584B01 >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email to users-leave(a)ovirt.org >> <mailto:users-leave@ovirt.org> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFTO5WBLVLGTV… >> > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego > * > Netbulae Virtualization Experts * > ------------------------------------------------------------------------ > Tel: 053 20 30 270 info(a)netbulae.eu <mailto:info@netbulae.eu> > Staalsteden 4-3A KvK 08198180 > Fax: 053 20 30 271 www.netbulae.eu <http://www.netbulae.eu> 7547 > TA Enschede BTW NL821234584B01 > > > ------------------------------------------------------------------------ > Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

2 4

Installing hosts w/o node installer
by Christian Reiss 08 Feb '20

08 Feb '20

Hey folks, quick question: If I would like to use specific versions (contained within the host) and craft myself a specific environment for the hosts am I correct to assume that only installing the ovirt repo and a gluster version of my choice (cough, 7.0) would suffice? Then adding the host via an engine (and taking the ususal steps as you would for an ovirt node: ssh keys et all)? To my understanding the rollout is done via ansible so packages will be installed if not present? The installation is pretty vague on this point (https://www.ovirt.org/download/) 1. Enable the Base, Optional, and Extra repositories 2. Install Cockpit and the cockpit-ovirt-dashboard plugin: 3. Enable Cockpit 4. Open the firewall 5. - 9. Deploy using a hosted engine. So, by using a remote engine (aka, like an additional host): 1. Enable the Base, Optional, and Extra repositories the end? I would use CentOS 7 as a base which I am very familiar with. I would also setup Gluster by hand so "Only" the virtualization part needs to be done. This would, among other things, grant me perfect host recovery options for a 1-host disaster case. We are looking at a base CentOS7 install without any deep modifications (except for some packages etc). Enjoy your weekend, all! :-) -Christian. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon christian(a)reiss.nrw \ / Campaign X against HTML XMPP chris(a)alpha-labs.net / \ in eMails WEB christian-reiss.de, reiss.nrw GPG Retrieval http://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

1 0

Re: Win Server 2k19 and BlueIris
by Robert Webb 08 Feb '20

08 Feb '20

FYI This also fixed the previous issues I was having with 2k19 servers that I was trying to migrate the disk image from Proxmox that was throwing the BSOD of KMODE EXCEPTION. From: Robert Webb <rwebb(a)ropeguru.com> Sent: Saturday, February 8, 2020 11:30 AM To: users <users(a)ovirt.org> Subject: [ovirt-users] Re: Win Server 2k19 and BlueIris Update: So after some digging, it seems this has been reported as an issue many times. As a workaround, I added the an entry to the kvm.conf in modprobe.d directory of ignore_msrs=1 and that allowed Blue Iris to boot. Would be nice to have an actual fix for this instead of a workaround. Would really like to know why kvm is thing that ia32_debugctl is not a valid cpu option. From: Robert Webb Sent: Saturday, February 8, 2020 10:33 AM To: users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: Win Server 2k19 and BlueIris So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?

1 0

Re: Win Server 2k19 and BlueIris
by Robert Webb 08 Feb '20

08 Feb '20

Update: So after some digging, it seems this has been reported as an issue many times. As a workaround, I added the an entry to the kvm.conf in modprobe.d directory of ignore_msrs=1 and that allowed Blue Iris to boot. Would be nice to have an actual fix for this instead of a workaround. Would really like to know why kvm is thing that ia32_debugctl is not a valid cpu option. From: Robert Webb Sent: Saturday, February 8, 2020 10:33 AM To: users <users(a)ovirt.org> Subject: Win Server 2k19 and BlueIris So I have been running Windows Server 2019 on Proxmox VE with Blue Iris NVR. Tried to migrate the qcow disk over to oVirt, and like other Win2k19 servers, they all give a BSOD with a KMODE error. Last night I installed 2k19 from scratch, installed the latest drivers I could find, oVirt-toolsSetup-4.3-3.el7, and proceeded to load up Blue Iris. As soon as I go to start Blue Iris, the VM hangs, then gives a BSOD with SYSTEM SERVICE EXCEPTION. Looking at the debug log on the ovirt node the VM is running, there one entry that gets created on each crash with, "kvm [4723]: vcpu1 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop". Running on oVirt node 4.3.8, cluster cpu is Intel Westmere IBRS SSBD Family, pc-i440fx-rhel7.6.0, and the physical cpu is 24x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz. Any ideas?

1 0