Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by k.gunasekhar@non.keysight.com
I also end up with the same problem today. How did rollback yum i see many yum updates in the yum history.
Here is what the error says.
The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_IvyBridge, spec_ctrl. Please update the host CPU microcode or change the Cluster CPU Type.
2 years, 10 months
Adding a 4th compute host to a HCI environment
by David White
Hello,
Is there documentation anywhere for adding a 4th compute-only host to an existing HCI cluster?
I did the following earlier today:
- Installed RHEL 8.4 onto the new (4th) host
- Setup an NFS share on the host
- Attached the NFS share to oVirt as a new storage domain
- I then turned the NFS share into a "backup domain"
- Once that was done, I installed ovirt-release44.rpm, followed by some ovirt packages:
- yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
- yum install cockpit-ovirt-dashboard vdsm-gluster ovirt-host
- I then logged into the oVirt Manager Web UI, navigated to Hosts, and clicked on New
- I successfully added the new host to the cluster
Once this was all done, load average on all 3 of my original HCI nodes started to go through the roof.
I've seen servers' load average go through the roof before when NFS shares are down, so I suspect that something happened to the NFS share when I went to add the host as a compute node.
In an effort to get things stabilized, I wound up yanking the new host out of oVirt, as well as the NFS share, at which point things did stabilize again.
My goal here:
- Setup the host as a compute-only host (don't participate in the gluster cluster)
- Setup the NFS share for backup purposes
Writing this email and reviewing my bash history, I think one of the places I went wrong was I installed vdsm-gluster. I don't think I need that, do I?
Is what I'm trying to do possible?
Sent with ProtonMail Secure Email.
2 years, 10 months
Guest CPU compatibility issues on upgraded host - RHEL 8
by David White
I have oVirt 4.4.6 running on my Engine VM.
I also have oVirt 4.4.6 on one of my hosts.
The other two hosts are still on oVirt 4.4.5.
My issue seems slightly different than the issue(s) other people have described.
I'm on RHEL 8 hosts.
My Engine VM is running fine on the upgraded host, as is one of my Ubuntu guests.
However, it seems like I'm not able to migrate *ANY* other guests over the new host. The oVirt UI just indicates that for whatever reason the upgraded host isn't available / compatible for a VM to be migrated to.
I'm not sure how or why this 1 Ubuntu guest VM was able to get migrated, but it looks like its working just fine.
I did try:
yum downgrade edk2-ovmf
Base on other people's comments. But I'm not sure how long to wait, or what else to try, to try to get my upgraded host operational again.
Sent with ProtonMail Secure Email.
2 years, 10 months
issue creating disk with rest api using json format
by Pascal D
I am unable to create disk using JSON however the same query in XML works great. In Json I get the following message back:
{
"detail": "For correct usage, see: https://ov1.butterflyit.com/ovirt-engine/apidoc#services/disks/methods/add",
"reason": "Request syntactically incorrect."
}
Both use POST /ovirt-engine/api/disks and the content-type is either application/json or application/xml
Here is the request in JSON:
{
"id": "866770c3-acf9-4f67-b72c-05ed241908e4",
"name": "mydisk",
"description": "test disk",
"bootable": false,
"shareable": true,
"provisioned_size": 10240000000,
"interface": "virtio",
"format": "cow",
"storage_domains": {
"storage_domain": {
"name": "VMS"
}
}
}
And here it is in XML
<disk id="866770c3-acf9-4f67-b72c-05ed241908e4">
<bootable>false</bootable>
<name>mydisk</name>
<description>test Drive</description>
<interface>virtio</interface>
<provisioned_size>10240000000</provisioned_size>
<format>cow</format>
<storage_domains>
<storage_domain>
<name>VMS</name>
</storage_domain>
</storage_domains>
</disk>
2 years, 10 months
Ovirt 4.4.6.8 High Performance VM quirkiness
by Don Dupuis
I created a high performance vm and everything is fine. I stop the virtual
machine and make edits to it and again runs correctly. I shutdown the vm
and click the edit tab to look at what I changed and it is now back to the
defaults and my edits are gone. Is this now the intended result. I was
using the same settings in 4.3 and never exhibited this behavior. What I
have observed so for is that I disabled Headless, disabled cpu pinning, and
changed numa config. When I shutdown the vm, they revert to default of
Headless enabled, cpu pinning is set and the numa config changed. This is
not what I expect to happen. Has anyone else noticed this behavior?
Thanks
Don
2 years, 10 months
Centos 8 to Centos Stream
by nikkognt@gmail.com
Hi,
in preparation for upgrade of stand alone engine from centos 8 to centos stream, I would like to know if exist a procedure to follow for this operation or I must only follow the instruction on CentOS official site. [1]
Best regards
Nikkognt
[1] https://www.centos.org/centos-stream/
2 years, 10 months
CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by Nur Imam Febrianto
Hi,
This morning I have a problem that suddenly my Host (Using Centos 8 Stream, not oVirt Node) showing error with Cpu Compatibility. It says my CPU doesn’t have Haswell-noTSX and spec_ctrl flag. After downgrading the kernel back from 4.18.0 – 305 to 4.18.0 – 301.1 and rollback yum update, it working again. Do anybody having same issue ?
I’m using Xeon E5-2695v4 with cluster compatibility Secure Intel Haswell. Using oVirt 4.4.6 on CentOS Stream host.
Thanks before.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
2 years, 10 months
Re: Import Ge0-Replicated Storage Domain fails
by Simon Scott
Just to clarify...
Site A has volume data2 which geo-replicates to Site B
Site B has volume data1 which geo-replicates to Site A
I will look at the engine upgrade and ansible today.
2 years, 10 months
Cluster stuck in maintenance - Hosts not upgrading as expected
by David White
I have a 3-node hyperconverged cluster with Gluster filesystem running on RHEL 8.3 hosts.
It's been stable on oVirt 4.5.
Today, I just upgraded the Engine to v4.6.
[Screenshot from 2021-05-22 20-29-23.png]
I then logged into the oVirt manager, navigated to Compute -> Clusters, and clicked on Upgrade.
The Status of the cluster does have an exclamation mark that says "Upgrade Cluster Compatibility Level", but my understanding is, I shouldn't do that until all 3 of my hosts have been upgraded.
Looking at active tasks, I see that the first host in my cluster is stuck in "Upgrading".
It's now been like this for 3 hours, without any visible progress.
If I try to launch a VM that is not configured for high availability, the VM fails to launch, and I get a message about the cluster being in "Maintenance Mode" and that none of the hosts satisfies current scheduling restraints.
How do I....
a) Cancel / clear the upgrade and take the cluster out of "maintenance mode"
b) Properly upgrade the cluster, since clicking the "Upgrade" button clearly didn't work?
Thanks,
David
Sent with ProtonMail Secure Email.
2 years, 10 months