Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
upgrading ovirt node fails. Fence-agents release -85 is incomplete
Version-Release number of selected component (if applicable):
fence-agents-common-4.2.1-85
How reproducible:
always
Steps to Reproduce:
1. dnf make cache
2. dnf upgrade
Actual results:
# dnf upgrade
Last metadata expiration check: 0:00:04 ago on Thu 03 Feb 2022 05:19:40 PM CET.
Error:
Problem 1: package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed
- cannot install both fence-agents-common-4.2.1-85.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch
- cannot install the best update candidate for package fence-agents-ibm-powervs-4.2.1-84.el8.noarch
- cannot install the best update candidate for package fence-agents-common-4.2.1-84.el8.noarch
Problem 2: package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed
- cannot install both fence-agents-common-4.2.1-85.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-amt-ws-4.2.1-85.el8.noarch requires fence-agents-common >= 4.2.1-85.el8, but none of the providers can be installed
- cannot install the best update candidate for package fence-agents-ibm-vpc-4.2.1-84.el8.noarch
- cannot install the best update candidate for package fence-agents-amt-ws-4.2.1-84.el8.noarch
Problem 3: problem with installed package fence-agents-ibm-vpc-4.2.1-84.el8.noarch
- package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed
- cannot install both fence-agents-common-4.2.1-85.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-4.2.1-85.el8.noarch requires fence-agents-common >= 4.2.1-85.el8, but none of the providers can be installed
- cannot install the best update candidate for package fence-agents-apc-4.2.1-84.el8.noarch
Problem 4: problem with installed package fence-agents-ibm-powervs-4.2.1-84.el8.noarch
- package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires fence-agents-common = 4.2.1-84.el8, but none of the providers can be installed
- cannot install both fence-agents-common-4.2.1-85.el8.noarch and fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-snmp-4.2.1-85.el8.noarch requires fence-agents-common >= 4.2.1-85.el8, but none of the providers can be installed
- cannot install the best update candidate for package fence-agents-apc-snmp-4.2.1-84.el8.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Expected results:
upgrade fence agents
Additional info:
looks like fence-agents 4.2.1-85 got released but misses the release for the subpackages fence-agents-ibm-powervs and fence-agents-ibm-vpc
checked on 2021-02-03 17:30 CET on mirror
http://ftp.fau.de/centos/8-stream/AppStream/x86_64/os/Packages/
Comment 1Oyvind Albrigtsen
2022-02-04 10:20:04 UTC
I'm looking into how to solve this.
In the meanwhile you should be able to upgrade after running "yum remove fence-agents-ibm-vpc". It'll remove the -all subpackage, which you can reinstall after upgrading.
My original problem was during an ovirt update which has a dependency tree
ovirt -> vdsm -> fence-agents-all
It will hit everyone trying to upgrade ovirt.
My workaround is masking -85 packages.
Comment 3Oyvind Albrigtsen
2022-02-07 15:11:59 UTC
You can run "rpm -q --nodeps fence-agents-ibm-vpc", and then upgrade. That way it will only remove that specific package, and if there was a dependency for it in the upgrade -all subpackage it would install it during the upgrade.
Comment 5RHEL Program Management
2023-08-03 07:28:35 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.