Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3
by Andrei Verovski
Hi !
I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running as KVM appliance (not hosted engine).
This sequence of commands
yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
engine-upgrade-check
yum update ovirt\*setup\*
Results in a long list of dependency errors, short excerpt below.
Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance.
————— LOG ----------
Problem 1: problem with installed package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch
- package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed
Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed
- package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed
- package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed
- package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch
3 years, 5 months
Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3
by scrik787＠gmail.com
I changed the type in the cluster and now my hosted-engine machine won't start!. There
are no backups. How can I manually change the parameters of the machine from under the
roof so that it starts and I can restore ovirt to work
Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts a
pcie-root-port
VDSM.log https://pastebin.com/vsAKy9rX
3 years, 5 months
Host NonResponsive after migration to oVirt 4.4
by tferic＠swissonline.ch
Hi
I am looking for help after my oVirt upgrade failed.
I have upgraded from ovirt 4.3 to 4.4 following the instructions here:
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 <https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3>
It's a single-host (standalone engine) test environment.
I wiped CentOS 7 and reinstalled a fresh CentOS 8.
I installed the oVirt 4.4 repo and all the necessary software packets.
I used `engine-backup --mode=restore --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a backup file I created before I started the upgrade.
After the restore, I ran `engine-setup`.
I did not get any errors during any of these steps on the console.
So the upgrade could be considered successful from that perspective.
After the upgrade, I login to the ovirt admin portal, and I try to "Activate" my host (was set to "Maintenance" mode before upgrade).
The Activation fails with error "NonResponsive" in the GUI.
Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non responsive.”
In /var/log/ovirt-engine/engine.log, I find the following error:
```
2020-11-09 23:12:21,080+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb', vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution failed: java.net.ConnectException: Connection refused
```
`systemctl status ovirt-engine` shows that the engine is running.
I am able to reboot the host from the oVirt GUI directly.
Does anyone have an idea how to proceed?
Many thanks
Toni
3 years, 5 months
Clone a VM in the User Portal
by Nicolás
Hi,
We're using oVirt 4.3.8, having an organization that intensively uses
the User Portal. After upgrading from 4.2, we've noticed that cloning a
VM from within the User Portal is not possible anymore. In our case,
this feature was heavily used by hundreds of students deploying their VMs.
Is this feature in the roadmap yet? If not, do you consider it useful to
open a RFE?
Thank you.
Regards,
Nico
3 years, 5 months
Cannot restore engine from 4.3.9 to 4.4.3
by tferic＠swissonline.ch
Hi
I just tried to restore my engine backup taken from release 4.3.9.4 to a
newer oVirt installation release 4.4.3.11.
The restore process fails with a FATAL error.
I was under the impression that backups from all 4.3 versions were
supposed to be restorable on 4.4.
My installation is a single-box all-in-one (Standalone Engine installed
together with oVirt node).
# engine-backup --mode=restore
--file=/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
--provision-all-databases
Start of engine-backup with mode 'restore'
scope: all
archive file:
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
log file:
/var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log
Preparing to restore:
- Unpacking file
'/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup'
FATAL: Backup was created by version '4.3.9.4' and can not be restored
using the installed version 4.4.3.11
Complete content of the restore log file:
2020-11-11 03:15:00 23143: Start of engine-backup mode restore scope all
file
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
2020-11-11 03:15:00 23143: OUTPUT: Start of engine-backup with mode
'restore'
2020-11-11 03:15:00 23143: OUTPUT: scope: all
2020-11-11 03:15:00 23143: OUTPUT: archive file:
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
2020-11-11 03:15:00 23143: OUTPUT: log file:
/var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log
2020-11-11 03:15:00 23143: OUTPUT: Preparing to restore:
2020-11-11 03:15:01 23143: OUTPUT: - Unpacking file
'/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup'
2020-11-11 03:15:01 23143: Opening tarball
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
to /tmp/engine-backup.UAcLerghwY
2020-11-11 03:15:01 23143: Verifying hash
2020-11-11 03:15:01 23143: Verifying version
2020-11-11 03:15:01 23143: FATAL: Backup was created by version
'4.3.9.4' and can not be restored using the installed version 4.4.3.11
regards,
Toni Feric
3 years, 5 months
Problem with Cluster-wise BIOS Settings in oVirt 4.4
by Rodrigo G. López
Hi all,
We are running an oVirt 4.4 Hosted Engine as a VM, and after changing
the Cluster's BIOS type from Q35 with Legacy BIOS (the default one after
installation) to Preexistent, the VM fails with the following error:
XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts
a pcie-root-port.
We need it so that we can run imported VMs from a previous version of
oVirt, namely 4.0.
Applying the BIOS settings individually works but as an attempt to
generalize the settings we decided to apply it to the full cluster.
Tell me if you need more data.
Cheers,
-rodri
3 years, 5 months
oVirt 4.4.2 MS Windows 10 sysprep floppy
by ozmen62＠hotmail.com
Hi,
I've cretated a template which has sysprep.
Every document about sysprep says use "Attach Floppy" , but we know this function has been disabled/deprecated
So, when i use Run One, attach windows cdrom and put in it definitions (domain name, user credentials etc) , nothing happens.
I also have correct properties and sysprep files in engine
Just windows boot like it is new machine and ask lots of questions for prepare itself.
Would someone please explain this?
How can i run sysprep correctly?
3 years, 5 months
setting routing rules for guests?
by yam yam
Hello everyone!
I'm wondering there is any feature like applying routing rules for VM to reach the external network (and vice versa).
and I guess it's different according to using external provider(OVN).
if not, how to users usually assign floating IP to VM??
Thanks
Sincerely,
3 years, 5 months
Re: Clone a VM in the User Portal
by Arik Hadas
On Tue, Nov 10, 2020 at 10:10 PM tferic(a)swissonline.ch <
tferic(a)swissonline.ch> wrote:
> Cloning VM's is a core feature of virtualization.
>
> I remember having cloned VM's back in the 90's with the free VMware
> version 0.9.
>
> My main use case ever since is cloning fully configured production servers
> into a testservers, for isolated testing.
>
> Why would a hypervisor not offer cloning, when it is possible and useful?
>
> regards, Toni
>
(Added users(a)ovirt.org back)
Sure, it can be handy in some cases - that's why we've implemented it in
oVirt and enhance it in 4.4.3 (for running VMs).
But I wouldn't expect it to be commonly used via the user portal, that's
why I am interested in the use-case.
>
> On 10.11.20 16:22, Arik Hadas wrote:
>
>
>
> On Tue, Nov 10, 2020 at 4:37 PM Nicolás <nicolas(a)devels.es> wrote:
>
>> Hi Arik,
>>
>> El 10/11/20 a las 13:21, Arik Hadas escribió:
>>
>>
>>
>> On Tue, Nov 10, 2020 at 3:08 PM Nicolás <nicolas(a)devels.es> wrote:
>>
>>> Hi Sharon,
>>>
>>> Thanks for the reply! I've opened [1], so hopefully someone will be able
>>> to implement it.
>>>
>>> Regards,
>>>
>>> Nico
>>>
>>> [1]: https://github.com/oVirt/ovirt-site/issues/2389
>>>
>>> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>>>
>>> Hi,
>>>
>>> This feature of cloning a VM was indeed part of the old User Portal and
>>> you are right that it's not supported by the newer VM Portal (since oVirt
>>> 4.3).
>>> It seemed that this wasn't required by VM Portal users (no user
>>> complained up till now) and that's why we omitted it and it's not part of
>>> our current roadmap to implement it as well.
>>>
>>> Nevertheless, there is no real reason not to include that ability as
>>> part of VM Portal, so you are most welcome to open an issue on
>>> https://github.com/oVirt/ovirt-web-ui/issues
>>> <https://github.com/oVirt/ovirt-site/issues>
>>> and you can push a fix yourself if you have time (or someone else from
>>> the community) :-)
>>>
>>> Thanks!
>>> Sharon
>>>
>>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás <nicolas(a)devels.es> wrote:
>>>
>>>> Hi,
>>>>
>>>> We're using oVirt 4.3.8, having an organization that intensively uses
>>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a
>>>> VM from within the User Portal is not possible anymore. In our case,
>>>> this feature was heavily used by hundreds of students deploying their
>>>> VMs.
>>>>
>>>
>> Out of curiosity, why cloning a VM and not provisioning the VMs from
>> template(s)?
>>
>>
>>
>> Most of our students are IT-related, and their professors want to teach
>> them the procedure to deploy a VM from scratch. Some other courses surely
>> deploy their VMs from a template as they are not that IT oriented and they
>> just want to have a working VM instead of building it from scratch. We have
>> a lot of casuistry, but in our case about 400~500 students would very
>> welcome having back the clone option.
>>
>
> Thanks Nicolás.
> I'd say that even for the IT-related students it may make more sense to
> provision VMs from templates instead of cloning VMs -
> so you want them to deploy VMs from scratch, which means starting with a
> VM that is based on the blank template, add disk(s) and other devices,
> install and configure the guest and such; and then the students would use
> clone-VM to duplicate the VM they just prepared, right?
> Why would you want them to clone the VM rather than creating a template
> out of this VM and provision further VMs from that template with
> thin-provisioned disks?
>
>
>>
>> Regards,
>>
>> Nico
>>
>>
>>>> Is this feature in the roadmap yet? If not, do you consider it useful
>>>> to
>>>> open a RFE?
>>>>
>>>> Thank you.
>>>>
>>>> Regards,
>>>>
>>>> Nico
>>>> _______________________________________________
>>>> 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://lists.ovirt.org/archives/list/users@ovirt.org/message/HFMFJRV3AC3...
>>>>
>>>
>>> _______________________________________________
>>> 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://lists.ovirt.org/archives/list/users@ovirt.org/message/RUEW52WZUD2...
>>>
>>
>>
> _______________________________________________
> 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://lists.ovirt.org/archives/list/users@ovirt.org/message/QXPS6FCRT66...
>
>
3 years, 5 months
[ANN] oVirt 4.4.3 is now generally available
by Sandro Bonazzola
oVirt 4.4.3 is now generally available
The oVirt project is excited to announce the general availability of oVirt
4.4.3 , as of November 10th, 2020.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade
Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).
Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.
For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXE...
)
Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>.
What’s new in oVirt 4.4.3 Release?
This update is the third in a series of stabilization updates to the 4.4
series.
This release is available now on x86_64 architecture for:
-
Red Hat Enterprise Linux 8.2 / 8.3
-
CentOS Linux (or similar) 8.2
-
CentOS Stream (tech preview)
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
-
Red Hat Enterprise Linux 8.2 / 8.3
-
CentOS Linux (or similar) 8.2
-
CentOS Stream (tech preview)
Please note that this release introduces cluster compatibility level 4.5
which is supported only with Red Hat Enterprise Linux 8.3 or equivalent.
oVirt Node and Appliance have been updated, including:
-
oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/
-
Ansible 2.9.15:
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v...
-
Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Notes:
-
oVirt Appliance is already available for CentOS Linux 8
-
oVirt Node NG will be available soon for CentOS Linux 8
Additional resources:
-
Read more about the oVirt 4.4.3 release highlights:
https://www.ovirt.org/release/4.4.3/
-
Get more oVirt project updates on Twitter: https://twitter.com/ovirt
-
Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] https://www.ovirt.org/release/4.4.3/
<https://www.ovirt.org/release/4.4.3/>
[2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
3 years, 5 months
