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 2114011 - Provisioning a host on N-1 Satellite 6.10 and Capsule 6.9 fails due to path change from `repos` to `content`
Summary: Provisioning a host on N-1 Satellite 6.10 and Capsule 6.9 fails due to path c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.10.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-02 14:50 UTC by Jaroslav Krajicek
Modified: 2023-06-14 09:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-14 09:05:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-17340 0 None None None 2023-04-26 21:33:55 UTC

Description Jaroslav Krajicek 2022-08-02 14:50:28 UTC 
Description of problem:
 - Satellite 6.9 with Capsule 6.9
 - After upgrading Satellite 6.9 to 6.10, provisioning a host through the 6.9 (N-1) Capsule fails due to differing HTTP path for content.
 - Capsule serves content at http://capsule.example.com/pulp/repos while Satellite (and the template) at http://satellite.example.com/pulp/content

Version-Release number of selected component (if applicable):
 Satellite 6.10.7, Capsule 6.9.9

How reproducible:
 100%, Library environment

Steps to Reproduce:
1. Fresh Satellite 6.9 + Caspule 6.9, incl. provisioning setup
2. Synchronize Kickstart and RHEL repository on Satellite
3. Synchronize repositories to Capsule
4. Upgrade Satellite to 6.10
5. Try to provision a host through the Capsule

Actual results:
Host being provisioned fails to fetch the squashfs.img
~~~
dracut-initqueue[733]: curl: (22) The requested URL returned error: 404 Not Found
~~~

Expected results:
Provosioning goes through without any issues, and the template renders depending on the capsule providing the actual content.

Additional info:
Workaround needed. Replacing the string works, but needs to be manually selected depending on the Satellite/Capsule used for provisioning.
~~~
<%= "#{@host.url_for_boot(:kernel).gsub('pulp/content', 'pulp/repos')}" %>
~~~
Comment 4 Adam Ruzicka 2023-05-05 14:09:15 UTC 
This issue can occur only in one specific scenario - when one has 6.10 Satellite and 6.9 capsules. No other scenarios (matching versions, N satellite and N-1 capsules for N >= 6.11) should be affected by this.

In general I'd recommend upgrading the capsules to 6.10 and, if possible, upgrading Satellite to 6.11, especially considering that 6.10 will go EOL at the end of the month.
Comment 6 Adam Ruzicka 2023-06-14 09:05:55 UTC 
Satellite 6.10 went EOL on May 31, 2023 and took this bug with it. Per #4, the issue shouldn't happen anymore with any combination of currently supported versions so I'll go ahead and close this. If you manage to trigger the bug again on currently supported versions, feel free to reopen.
Note You need to log in before you can comment on or make changes to this bug.