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.
Bug 2226946 - Upgrade fails to enable satellite module due to maven modules conflict
Summary: Upgrade fails to enable satellite module due to maven modules conflict
Keywords:
Status: CLOSED DUPLICATE of bug 2127277
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.14.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks: 2127277
TreeView+ depends on / blocked
 
Reported: 2023-07-27 05:55 UTC by Devendra Singh
Modified: 2023-07-27 13:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-27 13:15:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19207 0 None None None 2023-07-27 05:58:36 UTC

Description Devendra Singh 2023-07-27 05:55:50 UTC 
Description of problem: Satellite modules failed to resolve the maven conflict


Version-Release number of selected component (if applicable):
6.14.0 Snap9

How reproducible:
1/1

Steps to Reproduce:
1. Checkout the satellite base version of the 6.13.z
2. Prepare the setup for the 6.14.0 Snap9 satellite upgrade.
3. Run the upgrade from 6.13.z to 6.14.0 Snap9 
4. Upgrade failed in the "Running Migration scripts to Satellite 6.14" stage

Running Migration scripts to Satellite 6.14
================================================================================
Setup repositories:                                                   [33m[1m[SKIPPED][0m
--------------------------------------------------------------------------------
Enable the given stream modules:                                      [31m[1m[FAIL][0m
Failed executing dnf module enable satellite:el8 -y, exit status 1:
 Updating Subscription Management repositories.
Satellite 6.14 RHEL8                            243 kB/s | 3.0 kB     00:00    
Satellite Maintenance 6.14 RHEL8                202 kB/s | 2.6 kB     00:00    
Modular dependency problem:

 Problem: module satellite:el8:61420230726201710:a1d71636.x86_64 requires module(maven:3.8), but none of the providers can be installed
  - module maven:3.5:8060020220428102527:219351c9.x86_64 conflicts with module(maven:3.8) provided by maven:3.8:8080020230202141436:1e199b36.x86_64
  - module maven:3.8:8080020230202141436:1e199b36.x86_64 conflicts with module(maven:3.5) provided by maven:3.5:8060020220428102527:219351c9.x86_64
  - module maven:3.5:8060020220428102527:219351c9.x86_64 conflicts with module(maven:3.8) provided by maven:3.8:8070020220802090337:c806eb65.x86_64
  - module maven:3.8:8070020220802090337:c806eb65.x86_64 conflicts with module(maven:3.5) provided by maven:3.5:8060020220428102527:219351c9.x86_64
  - conflicting requests
Error: Problems in request:
Modular dependency problems:

 Problem: module satellite:el8:61420230726201710:a1d71636.x86_64 requires module(maven:3.8), but none of the providers can be installed
  - module maven:3.5:8060020220428102527:219351c9.x86_64 conflicts with module(maven:3.8) provided by maven:3.8:8080020230202141436:1e199b36.x86_64
  - module maven:3.8:8080020230202141436:1e199b36.x86_64 conflicts with module(maven:3.5) provided by maven:3.5:8060020220428102527:219351c9.x86_64
  - module maven:3.5:8060020220428102527:219351c9.x86_64 conflicts with module(maven:3.8) provided by maven:3.8:8070020220802090337:c806eb65.x86_64
  - module maven:3.8:8070020220802090337:c806eb65.x86_64 conflicts with module(maven:3.5) provided by maven:3.5:8060020220428102527:219351c9.x86_64
  - conflicting requests
--------------------------------------------------------------------------------
Scenario [Migration scripts to Satellite 6.14] failed.

Actual results: Satellite packages failed to resolve the maven conflict


Expected results:maven conflict should not happen


Additional info:
Comment 3 Lukas Pramuk 2023-07-27 08:18:23 UTC 
maven:3.5 gets enabled as a dependency of candlepin/tomcatjss

BZ 2127277 introduced usage of maven:3.8 instead however migration part is missing and needs to be delivered by foremn-maintain code
Comment 4 Eric Helms 2023-07-27 13:15:48 UTC 

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