https://alt.fedoraproject.org/cloud/ includes Cloud Base image for Openstack which is intended to ease the usage of Fedora on OpenStack. To improve the integration with OpenStack and other VM management systems (oVirt, KubeVirt), each user would have to install and enable qemu-guest-agent on it before usage.
Please help our consumers and enable qemu-guest-agent in the OpenStack image.
Steps to Reproduce: 1. Import https://download.fedoraproject.org/pub/fedora/linux/releases/33/Cloud/x86_64/images/Fedora-Cloud-Base-33-1.2.x86_64.qcow2 to KubeVirt (or oVirt or OpenShift)
Actual results: Guest-provided data (IP addresses, logged in users) are not available
Expected results: qemu-guest-agent is running out-of-the box
Additional info: This can be worked around by each end user with
but the whole point of having a Cloud Base Image is to provide the best user experience out of the box.
This is a clone of https://bugzilla.redhat.com/show_bug.cgi?id=1899501
I don't want this agent installed or enabled on my AWS or GCP instances by default. This sounds like something that should be handled by Openstack when adding the image and not the base cloud image.
Metadata Update from @dustymabe: - Issue tagged with: meeting
Added the meeting label.
We discussed this at the community meeting today.
* AGREED: since the unit appears to be inert on any system that can't take advantage of the service, we propose to add qemu-guest-agent to the base package set. We won't include it on GCP since we have a separate image for GCP already. In the future we may make other images specific to cloud providers, in which case we'll also remove it from those variants. (dustymabe, 16:20:33)
@davdunc has agreed to help us make this change.
https://pagure.io/fedora-kickstarts/pull-request/737 has merged
Metadata Update from @ngompa: - Issue untagged with: meeting
Metadata Update from @ngompa: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.