On 26.06.19 13:02, markus.falb(a)mafalb.at wrote:
Thanks Oliver,
> a Node installation is image based and this should not happen ...
What should not happen? That it is manually updated via yum? Hmm, always done that with
previous versions.
I never saw version locked packages on a node before. I went from 4.2.x
over previous
4.3.x versions to 4.3.4 and didn't have or see any versionlocks. What
packages are locked ?
# yum versionlock status
Could it be a list of obsoletes ?
> On an Engine system you have to call engine-setup again
(don't worry)
> which updates installation files and then installs the versionlock'ed
> packages.
But on an my engine there are no versionlocks, and there are the ovirt repos active, I
thought that updates would be picked up with an yum update. I thought that engine-setup is
only for upgrades (minor and/or major version bump)
you are right on this.
Best regards, Oliver
> Best regards, Markus
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WQCZ7MNZAGO...