- Users - oVirt List Archives

Re: Stale hosted engine node information harmful ?
by Strahil 02 May '19

02 May '19

In a Red Hat Solution , it is recommended to restart ovirt-ha-agent & ovirt-ha-broker. I usually set the global maintenance and wait 20s-30s . Then I just stop on all nodes ovirt-ha-agent.service & ovirt-ha-broker.service . Once everywhere is stopped, start the 2 services on all nodes and wait 4-5min. Last verify the status from each host, before removing global maintenance. Best Regards, Strahil NikolovOn May 2, 2019 12:30, Andreas Elvers <andreas.elvers+ovirtforum(a)solutions.work> wrote: > > I have 5 nodes (node01 to node05). Originally all those nodes were part of our default datacenter/cluster with a NFS storage domain for vmdisk, engine and iso-images. All five nodes were engine HA nodes. > Later node01, node02 and node03 were re-installed to have engine HA removed. Then those nodes were removed from the default cluster. Eventually node01,02 and 03 were completely re-installed to host our new Ceph/Gluster based datecenter. The engine is still running on the old default Datacenter. Now I wish to move it over to our ceph/gluster datacenter. > > when I look at the current output of "hosted-engine --vm-status" I see: > > --== Host node01.infra.solutions.work (id: 1) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node01.infra.solutions.work > Host ID : 1 > Engine status : unknown stale-data > Score : 0 > stopped : True > Local maintenance : False > crc32 : e437bff4 > local_conf_timestamp : 155627 > Host timestamp : 155877 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=155877 (Fri Aug 3 13:09:19 2018) > host-id=1 > score=0 > vm_conf_refresh_time=155627 (Fri Aug 3 13:05:08 2018) > conf_on_shared_storage=True > maintenance=False > state=AgentStopped > stopped=True > > > --== Host node02.infra.solutions.work (id: 2) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node02.infra.solutions.work > Host ID : 2 > Engine status : unknown stale-data > Score : 0 > stopped : True > Local maintenance : False > crc32 : 11185b04 > local_conf_timestamp : 154757 > Host timestamp : 154856 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=154856 (Fri Aug 3 13:22:19 2018) > host-id=2 > score=0 > vm_conf_refresh_time=154757 (Fri Aug 3 13:20:40 2018) > conf_on_shared_storage=True > maintenance=False > state=AgentStopped > stopped=True > > > --== Host node03.infra.solutions.work (id: 3) status ==-- > > conf_on_shared_storage : True > Status up-to-date : False > Hostname : node03.infra.solutions.work > Host ID : 3 > Engine status : unknown stale-data > Score : 0 > stopped : False > Local maintenance : True > crc32 : 9595bed9 > local_conf_timestamp : 14363 > Host timestamp : 14362 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=14362 (Thu Aug 2 18:03:25 2018) > host-id=3 > score=0 > vm_conf_refresh_time=14363 (Thu Aug 2 18:03:25 2018) > conf_on_shared_storage=True > maintenance=True > state=LocalMaintenance > stopped=False > > > --== Host node04.infra.solutions.work (id: 4) status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : node04.infra.solutions.work > Host ID : 4 > Engine status : {"health": "good", "vm": "up", "detail": "Up"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 245854b1 > local_conf_timestamp : 317498 > Host timestamp : 317498 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=317498 (Thu May 2 09:44:47 2019) > host-id=4 > score=3400 > vm_conf_refresh_time=317498 (Thu May 2 09:44:47 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineUp > stopped=False > > > --== Host node05.infra.solutions.work (id: 5) status ==-- > > conf_on_shared_storage : True > Status up-to-date : True > Hostname : node05.infra.solutions.work > Host ID : 5 > Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} > Score : 3400 > stopped : False > Local maintenance : False > crc32 : 0711afa0 > local_conf_timestamp : 318044 > Host timestamp : 318044 > Extra metadata (valid at timestamp): > metadata_parse_version=1 > metadata_feature_version=1 > timestamp=318044 (Thu May 2 09:44:45 2019) > host-id=5 > score=3400 > vm_conf_refresh_time=318044 (Thu May 2 09:44:45 2019) > conf_on_shared_storage=True > maintenance=False > state=EngineDown > stopped=False > > > The old node01, node02 and node03 are still present. > > The new incarnations of node01, node02 and node03 will be the destination the the deployment of the new home of our engine to which I wish to restore the backup to. But I'm not sure, if (and how) the old date should be removed first. > _______________________________________________ > 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/WF5BNCWZHS2ZF…

2 1

Re: All hosts non-operational after upgrading from 4.2 to 4.3
by Strahil 02 May '19

02 May '19

Are you able to access your iSCSI via the /rhev/data-center/mnt... mount point ? Best Regards, Strahil NikolovOn Apr 5, 2019 19:04, John Florian <jflorian(a)doubledog.org> wrote: > > I am in a severe pinch here. A while back I upgraded from 4.2.8 to 4.3.3 and only had one step remaining and that was to set the cluster compat level to 4.3 (from 4.2). When I tried this it gave the usual warning that each VM would have to be rebooted to complete, but then I got my first unusual piece when it then told me next that this could not be completed until each host was in maintenance mode. Quirky I thought, but I stopped all VMs and put both hosts into maintenance mode. I then set the cluster to 4.3. Things didn't want to become active again and I eventually noticed that I was being told the DC needed to be 4.3 as well. Don't remember that from before, but oh well that was easy. > > However, the DC and SD remains down. The hosts are non-op. I've powered everything off and started fresh but still wind up in the same state. Hosts will look like their active for a bit (green triangle) but then go non-op after about a minute. It appears that my iSCSI sessions are active/logged in. The one glaring thing I see in the logs is this in vdsm.log: > > 2019-04-05 12:03:30,225-0400 ERROR (monitor/07bb1bf) [storage.Monitor] Setting up monitor for 07bb1bf8-3b3e-4dc0-bc43-375b09e06683 failed (monitor:329) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 326, in _setupLoop > self._setupMonitor() > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 348, in _setupMonitor > self._produceDomain() > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 158, in wrapper > value = meth(self, *a, **kw) > File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 366, 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'07bb1bf8-3b3e-4dc0-bc43-375b09e06683',) > > How do I proceed to get back operational?

2 1

Re: Fwd: [Gluster-users] Announcing Gluster release 5.5
by Strahil 02 May '19

02 May '19

Hi Darrel, Will it fix the cluster brick sudden death issue ? Best Regards, Strahil NikolovOn Mar 21, 2019 21:56, Darrell Budic <budic(a)onholyground.com> wrote: > > This release of Gluster 5.5 appears to fix the gluster 3.12->5.3 migration problems many ovirt users have encountered. > > I’ll try and test it out this weekend and report back. If anyone else gets a chance to check it out, let us know how it goes! > > -Darrell > >> Begin forwarded message: >> >> From: Shyam Ranganathan <srangana(a)redhat.com> >> Subject: [Gluster-users] Announcing Gluster release 5.5 >> Date: March 21, 2019 at 6:06:33 AM CDT >> To: announce(a)gluster.org, gluster-users Discussion List <gluster-users(a)gluster.org> >> Cc: GlusterFS Maintainers <maintainers(a)gluster.org> >> >> The Gluster community is pleased to announce the release of Gluster >> 5.5 (packages available at [1]). >> >> Release notes for the release can be found at [3]. >> >> Major changes, features and limitations addressed in this release: >> >> - Release 5.4 introduced an incompatible change that prevented rolling >> upgrades, and hence was never announced to the lists. As a result we are >> jumping a release version and going to 5.5 from 5.3, that does not have >> the problem. >> >> Thanks, >> Gluster community >> >> [1] Packages for 5.5: >> https://download.gluster.org/pub/gluster/glusterfs/5/5.5/ >> >> [2] Release notes for 5.5: >> https://docs.gluster.org/en/latest/release-notes/5.5/ >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users(a)gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users > >

9 18

oVirt and Ceph iSCSI: separating discovery auth / target auth ?
by Matthias Leopold 01 May '19

01 May '19

Hi, I'm trying to use the Ceph iSCSI gateway with oVirt. According to my tests with oVirt 4.3.2 * you cannot separate iSCSI discovery auth and target auth * you cannot use an iSCSI gateway that has no discovery auth, but uses CHAP for targets This means I'm forced to use the same credentials for discovery auth and target auth. In Ceph iSCSI gateway I can have multiple targets with use different credentials, but I can define discovery auth only once for the whole gateway (or have no discovery auth). If all of this is correct and I want to use the Ceph iSCSI gateway with oVirt * I have to use discovery auth * the credentials for discovery auth will give every other Ceph iSCSI gateway user access to the oVirt target This is not a desirable situation. Did I understand anything wrong? Are there other ways to solve this? thx matthias

1 2

Upgrade 4.1.8 to 4.3.3
by christopher.jorgensen＠gmail.com 01 May '19

01 May '19

I am a little behind in updates but I couldn't find any specific instructions going from 4.1.8 to 4.3.3. From what I read so far, the process for upgrading should be as follows: 4.1.8 --> 4.1.9 https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_t… 4.1.9 --> 4.2.0 https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_t… 4.2.0 --> 4.2.8 (use instructions above to upgrade to the latest 4.2 before going to 4.3) 4.2.8 --> 4.3.3 Is this correct or should I add / remove upgrade versions?

3 2

integration with openstack nove-compute
by ehsan.sabooni＠gmail.com 01 May '19

01 May '19

hello dear all, is it possible to make a compute-nove VM inside oVirt, using which, to be able to create VM instances inside oVirt through openstack horizon? to make it simple, is it possible to have oVirt has the hypervisor for openstack, while having a nova-compute node as a VM inside ovirt? as a hint, the same thing is possible via vsphere vCenter, if we install vCenter driver on the nova-compute node. thank you for your support!

2 1

silent install failing in 4.3.3.5-1 due to question on fqdn of host
by Brian Kircher 01 May '19

01 May '19

Anyone happen to know if I can get the following into an answer file for a true silent deployment? It's asking to confirm or change from the fqdn of the host doing the HE install. Default is fine, but I have to connect in to the screen to answer this before it will continue. Default changed to generic in below log. QUESTION/1/OVESETUP_NETWORK_FQDN_first_HE 019-04-30 18:56:38,802-0500 DEBUG otopi.context context.dumpEnvironment:745 ENVIRONMENT DUMP - END 2019-04-30 18:56:38,804-0500 DEBUG otopi.context context._executeMethod:127 Stage validation METHOD otopi.plugins.gr_he_common.network.bridge.Plugin._validate_hostname_first_host 2019-04-30 18:56:38,806-0500 DEBUG otopi.plugins.gr_he_common.network.bridge dialog.queryEnvKey:90 queryEnvKey called for key OVEHOSTED_NETWORK/host_name 2019-04-30 18:56:38,806-0500 DEBUG otopi.plugins.otopi.dialog.human human.queryString:159 query OVESETUP_NETWORK_FQDN_first_HE 2019-04-30 18:56:38,807-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Please provide the hostname of this host on the management network [host01.domain.com] Version 4.3.3.5-1.el7 Thanks, Brian ________________________________ This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.

1 0

ovirt 4.3.3 Disk for New VM is always Preallocated
by Strahil Nikolov 01 May '19

01 May '19

Hi All, I have stumbled upon a potential bug in UI. Can someone test it , in order to reproduce it ? How to reproduce:1. Create a VM2. Within the new VM wizard - Create a disk and select Thin Provision.3. Create the VM and wait for the disk to be completed.4. Check the disk within UI - Allocation Policy is set to "Preallocation" Best Regards,Strahil Nikolov

3 4

Update storage lease via python sdk
by klaasdemter＠gmail.com 30 Apr '19

30 Apr '19

Hi, I'm trying to update a storage lease via python sdk but I can’t seem to figure out how to wait for the storage lease configuration to finish. The vm status does not show “configuration in progress” just “up” and the event is created as soon as I issue the update, not when its done. Can someone give me a hint or point me to an example? https://github.com/Klaas-/ovirt-engine-sdk/blob/4094d3a2d4b011d4926e58374dd… Greetings Klaas

1 1

Re: 4.3.x upgrade and issues with OVN
by Weber, Charles (NIH/NIA/IRP) [E] 30 Apr '19

30 Apr '19

Complete shutdown of 4.3.3 cluster, change cluster from 4.2 to 4.3 compatibility and upgrade of all hosts to current 4.3.3 with patches has seemingly fixed everything.

1 0

Re: Please Help, Ovirt Node Hosted Engine Deployment Problems 4.3.2
by Strahil 30 Apr '19

30 Apr '19

> Each data has to be written on the host itself and on the two remote ones so you are going to have 1000 mbps / 2 (external replicas ) / 8 (bit/bytes) = a max of 62.5 MB/s sustained throughput shared between all the VMs and this ignoring all the overheads. > In practice it will be much less ending in a barely usable environment. I am currently in this type of setup (replica 2 arbiter 1 on 1 gbit/s both storage and oVirt connectivity) and the maximum write (sequential) speed I can reach is aprox 89 MB/s. I guess with replica 3 the maximum will be as Simone stated. My maximum read speed is aprox 500 MB/s despite that local NVMe is capable of 1.3 GB/s and I guess FUSE is not using the local brick no matter I have set it up with cluster.use-local (or whatever it was called). If possible , get a 10 gbit/s connectivity or multiple gbit interfaces ( as I'm planing to do in the nearest future). Best Regards, Strahil Nikolov

1 0

HA VM not work when VM OS cannot run normally
by du_hongyu＠yeah.net 30 Apr '19

30 Apr '19

HI， I create a HA VM in ovirt follaw this article https://ovirt.org/develop/ha-vms.html#highly-available-vms-and-io-errors when my vm‘s OS can not run, but ovirt consider this vm is up, so is this a bug for HA VM? can you give me some advise? Regards Hongyu Du

2 4

Ovirt Nested in VMWare (Working approach)
by RabidCicada 30 Apr '19

30 Apr '19

I worked through this previously and posted in IRC yesterday about working around running ovirt nested under VMWare. I figured i'd post it to the mail group so that it would be available in it's entirety here for future reference: The following gists explain the 3 major adjustments that have to be made currently to get nested virt under vmware working: https://gist.github.com/RabidCicada/993349b3a7eaf35637122f0122fdedb3 https://gist.github.com/RabidCicada/bc01eb0b13195faa26520c0fb666ec34 https://gist.github.com/RabidCicada/37ff6f1ed2afd8dd4edefac735536c69 https://gist.github.com/RabidCicada/40655db1582ca5d07c9bbf2c429cdd01 Hopefully it can save others the huge amount of time it took me to figure it all out. Specifically it's a problem with the --machine type at 3 major parts of the vm creation for the hosted-engine. 1) You have to fix the virt-install to use --machine pc-i440fx-rhel7.2.0 2) You have to fix the guestfish spinup of the partially configured vm to use --machine pc-i440fx-rhel7.2.0, where they edit the nic config among other things 3) You have to tell vdsm on the node to use --machine pc-i440fx-rhel7.2.0 I don't know the underlying reason why a --machine type > pc-i440fx-rhel7.2.0 breaks the system but it ends up resulting in a bios freeze. Again, Hope this helps someone. Suggested only to use for a test/dev system.

2 1

[QA][Feedback Needed] RDO Stein integration testing
by Sandro Bonazzola 30 Apr '19

30 Apr '19

Hi, RDO Stein has been released a few days ago: https://blogs.rdoproject.org/2019/04/rdo-stein-released/ I opened test bug for the providers oVirt is consuming from OpenStack: Neutron, Glance and Cinder. Has anyone capacity for testing this (not on production systems!) and give feedback? Bug 1704350 <https://bugzilla.redhat.com/show_bug.cgi?id=1704350> - Test neutron integration with RDO Stein Bug 1704349 <https://bugzilla.redhat.com/show_bug.cgi?id=1704349> - Test glance integration with RDO Stein Bug 1704352 <https://bugzilla.redhat.com/show_bug.cgi?id=1704352> - Test Cinder integration with RDO Stein Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

ovirt 4.3.3 cannot create VM in non-default cluster
by Strahil Nikolov 29 Apr '19

29 Apr '19

Hi All, I'm having an issue to create a VM in my second cluster called "Intel" which consists of only 1 Host -> ovirt3 which plays the role of a gluster arbiter in my hyperconverged setup. When I try to create the VM (via UI) I receive: "Cannot add VM. CPU Profile doesn't match provided Cluster." When I try to select the host where I can put the VM , I see only ovirt1 or ovirt2 which are part of the 'Default' Cluster . Do we have an opened bug for that ? Note: A workaround is to create the VM in the Default cluster and later edit it to match the needed Cluster. Best Regards,Strahil Nikolov

1 2

4.3.3 restore fails
by magnus＠boden.one 29 Apr '19

29 Apr '19

Hello, I had a ovirt-engine-4.3.0 that I am migrating to a new machine. I have done a backup of that machine but the restore fails on the new machine. Fresh install of centos and the 4.3.3 ovirt-engine. [root@oengine ~]# engine-backup --mode=restore --file=ovirt-engine-backup-20190426214711.backup --log=02.17.log --provision-db --provision-dwh-db --restore-permissions Start of engine-backup with mode 'restore' scope: all archive file: ovirt-engine-backup-20190426214711.backup log file: 02.17.log Preparing to restore: - Unpacking file 'ovirt-engine-backup-20190426214711.backup' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' - user 'ovirt_engine_history', database 'ovirt_engine_history' Restoring: - Engine database 'engine' FATAL: Errors while restoring database engine [root@oengine ~]# cat 02.17.log 2019-04-27 02:17:55 32343: Start of engine-backup mode restore scope all file ovirt-engine-backup-20190426214711.backup 2019-04-27 02:17:55 32343: OUTPUT: Start of engine-backup with mode 'restore' 2019-04-27 02:17:55 32343: OUTPUT: scope: all 2019-04-27 02:17:55 32343: OUTPUT: archive file: ovirt-engine-backup-20190426214711.backup 2019-04-27 02:17:55 32343: OUTPUT: log file: 02.17.log 2019-04-27 02:17:55 32343: Setting scl env for rh-postgresql10 2019-04-27 02:17:55 32343: OUTPUT: Preparing to restore: 2019-04-27 02:17:55 32343: OUTPUT: - Unpacking file 'ovirt-engine-backup-20190426214711.backup' 2019-04-27 02:17:55 32343: Opening tarball ovirt-engine-backup-20190426214711.backup to /tmp/engine-backup.NVv4Bxjb2k 2019-04-27 02:17:55 32343: Verifying hash 2019-04-27 02:17:55 32343: Verifying version 2019-04-27 02:17:55 32343: Reading config 2019-04-27 02:17:55 32343: OUTPUT: Restoring: 2019-04-27 02:17:55 32343: OUTPUT: - Files 2019-04-27 02:17:55 32343: Restoring files 2019-04-27 02:17:56 32343: Reloading configuration 2019-04-27 02:17:56 32343: OUTPUT: Provisioning PostgreSQL users/databases: 2019-04-27 02:17:56 32343: provisionDB: user engine host localhost port 5432 database engine secured False secured_host_validation False 2019-04-27 02:17:56 32343: OUTPUT: - user 'engine', database 'engine' [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf', '/tmp/engine-backup.NVv4Bxjb2k/pg-provision-answer-file'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20190427021756-hxbrea.log Version: otopi-1.8.1 (otopi-1.8.1-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Creating PostgreSQL 'engine' database [ INFO ] Configuring PostgreSQL [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20190427021756-hxbrea.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of provisiondb completed successfully 2019-04-27 02:17:58 32343: provisionDB: user ovirt_engine_history host localhost port 5432 database ovirt_engine_history secured False secured_host_validation False 2019-04-27 02:17:58 32343: OUTPUT: - user 'ovirt_engine_history', database 'ovirt_engine_history' [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf', '/tmp/engine-backup.NVv4Bxjb2k/pg-provision-answer-file'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20190427021758-s2av1b.log Version: otopi-1.8.1 (otopi-1.8.1-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Creating PostgreSQL 'ovirt_engine_history' database [ INFO ] Configuring PostgreSQL [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20190427021758-s2av1b.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of provisiondb completed successfully 2019-04-27 02:18:00 32343: OUTPUT: Restoring: 2019-04-27 02:18:00 32343: Generating pgpass 2019-04-27 02:18:00 32343: Verifying connection 2019-04-27 02:18:00 32343: pg_cmd running: psql -w -U engine -h localhost -p 5432 engine -c select 1 ?column? ---------- 1 (1 row) 2019-04-27 02:18:00 32343: pg_cmd running: psql -w -U engine -h localhost -p 5432 engine -t -c show lc_messages 2019-04-27 02:18:00 32343: pg_cmd running: pg_dump -w -U engine -h localhost -p 5432 engine -s 2019-04-27 02:18:01 32343: pg_cmd running: psql -w -U ovirt_engine_history -h localhost -p 5432 ovirt_engine_history -c select 1 ?column? ---------- 1 (1 row) 2019-04-27 02:18:01 32343: pg_cmd running: psql -w -U ovirt_engine_history -h localhost -p 5432 ovirt_engine_history -t -c show lc_messages 2019-04-27 02:18:01 32343: pg_cmd running: pg_dump -w -U ovirt_engine_history -h localhost -p 5432 ovirt_engine_history -s 2019-04-27 02:18:01 32343: OUTPUT: - Engine database 'engine' 2019-04-27 02:18:01 32343: Restoring engine database backup at /tmp/engine-backup.NVv4Bxjb2k/db/engine_backup.db 2019-04-27 02:18:01 32343: restoreDB: backupfile /tmp/engine-backup.NVv4Bxjb2k/db/engine_backup.db user engine host localhost port 5432 database engine orig_user compressor format custom jobsnum 2 2019-04-27 02:18:01 32343: pg_cmd running: pg_restore -w -U engine -h localhost -p 5432 -d engine -j 2 /tmp/engine-backup.NVv4Bxjb2k/db/engine_backup.db pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 7624; 0 0 COMMENT EXTENSION plpgsql pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of extension plpgsql Command was: COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural language'; pg_restore: [archiver (db)] Error from TOC entry 7625; 0 0 COMMENT EXTENSION "uuid-ossp" pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of extension uuid-ossp Command was: COMMENT ON EXTENSION "uuid-ossp" IS 'generate universally unique identifiers (UUIDs)'; pg_restore: [archiver (db)] Error from TOC entry 6400; 2606 18298 CONSTRAINT external_variable pk_external_variable engine pg_restore: [archiver (db)] could not execute query: ERROR: could not create unique index "pk_external_variable" DETAIL: Key (var_name)=(fence-kdump-listener-heartbeat) is duplicated. Command was: ALTER TABLE ONLY public.external_variable ADD CONSTRAINT pk_external_variable PRIMARY KEY (var_name); WARNING: errors ignored on restore: 4 2019-04-27 02:18:43 32343: Non-ignored-errors in pg_restore log: pg_restore: [archiver (db)] could not execute query: ERROR: could not create unique index "pk_external_variable" 2019-04-27 02:18:43 32343: FATAL: Errors while restoring database engine If this is a problem while restoring a 4.3.0 backup to a 4.3.3 engine is it possible to install the 4.3.0 version? Following the installation part of the release notes of 4.3.0 will result in 4.3.3 being installed. Best Regards Magnus

2 2

[Users] importing from kvm into ovirt
by Jonathan Horne 29 Apr '19

29 Apr '19

--_000_9BE6F493F83A594DA60C45E6A09DC5AC016BA694AUSP01DAG0201co_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I need to import a kvm virtual machine from a standalone kvm into my ovirt = cluster. Standalone is using local storage, and my ovirt cluster is using = iscsi. Can i please have some advice on whats the best way to get this sys= tem into ovirt? Right now i see it as copying the .img file to somewhere=85 but i have no i= dea where to start. I found this directory on one of my ovirt nodes: /rhev/data-center/mnt/blockSD/fe633237-14b2-4f8b-aedd-bbf753bcafaf/master/v= ms But inside is just directories that appear to have uuid-type of names, and = i can't tell what belongs to which vm. Any advice would be greatly appreciated. Thanks, jonathan ________________________________ This is a PRIVATE message. If you are not the intended recipient, please de= lete without copying and kindly advise us by e-mail of the mistake in deliv= ery. NOTE: Regardless of content, this e-mail shall not operate to bind SKO= POS to any order or other contract unless pursuant to explicit written agre= ement or government initiative expressly permitting the use of e-mail for s= uch purpose. --_000_9BE6F493F83A594DA60C45E6A09DC5AC016BA694AUSP01DAG0201co_ Content-Type: text/html; charset="Windows-1252" Content-ID: <41FAB2B157C43549B6577A3495BA255C(a)collaborationhost.net> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font= -family:Calibri,sans-serif"> <div> <div> <div>I need to import a kvm virtual machine from a standalone kvm into my o= virt cluster.  Standalone is using local storage, and my ovirt cluster= is using iscsi.  Can i please have some advice on whats the best way = to get this system into ovirt?</div> </div> </div> <div><br> </div> <div>Right now i see it as copying the .img file to somewhere=85 but i have= no idea where to start.  I found this directory on one of my ovirt no= des:</div> <div><br> </div> <div>/rhev/data-center/mnt/blockSD/fe633237-14b2-4f8b-aedd-bbf753bcafaf/mas= ter/vms</div> <div><br> </div> <div>But inside is just directories that appear to have uuid-type of names,= and i can't tell what belongs to which vm.</div> <div><br> </div> <div>Any advice would be greatly appreciated.</div> <div><br> </div> <div>Thanks,</div> <div>jonathan</div> <br> <hr> <font color=3D"Gray" face=3D"Arial" size=3D"1">This is a PRIVATE message. I= f you are not the intended recipient, please delete without copying and kin= dly advise us by e-mail of the mistake in delivery. NOTE: Regardless of con= tent, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit wri= tten agreement or government initiative expressly permitting the use of e-m= ail for such purpose.</font> </body> </html> --_000_9BE6F493F83A594DA60C45E6A09DC5AC016BA694AUSP01DAG0201co_--

3 2

Upgraded ovirt-4.2 to ovirt-4.3 and VM run fails
by Gobinda Das 29 Apr '19

29 Apr '19

Hi, I have upgraded ovirt-4.2 to ovirt-4.3 and after upgrade while starting vms giving me error: Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host *node1.test.com <http://node1.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. The host *node2.test.com <http://node2.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. The host *node3.test.com <http://node3.test.com>* did not satisfy internal filter ClusterInMaintenance because the cluster is in maintenance and only highly available VMs are allowed to start. Eventhough cluster is not in maintenance mode. This setup is using gluster6 for storage. -- Thanks, Gobinda

2 1

HA VMs fail to start on host failure
by tezmobile＠googlemail.com 29 Apr '19

29 Apr '19

In a host failure situation, we see that oVirt tries to restart the VMs on other hosts in the cluster but this (more often than not) fails due to kvm being unable to acquire a write lock on the qcow2 image. We see ovirt attempt to restart the VMs several times, each time on different hosts but with the same outcome after which it gives up trying. After this we must log into the oVirt web interface and start the VM manually, which works fine (by this time we assume enough time has passed for the lock to clear itself). This behaviour is experienced with Centos 7.6, Libvirt 4.5.0-10, vdsm 4.30.13-1 Log excerpt from hosted engine: 2019-04-24 17:05:26,653+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [] VM 'ef7e04f0-764a-4cfe-96bf-c0862f1f5b83'(vm-21.example.local) moved from 'WaitForLaunch' --> 'Down' 2019-04-24 17:05:26,710+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-82) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm-21.example.local is down with error. Exit message: internal error: process exited while connecting to monitor: 2019-04-24T16:04:48.049352Z qemu-kvm: -drive file=/rhev/data-center/mnt/192.168.111.111:_/21a1390b-b73b-46b1-85b9-2bbf9bba5308/images/c9d96ab6-cb0b-4fba-9b07-096ff750c7f7/16da3660-1afe-40a3-b868-3a74e74bab2f,format=qcow2,if=none,id=drive-ua-c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,serial=c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,werror=stop,rerror=stop,cache=none,aio=threads: 'serial' is deprecated, please use the corresponding option of '-device' instead 2019-04-24T16:04:48.079989Z qemu-kvm: -drive file=/rhev/data-center/mnt/192.168.111.111:_/21a1390b-b73b-46b1-85b9-2bbf9bba5308/images/c9d96ab6-cb0b-4fba-9b07-096ff750c7f7/16da3660-1afe-40a3-b868-3a74e74bab2f,format=qcow2,if=none,id=drive-ua-c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,serial=c9d96ab6-cb0b-4fba-9b07-096ff750c7f7,werror=stop,rerror=stop,cache=none,aio=threads: Failed to get "write" lock So my question is, how can I either force oVirt to continue to try restarting the VM or delay the initial VM restart for enough time to allow locks to clear?

1 0

Template Disk Corruption
by Alex McWhirter 29 Apr '19

29 Apr '19

1. Create server template from server VM (so it's a full copy of the disk) 2. From template create a VM, override server to desktop, so that it become a qcow2 overlay to the template raw disk. 3. Boot VM 4. Shutdown VM 5. Delete VM Template disk is now corrupt, any new machines made from it will not boot. I can't see why this happens as the desktop optimized VM should have just been an overlay qcow file...

2 5

oVirt 4.3.2 Error: genev_sys_6081 is not present in the system
by Dee Slaw 29 Apr '19

29 Apr '19

Hello, I've installed oVirt 4.3.2 and the problem is that it log messages: VDSM ovirt-04 command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '[Errno 19] genev_sys_6081 is not present in the system'} in Open Virtualization Manager. It also keeps on logging in /var/log/messages: Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9861] device (genev_sys_6081): carrier: link connected Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9864] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34160) Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9866] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 NetworkManager[8725]: <info> [1553244663.9906] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:03 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0038] device (genev_sys_6081): carrier: link connected Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0042] manager: (genev_sys_6081): new Generic device (/org/freedesktop/NetworkManager/Devices/34161) Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0044] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 NetworkManager[8725]: <info> [1553244664.0082] device (genev_sys_6081): enslaved to non-master-type device ovs-system; ignoring Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 left promiscuous mode Mar 22 11:51:04 ovirt-04 kernel: device genev_sys_6081 entered promiscuous mode Also I can see the following in /var/log/openvswitch: 2019-03-22T08:53:12.413Z|131047|bridge|WARN|could not add network device ovn-034a1c-0 to ofproto (File exists) 2019-03-22T08:53:12.431Z|131048|tunnel|WARN|ovn-a21088-0: attempting to add tunnel port with same config as port 'ovn-0836d7-0' (::->192.168.10.24, key=flow, legacy_l2, dp port=2) 2019-03-22T08:53:12.466Z|131055|connmgr|WARN|accept failed (Too many open files) 2019-03-22T08:53:12.466Z|131056|unixctl|WARN|punix:/var/run/openvswitch/ovs-vswitchd.9103.ctl: accept failed: Too many open files In ovsdb-server.log: 2019-03-22T03:24:12.583Z|05792|jsonrpc|WARN|unix#28684: receive error: Connection reset by peer 2019-03-22T03:24:12.583Z|05793|reconnect|WARN|unix#28684: connection dropped (Connection reset by peer) How to fix this issue with geneve tunnels?

4 11

Re: All Windows vms report "Actual timezone in guest doesn't match configuration"
by Strahil 29 Apr '19

29 Apr '19

What happens when you restart ovirt agent services ? Best Regards, Strqhil NikolovOn Apr 26, 2019 03:06, michael(a)wanderingmad.com wrote: > > All of my windows VMs have a yellow exclamation point with the timezone error. The configuration in ovirt says eastern time, and I've tried changing the VM from eastern time to US eastern time, and error does not go away. This is with the latest ovirt guest tools for windows. > _______________________________________________ > 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/XL6XHN5KIEM7G…

2 1

Fetching DiskAttachmentService in ovirt-python-sdk-4
by Kaustav Majumder 29 Apr '19

29 Apr '19

Hi, I am trying to detach and delete disk from my vm. I found this service in the docs DiskAttachmentService http://ovirt.github.io/ovirt-engine-sdk/master/services.m.html#ovirtsdk4.se… I am not able to fetch this service. Below if the snippet of code I am trying. https://pastebin.com/UUu0Pfc8 Error--> File "./pre_setup/delete_vm_disk.py", line 19, in remove_attached_vm_disk attachment.remove(detach_only=False) AttributeError: 'DiskAttachment' object has no attribute 'remove' -- Thanks, Kaustav Majumder

3 4

One Way Flights Deals - Tripiflights
by marketings＠tripiflights.com 29 Apr '19

29 Apr '19

searching for one way flights deals . tripiflights is the perfect place for you. Here you will get best options at reasonable rates - https://go2article.com/article/one-way-flights-deals-tripiflights/

1 0

unable to upload disk images after upgrade to 4.3.3 -- ticket failures
by Edward Berger 29 Apr '19

29 Apr '19

Previously I had issues with the upgrades to 4.3.3 failing because of "stale" image transfer data, so I removed it from the database using the info given here on the mailing list and was able to complete the oVirt node and engine upgrades. Now I have a new problem. I can't upload a disk image anymore, which used to work. "test connection" returns success. In the dashboard Storage/Disks view, it starts and then stops with "paused by system" I tried pointing it at another node, same problem. I tried restarting services ovirt-imageio-proxy on engine and ovirt-imageio-daemon on the node, same failure. in the dashboard events when trying to upload disk I get this error Transfer was stopped by system. Reason: failed to add image ticket to ovirt-imageio-proxy. or when trying to resume transfer "paused by system" giving it the local path again. Transfer was stopped by system. Reason: failure in transfer image ticket renewal. I'm not sure what logs I should be looking deeper into.. Here's what the database says engine=# select * from image_transfers; -[ RECORD 1 ]-------------+------------------------------------- command_id | 59dce2b1-f8ba-44dd-9df9-c6e39773a3f9 command_type | 1024 phase | 4 last_updated | 2019-04-23 12:22:25.098-04 message | Uploading from byte 0 vds_id | disk_id | 6693d5ac-d3eb-43d7-9abe-97c5197efc23 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1996488704 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 -[ RECORD 2 ]-------------+------------------------------------- command_id | 16898219-be5b-4826-8f20-3355fa47272a command_type | 1024 phase | 4 last_updated | 2019-04-23 16:15:34.591-04 message | Uploading from byte 0 vds_id | disk_id | 3b8e3053-bfe4-49d3-abd2-5452b1674400 imaged_ticket_id | proxy_uri | signed_ticket | bytes_sent | 0 bytes_total | 1998585856 type | 2 active | f daemon_uri | client_inactivity_timeout | 60 I really need the image uploading to work. Any suggestions on what to do next?

2 2