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 1844344 - Why "satellite-capsule" package exists under satellite repository
Summary: Why "satellite-capsule" package exists under satellite repository
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.9.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-05 07:24 UTC by Kavita
Modified: 2021-04-21 13:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:14:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:17:14 UTC

Description Kavita 2020-06-05 07:24:41 UTC 
Description of problem:

Foreman Maintain relies on the satellite-capsule package to identify capsule environments. 
With the new capsule upgrade scenario in foreman-maintain, it fails to decide which upgrade scenario to run when both satellite and satellite-capsule packages are installed on the server.

Failure -
Satellite upgrade job failed due to "Too many scenarios match {:tags=>[:upgrade_scenario, :pre_upgrade_checks]}" error

I would like to know insights why this package exists on Satellite? Can we remove this package to avoid conflicts?

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
satellite-capsule package exists on satellite

Expected results:
satellite-capsule package should not exist on satellite. 

Additional info:

Foreman Maintain side BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1838382
Comment 1 Evgeni Golov 2020-07-08 12:28:16 UTC 
So I don't see a *good* reason why this package should be shipped in the *Satellite* repositories. All it contains are dependencies that are needed on a pure Capsule. This has been the case since at least Satellite 6.2 -- I couldn't find older sources.

Adding NEEDINFO on Mike, he *might* have some historical knowledge ;-)

Either way, I think the fix you applied in BZ#1844344 is correct and should make foreman-maintain work correctly.

Now, we certainly can remove that package from the Satellite repositories (build team: needs comps change and an Obsoletes in the main satellite package, so that it gets removed from customer systems if it's installed now), but I don't think this BZ should block beta as there is nothing broken by it anymore? :)
Comment 2 Kavita 2020-07-13 08:51:34 UTC 
(In reply to Evgeni Golov from comment #1)

> Either way, I think the fix you applied in BZ#1844344 is correct and should
> make foreman-maintain work correctly.
> 

Yes, with the fix for BZ#1844344 foreman-maintain is detecting upgrade scenario properly based on satellite or capsule server instead of giving a failure mentioned in the description. 

This is no longer blocker for foreman-maintain. But if this package is not required on satellite server then probably it should be removed.

Thanks!
Kavita
Comment 3 Kavita 2020-07-13 08:54:55 UTC 
Sorry(In reply to Kavita from comment #2)
> (In reply to Evgeni Golov from comment #1)
> 
> > Either way, I think the fix you applied in BZ#1844344 is correct and should
> > make foreman-maintain work correctly.
> > 
> 
> Yes, with the fix for *BZ#1838382* foreman-maintain is detecting upgrade
> scenario properly based on satellite or capsule server instead of giving a
> failure mentioned in the description. 
> 
> This is no longer blocker for foreman-maintain. But if this package is not
> required on satellite server then probably it should be removed.
> 
> Thanks!
> Kavita
Comment 6 Lukas Pramuk 2021-03-10 09:53:20 UTC 
VERIFIED.

@Satellite 6.9.0 Snap16

by the following steps:

# rpm -q satellite{,-capsule}
satellite-6.9.0-1.el7sat.noarch
package satellite-capsule is not installed

# yum --disableplugin=foreman-protector list satellite-capsule --showd
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Error: No matching Packages to list

>>> satellite-capsule rpm is no longer present in Satellite repo
Comment 9 errata-xmlrpc 2021-04-21 13:14:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313
Note You need to log in before you can comment on or make changes to this bug.