Proposal to drop support for oVirt

It’s a lot of work and I see it as a waste of time at this point. We already have a mechanism to either install it or not (install foreman-ovirt or remove it). Building a plugin means setting up the whole gem, publishing it, doing packaging, think about the migration, doing regression testing.

Rather than forking the gem, why not get involved in oVirt development and do it proper?

1 Like

One of the oVirt developers was so kind to issue release 4.6.0. Currently waiting for upload to rubygems.org:face_holding_back_tears:

4 Likes

I see we have ovirt-engine-sdk 4.6.0 in our repos for a while. Has someone tried this on our Foreman 3.10 EL9 builds or 3.11 RC? I wonder, whther there’s other Ruby 3 related issues.