Bug 2263869

Summary: AAP subscribed to a Capsule cannot pull subscription information from Satellite
Product: Red Hat Satellite Reporter: Ahmed Eladawy <aeladawy>
Component: Foreman ProxyAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: aruzicka, ehelms, rlavi
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
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: 2024-06-06 17:02:35 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:

Description Ahmed Eladawy 2024-02-12 13:49:25 UTC 
Description of problem:

As mentioned on the API Documentation :
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/api_guide/index#chap-Red_Hat_Satellite-API_Guide-Using_the_Red_Hat_Satellite_API

You can use the API on Satellite Server via HTTPS on port 443, or on Capsule Server via HTTPS on port 8443.

For the host that is subscribed to Satellite Server or Capsule Server, you can determine the correct port required to access the API from the /etc/rhsm/rhsm.conf file, in the port entry of the [server] section. You can use these values to fully automate your scripts, removing any need to verify which ports to use.

When registering a machine to the capsule , on [server] section the port is 443 which is used to connect to the capsule to obtain subscriptions by Ansible Automation Platform which results in an error :

No subscriptions found
POST api/v2/config/subscriptions/ 400
404 Client Error: Not Found for url: https://[Capsule]:443/katello/api/organizations

By checking the apache conf :

8443 simply forward what ever the request path to the Satellite as below:


  ## Proxy rules
  ProxyRequests Off
  ProxyPreserveHost Off
  ProxyPass / https://satellite.redhat.com/ disablereuse=on retry=0
  ProxyPassReverse / https://satellite.redhat.com/

But 443 only forward to certain paths to Satellite. For example: "/rhsm" path

  ## Proxy rules
  ProxyRequests Off
  ProxyPreserveHost Off
  ProxyPass /rhsm https://satellite.redhat.com/rhsm disablereuse=on retry=0
  ProxyPassReverse /rhsm https://satellite.redhat.com/rhsm
  ProxyPass /redhat_access https://satellite.redhat.com/redhat_access disablereuse=on retry=0
  ProxyPassReverse /redhat_access https://satellite.redhat.com/redhat_access

Therefore, the katello/api won't work in 443.


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

6.12
6.13
6.14

How reproducible:

100%

Steps to Reproduce:
1. Register a machine to the capsule.
2. Check the port under [server] section.
3. Try to register Ansible Automation Platform machine to the capsule and select subscriptions from the settings -> subscriptions

Actual results:

No subscriptions found
POST api/v2/config/subscriptions/ 400
404 Client Error: Not Found for url: https://[Capsule]:443/katello/api/organizations

Expected results:

To be able to obtain subscription.

Additional info:
Comment 1 Eric Helms 2024-02-15 16:23:38 UTC 
My initial thought is that there is something about your workflow that is different than our standard workflow, for example, I do not understand why your client machine is trying to access:

 * api/v2/config/subscriptions/
 * katello/api/organizations

Can you expand on this step: 

  3. Try to register Ansible Automation Platform machine to the capsule and select subscriptions from the settings -> subscriptions


This sounds like something AAP is doing that I am not aware of, and thus you may be the first use case attaching an AAP to a Capsule (rather than Satellite itself). Do you have more details or documentation reference that outlines this AAP configuration step?
Comment 2 Ahmed Eladawy 2024-02-16 12:51:15 UTC 
(In reply to Eric Helms from comment #1)
> My initial thought is that there is something about your workflow that is
> different than our standard workflow, for example, I do not understand why
> your client machine is trying to access:
> 
>  * api/v2/config/subscriptions/
>  * katello/api/organizations
> 
> Can you expand on this step: 
> 
>   3. Try to register Ansible Automation Platform machine to the capsule and
> select subscriptions from the settings -> subscriptions
> 
> 
> This sounds like something AAP is doing that I am not aware of, and thus you
> may be the first use case attaching an AAP to a Capsule (rather than
> Satellite itself). Do you have more details or documentation reference that
> outlines this AAP configuration step?

The client machine here is the Ansible Automation Platform (AAP) machine itself.

Available subscriptions or a subscription manifest authorize the use of the automation controller.To obtain your automation controller subscription, you can either:

1) Provide your Red Hat or Satellite username and password on the license page.
2) Obtain a subscriptions manifest from your Subscription Allocations page on the customer portal.

So, the AAP will use the information on rhsm.conf to reach the satellite/capsule to import the subscription :

https://docs.ansible.com/automation-controller/latest/html/quickstart/import_license.html

And as the AAP is registered to the capsule , not the satellite , it tries to reach the API of the capsule on port 443 as it is the port on rhsm.conf and in that case , the error occurs:

No subscriptions found
POST api/v2/config/subscriptions/ 400
404 Client Error: Not Found for url: https://[Capsule]:443/katello/api/organizations
Comment 4 Eric Helms 2024-06-06 17:02:35 UTC 
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 "SAT-" 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.