Greg,
The first thing on the list in your link is to check what repos are enabled with yum repolist, but makes no mention of what repos should be enabled on node-ng, nor what to do about it if you have the wrong ones. I've never had an Ovirt update go the way it was "supposed" to go, despite having a bunch of documentation at hand. Usually I end up blowing away the hosts and starting with a fresh ISO.
The page you linked makes no mention of the command Edward mentioned that got things working for me:
yum update ovirt-node-ng-image-update
All the instructions I can find just say to run yum update, but that resulted in a bunch of dependency errors for me, on a normal 4.2.6 node install that I haven't touched since installation. Why? If I'm following the instructions, shouldn't it work?
running this command in the upgrade guide:
Gives me "This system is not registered with an entitlement server". Is that an outdated instruction? Does it apply to the particular update I'm trying to apply? No way to tell...
What would really help is a clear separation between commands intended for centos/RHEL and commands intended for Node. As an outsider, it's very difficult to know. Every chapter, where there is any difference in procedure, the documents should be split with RHEL on one side and NODE on the other.
The documentation would also benefit from tags like dates and versions that they apply to. "Valid for Ovirt 4.2.6 to 4.2.8 as of Feb 2, 2019". Then the documents should be tested and the dates/versions adjusted, or the docs adjusted, as needed.
Ovirt is awesome. But the docs are the project's worst enemy.
