Images upload - Content Security Policy
by jiri.mikulas＠mibcon.cz
Hello
I'm using Oracle Linux with ovirt-engine 4.5.5-1.22.el8
Operating System: Oracle Linux Server 8.10
Kernel: Linux 5.15.0-301.163.5.2.el8uek.x86_64
After upgrading from ovirt-engine version 4.5.5-1.21.el8 to version 4.5.5-1.22.el8, there seems to be an issue with uploading images.
When trying to test the connection for uploading images using
Storage -> Domains -> MyStorage -> Disks -> Upload
I debugged network communication in "chrome inspect" and received the error:
"Refused to connect to https://ovirt-engine:54323/info/ because it appears in neither the connect-src directive nor the default-src directive of the Content Security Policy."
Has anyone encountered this problem?
I have the CA certificate properly imported since version 4.5.5-1.21.el8, where the uploads worked normally.
Regards
Jiri
6 months, 3 weeks
Adding ISO doesn't work
by sol-pl-cm＠nttdata.com
I have a problem adding ISO. Fresh installation of OracleLinux-R8-U10 with Ovirt Version:4.5.5-1.22.el8 installed on it. I've already gone through all possible forums and threads with a similar problem, but none of them have been solved, and I haven't been able to solve the ISO problem either.
Engine is installed as a virtual machine on VMware and manages two KVM hosts (also a fresh install). I replaced the certificates for the test, but it didn't help and I went back to the old configuration.
I keep getting a certificate error when running the test, even though I added it to the browser. I tested on different browsers. "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser."
Can I get help here?
6 months, 3 weeks
Need advice before building a new oVirt Environment
by gbigras＠telesat.com
My question will be down below but before that here is some background info:
I currently have a functioning oVirt env (v4.5.7) with two self-hosted nodes (hand-me-down servers) and shared storage (TrueNAS server) with three data domains: one for the EngineVM (iSCSI), one for the VMs (iSCSI) and one for ISO files (NFS).
The powers that be, want to move away from TrueNAS and hand-me-downs and have new servers and a new NAS appliance (most likely NetApp). They are the ones who did not want to spend the money on new gear but now they have changed their minds. I wish that I could have started my oVirt env on the new equipment. This new equipment will take at best 2 months to arrive. In the meantime, I have to create various VMs in my existing environment.
Once my new gear arrives, what is the recommended approach:
1 - Start from scratch with a new datacenter/cluster env? Can I migrate VMs from one DC to another? The docs seem to say no. I'm guessing, I would have to export first, then import.
2 - Can my new equipment be part of the same DC but a different cluster?
I was thinking that option #2 is the right approach. I could start with storage (ie: new NetApp) as part of the new cluster. Once that is part of the cluster, I can add hosts then finally migrate VMs.
What say you?
thank you in advance.
6 months, 3 weeks
Ovirt Storage Monitoring behind RAID
by ankit＠eurus.net
Hi Folks,
I have recently build Ovirt 4.5 cluster with server(DellXC 360 and 730xd) as storage using iscsi target where i want to monitor disks behing RAID(Perc Card). How can i monitor disks in ovirt itself ?
Thanks.
AS
6 months, 3 weeks
Preparing to issue an oVirt release post Red Hat offboarding
by Sandro Bonazzola
Hi, Oracle fixed CVE-2024-7259 ( https://github.com/oVirt/ovirt-engine/security/advisories/GHSA-8xjm-j7fq-... ) in oVirt Engine and would be nice to issue an oVirt Engine release including the fix.
As the current master also includes support for new cluster level 4.8, VDSM needs to be released as well providing cluster level 4.8.
As you know, Red Hat offboarded the project and as such there are no more people officially assigned to the project from the company, despite a few of the historical developers still spend some of their free time helping out.
I can help building the packages and getting them out on my free time but I have no capacity for doing any testing or documentation updates or release notes related to this release.
Last oVirt Engine (4.5.6) was also released last February without any formal release announce.
Any volunteer to look into differences between current master and current stable release and see if anything else needs to be released other than ovirt-engine and vdsm?
Any volunteer to write release notes and update the website accordingly?
Any volunteer to run ovirt-system-test on https://github.com/oVirt/ovirt-engine/pull/970 and https://github.com/oVirt/vdsm/pull/422 as OST doesn't run anymore on GitHub?
Regards,
--
Sandro Bonazzola
7 months
Installation of hosts on RHEL9
by Fabrice Bacchella
Hi,
I’m migrating to oVirst 4.7 and RHEL9.
The engine is up and running but I have problems testing adding new hosts.
It fails running the command:
sudo vdsm-tool ovn-config $IP $FQDN.
The message is
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py", line 118, in get_network
return networks[net_name]
KeyError: '$FQDN'
And indeed if I print net_caps in the method net_caps of ovn_config, it says:
{'networks': {} ...
I have been unable to understand where this information is coming from, what is missing in my host ? Are they the networks as configured in the engine ?
7 months
HostedEngine VM doesn't start because in QXL video type mode
by Mario Indelicato
Hi,
I don't know how this happened but after an host reboot, the HostedEngine VM didn't started anymore.
The error in the log is:
"unsupported configuration: domain configuration does not support video model 'qxl'"
This is a single host test environment, OS is Rocky 9.4, so I know it's expected that QXL video is not supported anymore.
I tried editing the HostedEngine VM configuration via virsh, but when I start the VM it keeps trying to use QXL.
Also the VM conf in "/var/run/ovirt-hosted-engine-ha/vm.conf" says the video type is always QXL.
I tried dumping the XML configuration, edit the XML, undefined e re-define the VM from the updated XML, but still it uses QXL!!!
I'm resigned myself that the only solution is to re-deploy the HostedEngine from scratch.
Unless some of you can provide an alternative solution.
Many thanks in advance
Mario
7 months
Updating hosts OS - conflicts with ansible-core
by ivohccarvalho＠gmail.com
Hi.
I'm trying to update my hosts running RHEL 8.6 however I'm getting the following error:
[root@euovi01 yum.repos.d]# yum update
Updating Subscription Management repositories.
Last metadata expiration check: 0:18:58 ago on Mon 28 Oct 2024 04:06:04 PM WET.
Error:
Problem: package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch conflicts with ansible-core >= 2.13 provided by ansible-core-2.16.3-2.el8.x86_64
- cannot install the best update candidate for package ansible-core-2.12.2-4.el8_6.x86_64
- problem with installed package ovirt-hosted-engine-setup-2.6.6-1.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
What would be the best approach here?
7 months
Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2025
by Piotr Kliczewski
We are excited to announce that the call for proposals is now open for the
Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM
2025, to be hosted on Sunday (Feb 2) 2025.
This devroom is a collaborative effort, and is organized by dedicated folks
from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and
Foreman. We invite everyone involved in these fields to submit your
proposals by December 8th, 2024.
About the Devroom
The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors or virtual machine managers such as Xen Project, KVM,
bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such
as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula.
This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.
Presentations in this devroom will be aimed at developers working on these
platforms who are looking to collaborate and improve shared infrastructure
or solve common problems. We seek topics that encourage dialog between
projects and continued work post-FOSDEM.
Important Dates
Submission deadline: 8th December 2024
Acceptance notifications: 10th December 2024
Final schedule announcement: 15th December 2024
Devroom: 2nd February 2025
Submit Your Proposal
All submissions must be made via the Pretalx event planning site[1]. It is
a new submission system so you will need to create an account. If you
submitted proposals for FOSDEM in previous years, you won’t be able to use
your existing account.
During submission please make sure to select Virtualization and Cloud
infrastructure from the Track list. Please provide a meaningful abstract
and description of your proposed session.
Submission Guidelines
We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.
All presentation slots are 30 minutes, with 20 minutes planned for
presentations, and 10 minutes for Q&A.
All presentations will be recorded and made available under Creative
Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:
"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License.
Sincerely,
<NAME>."
In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend FOSDEM and deliver your presentation.
We will not consider proposals from prospective speakers who are unsure
whether they will be able to secure funds for travel and lodging to attend
FOSDEM. (Sadly, we are not able to offer travel funding for prospective
speakers.)
Code of Conduct
Following the release of the updated code of conduct for FOSDEM[3], we'd
like to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
times.
If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.
Questions?
If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
other attendees.
See you all at FOSDEM!
[1] https://pretalx.fosdem.org/fosdem-2025/cfp
[2] virtualization-devroom-manager at fosdem.org
[3] https://fosdem.org/2025/practical/conduct/
7 months
IPv4 vs IPv6 vs dual-stack
by Diggy Mc
With respect to oVirt hosts and the hosted-engine, what are the pros and cons of using just IPv4, or just IPv6, or using both?
7 months
