Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionJohan Bergström
2016-10-13 12:38:41 UTC
Description of problem:
Getting Protected multilib versions: libtasn1-3.8-3.el7.x86_64 != libtasn1-3.8-2.el7.i686 issues during upgrade of satellite 6.1.10 -> 6.2.2 due to missing libtasn1-i686 (3.8-3.el7) package in rhel-7-server-satellite-(and capsule)6.2-rpms repositories.
The x86_64 package is provided but not i686.
[root@capsule ~]# yum list libtasn1
Loaded plugins: aliases, changelog, package_upload, product-id, search-disabled-repos, subscription-manager, verify, versionlock
Installed Packages
libtasn1.i686 3.8-2.el7 @anaconda/7.1
libtasn1.x86_64 3.8-2.el7 @anaconda/7.1
Available Packages
libtasn1.x86_64 3.8-3.el7 rhel-7-server-satellite-capsule-6.2-rpms
Version-Release number of selected component (if applicable):
satellite 6.1.10 -> 6.2.2 upgrade.
How reproducible:
Every time.
Steps to Reproduce:
1. Install satellite 6.1.10 server, make sure you have libtasn1 packages, both i686 and x86_64 installed.
2. Enable rhel-7-server-satellite-6.2-rpms repo.
3. yum upgrade
Actual results:
[root@capsule ~]# yum upgrade
Loaded plugins: aliases, changelog, package_upload, product-id, search-disabled-repos, subscription-manager, verify, versionlock
rhel-7-server-rpms | 2.3 kB 00:00:00
rhel-7-server-satellite-capsule-6.2-rpms | 2.3 kB 00:00:00
Resolving Dependencies
--> Running transaction check
....dependency calculations
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for libtasn1 which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libtasn1 of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libtasn1.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libtasn1 installed, but
yum can only see an upgrade for one of those architectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of libtasn1 installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: libtasn1-3.8-3.el7.x86_64 != libtasn1-3.8-2.el7.i686
Expected results:
yum upgrade working
Additional info:
Workaround, using --setopt=protected_multilib=false works, but don't know if something will fail later on because I'm on different versions on x86_64/i686 libs now.
Thank you for your interest in Satellite 6. We have evaluated this feature request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: Getting Protected multilib versions: libtasn1-3.8-3.el7.x86_64 != libtasn1-3.8-2.el7.i686 issues during upgrade of satellite 6.1.10 -> 6.2.2 due to missing libtasn1-i686 (3.8-3.el7) package in rhel-7-server-satellite-(and capsule)6.2-rpms repositories. The x86_64 package is provided but not i686. [root@capsule ~]# yum list libtasn1 Loaded plugins: aliases, changelog, package_upload, product-id, search-disabled-repos, subscription-manager, verify, versionlock Installed Packages libtasn1.i686 3.8-2.el7 @anaconda/7.1 libtasn1.x86_64 3.8-2.el7 @anaconda/7.1 Available Packages libtasn1.x86_64 3.8-3.el7 rhel-7-server-satellite-capsule-6.2-rpms Version-Release number of selected component (if applicable): satellite 6.1.10 -> 6.2.2 upgrade. How reproducible: Every time. Steps to Reproduce: 1. Install satellite 6.1.10 server, make sure you have libtasn1 packages, both i686 and x86_64 installed. 2. Enable rhel-7-server-satellite-6.2-rpms repo. 3. yum upgrade Actual results: [root@capsule ~]# yum upgrade Loaded plugins: aliases, changelog, package_upload, product-id, search-disabled-repos, subscription-manager, verify, versionlock rhel-7-server-rpms | 2.3 kB 00:00:00 rhel-7-server-satellite-capsule-6.2-rpms | 2.3 kB 00:00:00 Resolving Dependencies --> Running transaction check ....dependency calculations --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for libtasn1 which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libtasn1 of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude libtasn1.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libtasn1 installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of libtasn1 installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: libtasn1-3.8-3.el7.x86_64 != libtasn1-3.8-2.el7.i686 Expected results: yum upgrade working Additional info: Workaround, using --setopt=protected_multilib=false works, but don't know if something will fail later on because I'm on different versions on x86_64/i686 libs now.