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.
Bug 1963153 - Perl-libs conflict on UBI8/nodejs-{10,12,14} images
Summary: Perl-libs conflict on UBI8/nodejs-{10,12,14} images
Keywords:
Status: CLOSED DUPLICATE of bug 1963049
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nodejs
Version: 8.4
Hardware: All
OS: All
urgent
high
Target Milestone: beta
: ---
Assignee: Node.js maintainers
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-21 15:11 UTC by Tony Garcia
Modified: 2021-05-26 14:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-26 14:55:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tony Garcia 2021-05-21 15:11:55 UTC 
Description of problem:
UBI8/nodejs-{10,12,14} images are unable to be updated.

Running 'dnf update' within each image will generate an error stating perl-libs module and perl-libs are conflicting.

Version-Release number of selected component (if applicable):
nodejs-10, 12 and 14 on ubi8

How reproducible:
Pull the image from registry.access.redhat.com and call a shell. Run 'dnf update' from within the container.

Steps to Reproduce:
1.podman run -it --user root registry.access.redhat.com/ubi8/nodejs-14 /bin/bash (the customer was able to reproduce w/ 'docker run' on osx)
2.run 'dnf update'

Actual results:
bash-4.4# dnf update
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

Red Hat Universal Base Image 8 (RPMs) - BaseOS                                                                                                                3.0 MB/s | 785 kB     00:00    
Red Hat Universal Base Image 8 (RPMs) - AppStream                                                                                                              43 MB/s | 7.4 MB     00:00    
Red Hat Universal Base Image 8 (RPMs) - CodeReady Builder                                                                                                     189 kB/s |  15 kB     00:00    
Error: 
 Problem 1: package perl-threads-1:2.21-2.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-417.el8_3.x86_64
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-419.el8.x86_64
  - cannot install the best update candidate for package perl-threads-1:2.21-2.el8.x86_64
  - cannot install the best update candidate for package perl-libs-4:5.26.3-417.el8_3.x86_64
 Problem 2: package perl-threads-shared-1.58-2.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-417.el8_3.x86_64
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-419.el8.x86_64
  - package perl-Errno-1.30-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-threads-shared-1.58-2.el8.x86_64
  - cannot install the best update candidate for package perl-Errno-1.28-417.el8_3.x86_64
  - package perl-libs-4:5.30.1-452.module+el8.4.0+8990+01326e37.x86_64 is filtered out by modular filtering
 Problem 3: package perl-Unicode-Normalize-1.25-396.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-417.el8_3.x86_64
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-419.el8.x86_64
  - package perl-IO-1.40-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-IO-1.40-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires libperl.so.5.30()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Unicode-Normalize-1.25-396.el8.x86_64
  - cannot install the best update candidate for package perl-IO-1.38-417.el8_3.x86_64
  - package perl-libs-4:5.30.1-452.module+el8.4.0+8990+01326e37.x86_64 is filtered out by modular filtering
 Problem 4: package perl-TermReadKey-2.37-7.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-417.el8_3.x86_64
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-419.el8.x86_64
  - package perl-interpreter-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-interpreter-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires libperl.so.5.30()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package perl-interpreter-4:5.26.3-417.el8_3.x86_64
  - cannot install the best update candidate for package perl-TermReadKey-2.37-7.el8.x86_64
  - package perl-libs-4:5.30.1-452.module+el8.4.0+8990+01326e37.x86_64 is filtered out by modular filtering
 Problem 5: package perl-Storable-1:3.11-3.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-417.el8_3.x86_64
  - cannot install both perl-libs-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 and perl-libs-4:5.26.3-419.el8.x86_64
  - package perl-macros-4:5.30.1-451.module+el8.3.0+6961+31ca2e7a.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-macros-4:5.26.3-417.el8_3.x86_64
  - cannot install the best update candidate for package perl-Storable-1:3.11-3.el8.x86_64
  - package perl-libs-4:5.30.1-452.module+el8.4.0+8990+01326e37.x86_64 is filtered out by modular filtering
(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:
'dnf update' command completes successfully

Additional info:
Comment 1 Vít Ondruch 2021-05-21 17:01:29 UTC 
@jplesnik could you PTAL?
Comment 2 Vít Ondruch 2021-05-21 17:30:24 UTC 
Isn't it actually related to bug 1963049 reported against Perl?
Comment 3 Vít Ondruch 2021-05-21 17:31:27 UTC 
@pkubat FYI, that might affect all containers.
Comment 4 Jitka Plesnikova 2021-05-21 18:40:04 UTC 
I am not sure if it is a problem of perl.

By default, the module perl:5.26 is enabled, so I don't understand why dnf uses packages from perl:5.30.

# dnf module list perl
perl            5.26 [d][e]       common [d], minimal    Practical Extraction and Report Language                                 
perl            5.30              common [d], minimal    Practical Extraction and Report Language
Comment 5 Tony Garcia 2021-05-21 20:28:48 UTC 
Hi folks,

I wanted to mention something that may or may not be related. Prior to reporting this issue, the customer experienced the same problem w/ UBI8 and gcc packages. Support confirmed there was a metadata issue on cdn-ubi yesterday and once the metadata was fixed, the gcc package errors went away.

Could there be a metadata issue w/ perl as well?
Comment 6 michael.bruenker 2021-05-21 21:26:02 UTC 
Hello,
just wanted to mention that the exact same issue exists with ubi8/openjdk Images. Workaround is to add --nobest to the microdnf update, but this doesn't solve the root cause of course.
Comment 10 Petr Kubat 2021-05-25 07:21:16 UTC 
Thanks for the heads-up Vit. I am already seeing some reports for other images so makes sense this is not container image related, but rather UBI repository related.
Comment 11 Trevor McKay 2021-05-26 12:08:37 UTC 
We have this problem in a related image (ubi8/python-38), confirming the use of --nobest as suggested in the error is a workaround for us
Comment 12 Petr Pisar 2021-05-26 14:55:01 UTC 

*** This bug has been marked as a duplicate of bug 1963049 ***
Note You need to log in before you can comment on or make changes to this bug.