question about engine deployment success rate
by Henning Sprang
Hello,
I've just inherited a project where we need to bring a prototype of a
small Ovirt system (single node or 3 node hyperconverged, with
glusterFS on the same machine, a bunch of different VM's ) running in
an industrial machine into serial production.
This means, we want to build a new 1 or 3 node Ovirt system each day
up until 3 times a day.
In my tests so far, the failure rate of the Ovirt engine deployment
(via the included scripts as well as the web UI) turns out to be
pretty high - it's between 40-60%, meaning until we have a running
system, we would have to try the installation and/or final engine
deployment about 2-4 times until we are successful.
So far I could not identify clear error messages that let me tell how
to fix the problem.
Before going into details of the errors I would like to ask if people
deeper into Ovirt would consider this a somewhat normal success rate,
or if this indicates we are doing something generally wrong and we
should definitely spend a few more hours or maybe days into finding
sources of problems.
More info about the system and errors
* OVirt 4.3.9 (because the prototype was made and verified with that
version - would be interesting to know, too, if it's strongly
considered to upgrade for more stable installation/deployment)
* The errors that appear are changing between the deployment process
seeming not to be able to transfer the "LocalHostedEngine" VM to the
glusterFS storage to become a "HostedEngine", and the other seems to
be when the engine is already up and running, but never being really
connected to the Ovirt system, continuously restarting, and also
showing XFS filesystem errors in it's dmesg output.
Any hints on our chances on getting this solved or requests for more
information about the error are welcome - thanks in advance.
Henning
3 years
New Install. 3 node HCI using 4.4.8 ISO
by shane.krenz＠gmail.com
Hello everyone. First time posting. Sorry if this is already been spoken to... I didn't see anything with a quick search that I did.
3 nodes running dual E5-2600 series V4 CPUs with 256G memory in a Hybrid storage config. 2x 1.9TB SSDs and 6x 600G SAS spinners attached to a SAS/SATA HBA. 4x 1G ports.
During initial boot from the 4.4.8. ISO oVirt installer I set static IPs, added DNS entries and copied ssh keys copied to each host.
First issue with deploying the cluster was complaining about partitions found on sdb even though I reclaimed and deleted everything on all drives. Ended up zero'ing the drives and started over. Then sdb was on the filter list. So I edited the LVM.conf file. now I am stuck on "Gluster brick_t is invalid, must be a file or device" No idea what to do about that one.
Also, I am not sure if its actually pulling in the 600G 10k drives into the mix at all. How would I confirm this?
First 1.9TB SSD drive Is where I am installing the OS. Should I change this to some other drive or usb stick and have the 2x SSDs as cache and all spinners as capacity data? not sure how all that is supposed to work as I am not too familiar with Gluster.
I know Nutanix and vSAN pretty well. I wanted to try oVirt. I am having a MUCH harder time with initial setup. I appreciate any help / suggestions on best practice for my hardware setup.
3 years
c9s - early?
by lejeczek
hi guys.
Though CentOS Stream 9 is available these are its early days
- may I ask @devel - how far away oVirt is from this new
CStream?
many thanks, L.
3 years
The Engine VM (/32) and this host (/32) will not be in the same IP subnet.
by notify.sina＠gmail.com
Hi list,
'The Engine VM (10.200.30.5/32) and this host (10.200.30.3/32) will not be in the same IP subnet.'
This happens when I select a static IP address configuration for the engine.
Ive been struggling with setting up ovirt-hosted-engine on CentOS 8 servers in the Equinix network, using hosted-engine --deploy.
Why would the setup not want the engine and the host it's being setup on, not be in the same subnet?
Can someone please help me understand what prerequisites I am missing?
3 years
Issue upgrading VDSM in 4.4.9
by ling＠aliko.com
Hello, I am trying to perform an oVirt host upgrade and ran into this issue and looking for advice.
If i try to run dnf update vdsm directly:
Problem: cannot install the best update candidate for package vdsm-4.40.80.5-1.el8.x86_64
- nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
After updating ovirt-release to 4.4.9, this is what I see available for libvirt-daemon:
[root@vmserver02 yum.repos.d]# dnf list libvirt-daemon-kvm
Last metadata expiration check: 2:09:25 ago on Wed 20 Oct 2021 01:28:56 PM PDT.Installed Packageslibvirt-daemon-kvm.x86_64 7.0.0-14.1.el8 @ovirt-4.4-advanced-virtualization
And the advance-virtualization repo points to this:
[ovirt-4.4-advanced-virtualization]
name=Advanced Virtualization packages for $basearch
mirrorlist=http://mirrorlist.centos.org/?arch=$basearch&release=8&repo=vi...
enabled=1
gpgcheck=1
gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Virtualization
module_hotfixes=1
I am trying this on Centos 8 and also RHEL 8 machines. Both giving the same errors.
Thanks.
3 years
creating a network using Rest API
by Pascal D
I am trying to create a new network using the Rest Api. This network Is for VM and needs to be part of a network label. Here is that Jason I am using. The network gets created but is not part of the network label. When I try to create it using the network labels href I get an error that the user is not authorized to create than resource label even though I am logged as the admin
https://xxxxxx.com/ovirt-engine/api/networks
{
"data_center": {
"id":"7eb5bf2a-8729-11e9-96c7-00163e449339"
},
"name":"D1-C1-763",
"description":"Test network",
"mtu":1472,
"stp": false,
"required":true,
"usages":{
"usage":["vm"]
},
"vlan":{"id":763},
"network_labels": {
"network_label": [{"id": "C1-VLAN"}]
}
}
when assigning a network label I do the following:
https://xxxxxx.com/ovirt-engine/api/networks/bc493d18-e3d5-4072-b36d-a42a...
{ "Id": "C1-VLAN" }
{
"detail": "[User is not authorized to perform this action.]",
"reason": "Operation Failed"
}
3 years
