I'm testing what in object in a test env with novirt1 and novirt2 as hosts.
First reinstalled host is novirt2
For this I downloaded the 4.4.8 iso of the node:
before running the restore command for the first scratched node I
pre-installed the appliance rpm on it and I got:
I selected to pause an d I arrived here with local vm engine completing its
INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add host]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Include after_add_host
[ INFO ] You can now connect to
https://novirt2.localdomain.local:6900/ovirt-engine/ and check the status
of this host and eventually remediate it, please continue only when the
host is listed as 'up'
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create temporary lock
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Pause execution until
/tmp/ansible.4_o6a2wo_he_setup_lock is removed, delete it once ready to
But connecting t the provided
I see that only the still 4.3.10 host results up while novirt2 is not
In engine.log I see
2021-08-25 09:14:38,548+02 ERROR
(EE-ManagedThreadFactory-engine-Thread-4) [5f4541ee] Command
'HostDevListByCapsVDSCommand(HostName = novirt2.localdomain.local,
execution failed: java.net.ConnectException: Connection refused
and continuouslly this message...
I also tried to restart vdsmd on novit2 but nothing changed.
Do I have to restart the HA daemons on novirt2?
I'm trying to decommission the old master storage domain in ovirt, and
replace it with a new one. All of the VMs have been migrated off of the
old master, and everything has been running on the new storage domain
for a couple months. But when I try to put the old domain into
maintenance mode I get an error.
Old Master: vm-storage-ssd
New Domain: vm-storage-ssd2
The error is:
Failed to Reconstruct Master Domain for Data Center EDC2
As well as:
Sync Error on Master Domain between Host daccs01 and oVirt Engine.
Domain: vm-storage-ssd is marked as Master in oVirt Engine database but
not on the Storage side. Please consult with Support on how to fix this
2021-07-28 11:41:34,870-07 WARN
(EE-ManagedThreadFactory-engine-Thread-23)  Master domain version is
not in sync between DB and VDSM. Domain vm-storage-ssd
marked as master, but the version in DB: 283 and in VDSM: 280
Not stopping SPM on vds daccs01, pool id
f72ec125-69a1-4c1b-a5e1-313fcb70b6ff as there are uncleared tasks Task
'5fa9edf0-56c3-40e4-9327-47bf7764d28d', status 'finished'
After a couple minutes all the domains are marked as active again and
things continue, but vm-storage-ssd is still listed as the master
domain. Any thoughts?
This is on 184.108.40.206-1.el7 on CentOS 7.
engine=# SELECT storage_name, storage_pool_id, storage, status FROM
storage_pool_with_storage_domain ORDER BY storage_name;
storage_name | storage_pool_id
| storage | status
compute1-iscsi-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
yvUESE-yWUv-VIWL-qX90-aAq7-gK0I-EqppRL | 1
compute7-iscsi-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
8ekHdv-u0RJ-B0FO-LUUK-wDWs-iaxb-sh3W3J | 1
export-domain-storage | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
d3932528-6844-481a-bfed-542872ace9e5 | 1
iso-storage | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
f800b7a6-6a0c-4560-8476-2f294412d87d | 1
vm-storage-7200rpm | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
a0bff472-1348-4302-a5c7-f1177efa45a9 | 1
vm-storage-ssd | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
95acd9a4-a6fb-4208-80dd-1c53d6aacad0 | 1
vm-storage-ssd2 | f72ec125-69a1-4c1b-a5e1-313fcb70b6ff |
829d0600-c3f7-4dae-a749-d7f05c6a6ca4 | 1
I managed a ovirt 4.4.7 for production systems.
Last week i removed the Master storage domain (moved tamplates, vm-s well, unattached, etc), but i forgot to move isos.
Now, when i upload a new iso to a data storage domain, the system show it, but it's unbootable:
"could not read from cdrom code 0005"
We are using oVirt for several years.
And we start with Xeon v2 CPUs.
At this moment of time we got all v3 aтв we will chnage them to v4 in a month.
So i would like to change Cluster default CPU to Haswell, But got error with custom cpu on HostedEngine.
HostedEngine config is locked.
Is there a solution to chnage HostedEngine cpu type?
P.S. some problem with Cluster compability version (4.5 4.6)
I am trying to install vdsm hooks (scratchpad) specifically.
I can see that there are rpms available in
https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ but when I try to
install using yum it says it cannot find it.
Do I have to manually select the hook rpm and install it or am I missing
I have an HCI cluster running on Gluster storage. I exposed an NFS share into oVirt as a storage domain so that I could clone all of my VMs (I'm preparing to move physically to a new datacenter). I got 3-4 VMs cloned perfectly fine yesterday. But then this evening, I tried to clone a big VM, and it caused the disk to lock up. The VM went totally unresponsive, and I didn't see a way to cancel the clone. Nagios NRPE (on the client VM) was reporting server load over 65+, but I was never able to establish an SSH connection.
Eventually, I tried restarting the ovirt-engine, per https://access.redhat.com/solutions/396753. When that didn't work, I powered down the VM completely. But the disks were still locked. So I then tried to put the storage domain into maintenance mode, but that wound up putting the entire domain into a "locked" state. Finally, eventually, the disks unlocked, and I was able to power the VM back online.
From start to finish, my VM was down for about 45 minutes, including the time when NRPE was still sending data to Nagios.
What logs should I look at, and how can I troubleshoot what went wrong here, and hopefully avoid this from happening again?
Sent with ProtonMail Secure Email.
I have built a system as a template on oVirt. Specifically, Ubuntu 18.04 server.
I am noticing an issue when creating new vms from that template. I used the check box for "seal template" when creating the template.
When I create a new Ubuntu VM I am getting duplicate IP addresses for all the machines created from the template.
It seems like the checkbox doesn't fully function as intended. I would need to do further manual steps to clear up this issue.
Has anyone else noticed this behavior? Is this expected or have I missed something?
Thanks for your input!
Here the error in engine.log
2021-08-31 10:22:26,536-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Query OVA info. Run query script.
2021-08-31 10:22:29,640-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>".
2021-08-31 10:22:29,662-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message The element type "SpecParams" must be terminated by the matching end-tag "</SpecParams>".
2021-08-31 10:22:30,694-04 ERROR [org.ovirt.engine.core.utils.ovf.OvfManager] (default task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] Error parsing OVF due to Error loading ovf, message XML document structures must start and end within the same entity.
And my ansible log file
----- Original Message -----
From: Saif Abu Saleh (sabusale(a)redhat.com)
Date: 31/08/21 09:54
To: Dominique D (dominique.deschenes(a)gcgenicom.com)
Subject: Re: [ovirt-users] Import OVA problem
Hope you are doing well
In order to investigate this, we need to check the log files
Can you please try to do import again and provide the following log files after the import:
- engine.log, from location: <deployment_location>/var/log/ovirt-engine/engine.log
- ansible log file (depending on the time of the import), from location: <deployment_location>/var/log/ovirt-engine/ova
On Sun, Aug 29, 2021 at 6:08 PM Dominique D <dominique.deschenes(a)gcgenicom.com> wrote:
I have tried exporting 4 VMs (2 centos and 2 Windows) to an nfs mount (export OVA) and importing from ova and I can't see all the files.
Here are the files in the directory
-rw-------+ 1 root root 10739331584 Aug 29 10:27 linux2.ova
-rw-------+ 1 root root 1784370176 Aug 28 12:00 linuxtest.ova
-rw-------+ 1 root root 64434655232 Aug 28 13:57 vdiw10-2004v1C.ova
-rw-------+ 1 vdsm kvm 49040712192 Aug 27 17:21 vdiw10rg06.ova
The only file I see in virtual machine on source is linuxtest.ova and linux2.ova. Do you know why ?
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://email@example.com/message/3TX6YKUG56O...
On 2021-08-17 11:12, Dana Elfassy wrote:
> The execution of the task itself is fine - we're always installing this
> package because of dependencies.
> As for its failure- looks like an issue with the repositories.
> Please run $ yum repolist
> on the host and copy the output
Sorry for replying so late, was on a 2-week road-trip.
$ yum repolist
CentOS Stream 8 - AppStream
CentOS Stream 8 - BaseOS
Elasticsearch repository for 7.x
Extra Packages for Enterprise
Linux 8 - Next - x86_64
CentOS Stream 8 - Extras
Latest oVirt 4.4 Release
Ceph packages for x86_64
CentOS-8 - Gluster 8
CentOS-8 - OpsTools - collectd
Advanced Virtualization CentOS
Stream packages for x86_64
CentOS-8 - NFV OpenvSwitch
CentOS-8 Stream - oVirt 4.4
Copr repo for ovsdbapp owned by
Copr repo for gluster-ansible
owned by sac
Copr repo for EL8_collection
owned by sbonazzo
Extra Packages for Enterprise
Linux 8 - x86_64
OpenStack Train Repository
virtio-win builds roughly
matching what will be shipped in upcoming RHEL
CentOS Stream 8 - PowerTools
Then there's also this:
$ dnf update
Last metadata expiration check: 0:28:17 ago on Tue 31 Aug 2021 12:45:32
Problem 1: cannot install the best update candidate for package
- nothing provides python3-os-brick needed by
Problem 2: package ovirt-host-4.4.8-1.el8.x86_64 requires
ovirt-host-dependencies = 4.4.8-1.el8, but none of the providers can be
- cannot install the best update candidate for package
- nothing provides python3-os-brick needed by