@danken you may consider pushing a pull request to https://pagure.io/fedora-kickstarts or opening a bug against https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=spin-kickstarts for starting the discussion about adding ovirt-guest-agent to fedora images.

You can do the same for CentOS if you want to speed up before RHEL moves by opening a bug on https://bugs.centos.org reporting against Cloud Instance SIG. Please open a bz on ovirt-distribution asking to get ovirt-guest-agent built in CentOS Virt SIG too, right now it's only in EPEL.

@Sandro Bonazzola, would a nicer error message from ovirt-guest-agent make things better? I think that shipping the agent, but not enabling it, is a reasonable solution, anyway.

The user can pull in the agent with cloud-init. @Eitan Raviv did it. it works. But it is slow and cumbersome.

Please note that I am trying to solve my problem downstream, with
Bug 1323690 - New package request: ovirt-guest-agent
if accepted to RHEL, it would pop into CentOS and become easier to include in its cloud images.

AFAIK if the ovirt-guest-agent is included in an appliance provided by Fedora or CentOS build system, the agent will crash by default when running on standard qemu (OSError: [Errno 2] No such file or directory: '/dev/virtio-ports/ovirt-guest-agent.0')

So it will be unlikely added to distribution provided images.
We can respin the images ourselves but at least in integration team we have no man power to address this.
Can't user just install it with some ansible command or with cloud-init ?

@Sandro Bonazzola any thoughts?

@sbonazolla, what would it take to include an enabled ovirt-guest-agent in one of the images of https://cloud.centos.org/centos/7/images/ ?