Bug 1963153
Summary: | Perl-libs conflict on UBI8/nodejs-{10,12,14} images | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Tony Garcia <antgarci> |
Component: | nodejs | Assignee: | Node.js maintainers <nodejs-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 8.4 | CC: | jplesnik, michael.bruenker, pkubat, ppisar, tmckay |
Target Milestone: | beta | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-26 14:55:01 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tony Garcia
2021-05-21 15:11:55 UTC
@jplesnik could you PTAL? Isn't it actually related to bug 1963049 reported against Perl? @pkubat FYI, that might affect all containers. 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 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? 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. 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. 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 *** This bug has been marked as a duplicate of bug 1963049 *** |