On Fri, May 7, 2021 at 2:39 AM Derek Atkins <derek@ihtfp.com> wrote:

[snip]

*THIS* truly answers my underlying question(s). I was concerned that the
engine would be like the node, but this assures me it is not, it's just a
"faster" way to build the engine VM, but it turns into (effectively) a
standard CentOS+Engine VM post-install... Which SHOULD be good enough for
what I want to do! (I have the engine running a few extra services, and
wanted to make sure I could continue to do so).

OK.

But in the mid term the problem will impact you anyway.

What to do after 31/12/2021 with this system, as no new updates from CentOS repos?

I think in the next months it would be nice to have at least a CentOS --> CentOS Stream migration path for the Hosted Engine VM or for an external engine that are now based on CentOS

Or to confirm that the standard path described at https://centos.org/centos-stream/ works also for CentOS systems where oVirt repos are configured and active and engine packages installed.

Currently it says:

dnf swap centos-linux-repos centos-stream-repos
dnf distro-sync

Gianluca