cannot export - "r.original_template is undefined"
by Diggy Mc
I cannot export a VM to a data domain. I receive the error:
Export VM Failed
r.original_template is undefined
The VM originated as an OVA provided by a third party. After importing the OVA and customizing the VM, I wanted to export it for backup purposes, but cannot.
I am running oVirt 4.4.4. You can download the OVA directly from ERPNext.org if that helps troubleshooting. Download the "Production Image" from here: https://erpnext.org/get-started
Any help is appreciated and let me know if additional information is needed.
4 years
oVirt longevity after CentOS 8, RHV changes
by David White
I'm replying to Thomas's thread below, but am creating a new subject so as not to hijack the original thread.
I'm sure that this topic has come up before.
I first joined this list last fall, when I began planning and testing with oVirt, but as of the past few weeks, I'm paying closer attention to the mailing list now that I'm actually using oVirt and am getting ready to deploy to a production environment.
I'll also try to jump in and help other people as time permits and as my experience grow.
I echo Thomas's concerns here. While I'm thankful for Red Hat's gesture to allow people to use up to 16 Red Hat installs at no charge, I'm concerned about the longevity of oVirt, now that Red Hat is no longer going to support RHV going forward.
What is the benefit to Red Hat / IBM of supporting this platform now that it is no longer being commercialized as a Red Hat product? What is to prevent Red Hat from pulling the plug on this project, similar to what happened to CentOS 8?
As a user of oVirt (4.5, installed on Red Hat 8.3), how can I and others help to contribute to the project to ensure its longevity? Or should I really just go find an alternative in the future? (I had been planning to use oVirt for a while, and did some testing last fall, so the announcement of RHV's (commercial) demise was poor timing for me, because I don't have time to switch gears and change my plans to use something else, like Proxmox or something.
From what I've seen, this is a great product, and I guess I can understand Red Hat's decision to pull the plug on the commercial project, now that OpenShift supports full VMs. But my understanding is that OpenShift is a lot more complicated and requires more resources. I really don't need a full kubernetes environment. I just need a stable virtualization platform.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, April 1, 2021 5:44 PM, Thomas Hoberg <thomas(a)hoberg.net> wrote:
> I personally consider the fact that you gave up on 4.3/CentOS7 before CentOS 8 could have even been remotely reliable to run "a free open-source virtualization solution for your entire enterprise", a rather violent break of trust.
>
> I understand Redhat's motivation with Python 2/3 etc., but users just don't. Please just try for a minute to view this from a user's perspective.
>
> With CentOS 7 supported until 2024, we naturally expect the added value on top via oVirt to persist just as long.
>
> And with CentOS 8 support lasting until the end of this year, oVirt 4.4 can't be considered "Petrus" or a rock to build on.
>
> Most of us run oVirt simply because we are most interested in the VMs it runs (tenants paying rent).
>
> We're not interested in keeping oVirt itself stable and from failing after any update to the house of cards.
>
> And yes, by now I am sorry to have chosen oVirt at all, finding that 4.3 was abandonend before 4.4 or the CentOS 8 below was even stable and long before the base OS ran out of support.
>
> To the users out there oVirt is a platform, a tool, not a means to itself.
4 years
New Management VLAN for hyperconverged cluster
by David White
I'm working on setting up my environment prior to production, and have run into an issue.
I got most things configured, but due to a limitation on one of my switches, I decided to change the management vlan that the hosts communicate on. Over the course of changing that vlan, I wound up resetting my router to default settings.
I have the router operational again, and I also have 1 of my switches operational.
Now, I'm trying to bring the oVirt cluster back online.This is oVirt 4.5 running on RHEL 8.3.
The old vlan is 1, and the new vlan is 10.
Currently, hosts 2 & 3 are accessible over the new vlan, and can ping each other.
I'm able to ssh to both hosts, and when I run "gluster peer status", I see that they are connected to each other.
However, host 1 is not accessible from anything. I can't ping it, and it cannot get out.
As part of my troubleshooting, I've done the following:
From the host console, I ran `nmcli connection delete` to delete the old vlan (VLAN 1).
I moved the /etc/sysconfig/network-scripts/interface.1 file to interface.10, and edited the file accordingly to make sure the vlan and device settings are set to 10 instead of 1, and I rebooted the host.
The engine seems to be running, but I don't understand why.
From each of the hosts that are working (host 2 and host 3), I ran "hosted-engine --check-liveliness" and both hosts indicate that the engine is NOT running.
Yet the engine loads in a web browser, and I'm able to log into /ovirt-engine/webadmin/.
The engine thinks that all 3 hosts is nonresponsive. See screenshot below:
[Screenshot from 2021-04-07 17-33-48.png]
What I'm really looking for help with is to get the first host back online.
Once it is healthy and gluster is healthy, I feel confident I can get the engine operational again.
What else should I look for on this host?
Sent with ProtonMail Secure Email.
4 years
How to restore Storage Domain from disaster recovery
by miguel.garcia＠toshibagcs.com
My engine drop dead so had to create a new one and I'm trying to recover virtual drives from previous engine. I'm using next instructions to import storage domain https://www.ovirt.org/develop/release-management/features/storage/imports... but in order to do it well need to unattach storage domain from previous engine which that is not possible right now since the engine has died. Anyway discarting requirements I got the following warning message:
This operation might be unrecoverable and destructive!
Storage Domain(s) are already attached to a Data Center. Aproving this operation might cause data corruption if both Data Centers are Active.
Do you have an idea how to deactivate a Storage domain without ovirt-engine?
Is there any chance to export virtual drives as backups without engine?
Thanks in advance.
4 years
oVirt 4.4.4 not dislaying Sign-on Screen
by louisb＠ameritech.net
I recently installed oVirt 4.4.4, everything appeared to run successfully, however, I’m unable to get the sign-on screen to display on my RHEL 8.3 machine. I did do an install using the remote database installation. I encountered no issue with the install, I can see the “engine” and “ovirt_engine_history” in PostgreSQL 13.3. The tables and table spaces have all been created as designed by the installation process.
When I enter the URL that was displayed once the installation completed I get the following information displayed on the screen:
Internal Error
I’ve tried using the port 443 and port 80 URL and get the same results. The URL are as follows:
http://WorkstationName:80/ovirt-engine
https://WorkstationName:443/ovirt-engine
For three days I’ve been trying to locate logs that will help me located and resolve the problem, but so far I’ve had no luck.
Can anyone tell where I should start looking to resolve my issue? I’ve checked several system logs and logs for Apache with luck. What should I be looking for within the logs? What logs should I be looking at?
I don’t believe my issue is with the back-end database, I thinks its something with Apache not being able to find the web pages to display. How can I start to investigate my problem an develop a solution?
My Linux/RHEL 8.3 OS has all of the latest patches and fixes applied.
Thanks
4 years
Re: Restored engine backup: The provided authorization grant for the auth code has expired.
by Nicolás
Hi Shani,
El 6/4/21 a las 15:15, Shani Leviim escribió:
> Hi,
> Did you try to refresh the page and try again?
Yes, several times. Also different browsers with no difference.
> Can you share a screenshot?
Sure. Adding the screenshot in this e-mail. This happens after
authenticating like admin (internal) on either the administration panel
or the VM portal.
Thanks.
>
> *Regards,
> *
> *Shani Leviim
> *
>
>
> On Tue, Apr 6, 2021 at 4:20 PM Nicolás <nicolas(a)devels.es
> <mailto:nicolas@devels.es>> wrote:
>
> bump...
>
> El 26/3/21 a las 8:21, Nicolás escribió:
> > Please, any help with this?
> >
> > El 24/3/21 a las 10:05, Nicolás escribió:
> >> Hi,
> >>
> >> I'm restoring a full ovirt engine backup, having used the
> --scope=all
> >> option, for oVirt 4.3.
> >>
> >> I restored the backup on a fresh CentOS7 machine. The process went
> >> well, but when trying to log into the restored authentication
> system
> >> I get the following message which won't allow me to log in:
> >>
> >> The provided authorization grant for the auth code has expired.
> >>
> >> What does that mean and how can it be fixed?
> >>
> >> Thanks.
> >>
> >> Nicolás
> >> _______________________________________________
> >> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> >> To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@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/PADF5SSC6XU...
> > _______________________________________________
> > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> > To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@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/5VYLMSCUGDD...
> _______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@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/N6Q4EEC3KKK...
>
4 years
Engine Upgrade to 4.4.5 Version Number Question
by Nur Imam Febrianto
I’m currently trying to upgrade our cluster from 4.4.4 to 4.4.5. All using oVirt Node.
All host are successfully upgraded to 4.4.5 (I can see the image layer was changed from 4.4.4 to 4.4.5, cockpit also shows same version), but in Engine VM, already run engine-upgrade-check, upgrading ovirt-setup, running engine-setup successfully, reboot the engine but whenever I open the engine web page, it still showing Version 4.4.4.5-1.el8. Is this version correct ? Because my second Cluster that use their own hosted engine shows different version (4.4.5.11-1.el8). Anybody having a same issues like me ?
Thanks before.
Regards,
Nur Imam Febrianto
4 years
Re: Upgrading DWH from 4.4.4 to 4.4.5
by Yedidyah Bar David
On Thu, Mar 18, 2021 at 6:47 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote:
>
> Hi,
>
>
>
> I’m currently trying to upgrade my oVirt Cluster into 4.4.5. Hosted engine upgrade work successfully. But whenever I tried upgrading DWH on separate machine it keep giving me this error : Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans'
>
>
>
> In engine-setup log :
>
>
>
> 2021-03-18 23:34:10,976+0700 DEBUG otopi.context context._executeMethod:145 method exception
>
> Traceback (most recent call last):
>
> File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod
>
> method['method']()
>
> File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/apache/selinux.py", line 40, in _misc
>
> osetupcons.SystemEnv.SELINUX_BOOLEANS
>
> KeyError: 'OVESETUP_SYSTEM/selinuxBooleans'
>
> 2021-03-18 23:34:10,977+0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans'
>
>
>
> Using CentOS 8.3 as separate DWH machine. Anybody maybe can help me ?
>
> Thanks before.
Sorry, this is looks like a bug, caused by [1]. Would you like to
report it on bugzilla?
I think a workaround is to run engine-setup like this:
# engine-setup --otopi-environment=OVESETUP_SYSTEM/selinuxBooleans=multi-str:\
The shell will prompt with '> '. Just press Enter.
Martin - seems like I was wrong when commenting on [1] that it seems harmless...
Marcin: we should probably add separate-dwh to ovirt-system-tests or
something like that.
[1] https://gerrit.ovirt.org/c/ovirt-engine/+/113263
Sorry and best regards,
--
Didi
4 years
4.4 -> 4.3
by KSNull Zero
Hi,
What is the most simpliest way to backward migrate VMs from oVirt 4.4 to oVirt 4.3 ?
Is it possible to use export domain or there are some other ways ?
Thank you.
4 years
