Separate URL for repositories created for content views

Support
, , ,
1

Problem:
Separate URL for repositories created for content views. I created one content view which are having 2 repositories - Appstream and BaseOS

image
image1026×43 16.2 KB

Expected outcome:
When we give URL up to https:/myhostname.com/pulp/content/COT/Development/Mirror_AlmaLinux_8_Prod_Content_View/custom/Mirror_AlmaLinux_8/ we are getting 404 error. The expected output is to list Appstream and BaseOS.
Foreman and Proxy versions:
Latest

Distribution and version:
RHEL 8

Any help would be appreciated

2

When we give URL up to https:/myhostname.com/pulp/content/COT/Development/Mirror_AlmaLinux_8_Prod_Content_View/custom/Mirror_AlmaLinux_8/ we are getting 404 error.

But when we give

https:/myhostname.com/pulp/content/COT/Development/Mirror_AlmaLinux_8_Prod_Content_View/custom/Mirror_AlmaLinux_8/AppStream

and

https:/myhostname.com/pulp/content/COT/Development/Mirror_AlmaLinux_8_Prod_Content_View/custom/Mirror_AlmaLinux_8/BaseOS, we are getting the output. Is there any way to traverse one folder back and see both AppStream and BaseOS?

Any help would be appreciated

3

Can anyone look into this issue?

4

Hi,

Typically the workflow for clients is to be registered to the Katello instance with subscription-manager which populates the redhat repo with the url to the repos you are giving to the client and the certs so they can access the bits.

Is that workflow not working for you?

5

You can see everything at the pulp root:

https://foreman.example.com/pulp/content/

On a sidenote: unless you are owner of myhostname dot com please refrain from domain names registered to other people for obfuscation but revert to the reserved example domains example.com, example.net, example.org.