Red Hat Bugzilla – Bug 800551
thumbslug returns 403
Last modified: 2016-11-30 19:56:52 EST
Created attachment 568016 [details]
Description of problem:
After successfull registration to SAM, i can not install package.
Version-Release number of selected component (if applicable):
2012-03-02.1 / x86_64
Steps to Reproduce:
1. install SAM with yum -y instsall katello-headpin-all
2. configure headpin with katello-configure --deployment=headpin
3. import manifest file (attached)
4. configure some system to use this SAM with subscription-manager config ...
5. register the system with subscription-manager register
6. autosubscribe the system with subscription-manager subscribe --auto
7. try to install package with yum install nmap
[root@qb-sam ~]# yum install nmap
Loaded plugins: product-id, security, subscription-manager
Updating certificate-based repositories.
https://ibm-ls21-02.rhts.eng.rdu.redhat.com:8088/content/dist/rhel/server/6/6Server/x86_64/cf-tools/1.0/os/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 403"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-6-server-cf-tools-1-rpms. Please verify its path and try again
Package has been installed.
Particular thumbslug logs attached
Well, I thought it could be problem with the manifest file. So I checked the management at https://access.redhat.com/management and I discovered that the SAM organization, whose manifest file I use had got no subscriptions any more. (I am not asking why..)
So I added some subscriptions to that organization and downloaded new manifest.
But after the import of this new manifest into the SAM (and reregistration of the guest) I still had the 403 problem.
This is probably because SAM still used the broken subscriptions of the previous manifest file (probably until they are all used).
So I need to be able to disable or throw away anyhow the broken subscriptions in SAM. Or the SAM should even verify the certificate before it provides it to the guest...
In my situation it helped to reinstall the SAM and use only the new manifest, which is definitely not the ideal way to solve such problems..
Closing this bug as NOTABUG, because it is a different issue regarding to the original report. I'll find more information and consider reporting new bug.