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 2021985 - [BUG] Upgrading Satellite 6.9 with custom certificates to Satellite 6.10 beta will cause the same problem to occur as BZ# 1961886
Summary: [BUG] Upgrading Satellite 6.9 with custom certificates to Satellite 6.10 beta...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: All
OS: All
high
high
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Omkar Khatavkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-10 14:01 UTC by Sayan Das
Modified: 2023-01-20 10:34 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2027817 (view as bug list)
Environment:
Last Closed: 2022-07-05 14:30:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6504131 0 None None None 2021-11-11 16:12:18 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:30:16 UTC

Description Sayan Das 2021-11-10 14:01:37 UTC 
Description of problem:

Upgrading Satellite 6.9 with custom certificates to Satellite 6.10 beta will cause the same problem to occur as described and fixed in Bugzilla 1961886 .

The issue is apparently fixed on a new installation of 6.10 beta but for upgraded Satellite, the issue persists.

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

Satellite 6.10 Beta


How reproducible:
100%

Steps to Reproduce:
1. Install Satellite 6.9 with custom certs

2. Import manifest, enable repos, sync them , register a client with satellite

3. Upgrade the satellite to 6.10 beta after performing pulp2 to pulp3 migration.

4. Run "yum clean all && yum repolist -v" on the client system.


Actual results:

Step 4 fails with error like:

https://satellite.example.com/pulp/repos/RedHat/Library/content/dist/rhel/server/7/7Server/x86_64/optional/os/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/solutions/69319

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.

https://satellite.example.com/pulp/repos/RedHat/Library/content/dist/rhel/server/7/7Server/x86_64/optional/os/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.


Expected results:


* No errors in yum post upgrade


* satellite-installer should be able to fix this on it's own during upgrade itself.


Additional info:

An easy fix is:

either to create a custom repo with "Publish Via HTTP" disabled 

or, to edit an existing custom repo to disable "Publish Via HTTP" and then re-enable the same.
Comment 2 Pavel Moravec 2021-11-10 21:42:37 UTC 
Worth to have KCS for this? If this wont be fixed in 6.10 GA, it would be hit by bunch of customers.
Comment 3 Sayan Das 2021-11-11 03:38:17 UTC 
(In reply to Pavel Moravec from comment #2)
> Worth to have KCS for this? If this wont be fixed in 6.10 GA, it would be
> hit by bunch of customers.

Yeah, I will be creating it within next 24 hours and attach with the BZ.
Comment 8 Omkar Khatavkar 2022-05-09 15:17:18 UTC 
Upgraded satellite 6.9 to 6.11 no issues found while satellite updated using custom certs. Repos are able to sync with clients working as expected.
Comment 11 errata-xmlrpc 2022-07-05 14:30:00 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.11 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-2022:5498
Note You need to log in before you can comment on or make changes to this bug.