403 forbidden on redhat repositories only

Support
21

thanks a lot

as my repo url is : https://katello.spb.lan/products/96/repositories/252
i tried so :

[root@katello ~]# hammer repository-set show --organization SPB --id 96
Could not find repository set resource with id 96. Potential missing permissions: view_products
[root@katello ~]#
[root@katello ~]#
[root@katello ~]# hammer repository-set show --organization SPB --id 252
Could not find repository set resource with id 252. Potential missing permissions: view_products

do you think it is normal ?
i received a 403 error forbidden and here it talks about missing permission
is there any link between them ?

thanks

22

The hammer command repository-sets is the equivalent to the GUI “Content” → “RedHat Repositories”, so since your RedHat Repos are created as custom products/repos and not via the “RedHat Repositories” feature, this is expected behaviour.

23

what it looks like so strange is that in his small doc he did that :

`hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='7Server'  --name 'Red Hat Enterprise Linux 7 Server (RPMs)'`

and

--RHEL 6
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='6Server'  --name 'Red Hat Enterprise Linux 6 Server - Extras (RPMs)'
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='6Server'  --name 'Red Hat Enterprise Linux 6 Server - Optional (RPMs)'
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='6Server'  --name 'Red Hat Enterprise Linux 6 Server (RPMs)'

--RHEL 7
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='7Server' --name 'Red Hat Enterprise Linux 7 Server - Optional (RPMs)'
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='7Server' --name 'Red Hat Enterprise Linux 7 Server - Extras RPMs x86_64'
hammer repository-set enable --organization "$ORG"  --product 'Red Hat Enterprise Linux Server'  --basearch='x86_64'  --releasever='7Server' --name 'Red Hat Enterprise Linux 7 Server (RPMs)'
24

at the beginning there is no RHEL 8 repos

25

If i would guess, I would say the doc you have there is out of date.
Your ex-coworker probably started with the supported/“correct” way, then had some problem that could not be solved that way (probably enabling plain HTTP access without client authentication), built everything back up with custom products to allow for whatever the reason was, and never update the docs.

26

i think so …
this is the past … :slight_smile:

i check the manifest file and in a first view i don’t find any certif but json files but i will concentrate my search around this
very thanks a lot for your help
it was so precious

i update of course the post if i can solve my issue

ludo

27

hi all,

aftera long time investigating i can now successfully sync my redhat repos !
i refresh my subscription in my katello server
i refresh my manifest in the UI
i export the 2 files from /etc/pki/entilement (certs and key) and import them in 2 new content credentials then applied it to the redhat repo product

now i have another issue that i already had before :

duplicate key value violates unique constraint "core_repositorycontent_repository_id_content_id_df902e11_uniq"
DETAIL:  Key (repository_id, content_id, version_removed_id)=(62b472c2-3418-449d-bbcb-3eb20132b93f, eb44d844-68d3-45bb-a10f-bf28a1fcb94b, 92c6cc27-376a-45ea-8beb-534bc21db6b4) already exists.

if anyone knows how to solve it it will be great !

very thanks a lot for your help
next month i will plan to migrate in 4 version :slight_smile:

thanks very thanks

ludo

28

hi
we found the solution in this article :

see you