-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yum upgrade failed #2737
Comments
Here are the existing repos on the host:
|
Moved to the site because the upgrade guide needs an update too. it says:
But as ansible-core is obsoleting ansible and we require an older ansible version, this command should be:
|
@dewongway can you confirm that on your system running |
@apinnick this is valid for both oVirt and RHV when RHEL 8.6 will GA as it introduces ansible-core 2.12 obsoleting ansible 2.9. |
I will create a bug if you are sure that Bug created: https://bugzilla.redhat.com/show_bug.cgi?id=2059877 |
@sandrobonazzola Sorry I missed your comment before. I kind of worked around this issue before seeing your comment. What I did was that I locked the version of the ansible package, similar to the ovirt-engine* packages. That allowed yum update to proceed. I just removed ansible from the versionlock and tested your suggestion using --nobest. It seems to work. However, I feel like locking the version is less messy as yum doesn't spill out the long list of complaints.
|
@dewongway yes version locking will suppress the warnings but when we'll move to ansible-core you'll fail to upgrade because of the version locking while with --best it wil work in both cases at the cost of having a few warnings noise. |
Hi, I'm new to opening issues. If I miss including important information here please let me know.
I'm trying to yum upgrade on the ovirt-engine host. I have already upgraded the engine itself successfully. I'm now doing yum upgrade on the CentOS 8 Stream and it's giving me the following dependency errors. Am I missing a repository for the dependencies?
Thanks
The text was updated successfully, but these errors were encountered: