Bug 2230604
| Summary: | Cannot upgrade from maven:3.5 to maven:3.8 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Eric Helms <ehelms> |
| Component: | maven-3.8-module | Assignee: | Mikolaj Izdebski <mizdebsk> |
| Status: | CLOSED MIGRATED | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.8 | CC: | ahumbe, jverreng, tasano |
| Target Milestone: | rc | Keywords: | MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-20 15:03:56 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2127277 | ||
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: On a system that has been installed with default maven:3.5 module that gets enabled when installing either pki-servlet-engine or tomcatjss. For upgrades, we have to do a dnf module reset and then dnf module enable maven:3.8. That all works until you attempt to do a 'dnf upgrade' and the packages from maven:3.5 cannot upgrade to the packages in maven:3.8. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. dnf module enable pki-core pki-deps 2. dnf install pki-servlet-engine tomcatjss 3. dnf module reset maven 4. dnf module enable maven:3.8 5. dnf update Actual results: Problem: package slf4j-jdk14-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch requires mvn(org.slf4j:slf4j-api) = 1.7.25, but none of the providers can be installed - cannot install both slf4j-1.7.32-4.module+el8.8.0+18044+0a924b8f.noarch and slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch - cannot install both slf4j-1.7.32-4.module+el8.8.0+18044+0a924b8f.noarch and slf4j-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch - cannot install the best update candidate for package slf4j-jdk14-1.7.25-4.module_el8.4.0+595+e59c9af2.noarch - cannot install the best update candidate for package slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch - package slf4j-1.7.25-4.module_el8.0.0+39+6a9b6e22.noarch is filtered out by modular filtering - package slf4j-1.7.25-4.module_el8.6.0+1030+8d97e896.noarch 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: Package upgrade to succeed. Additional info: This is an annoyance for Satellite users as the maven:3.5 module is out of support and tools such as Insights flag out of support modules. The Satellite team would like to switch to relying on the maven:3.8 module that is still supported but have been unable to make the switch due to this issue.