I have a very strange problem with the subscription-manager for ubuntu!
Setup:
orcharhino: 5.6
Client: ubuntu 18.04
subscription-manager for ubuntu from: acc-pub/atix.de/orcharhino_clients/Ubuntu18TLS version 1.25.1
Client registration works fine and afterwards I have all correct repostiories from my orcharhino server. I can do an apt-get update ; apt-get ugrade and so on … until I do ‘subbscription-manager refresh’
This command does refresh my cert/key files for all my repositories but does NOT update rhsm.sources with this new keys! The repository configs still point to the old cert files (sslclientcert/key entry).
After the refresh commando is no apt-get update etc possible any more (Error: Release
IOError: Could not find the TLS certificate file, invalid path: /etc/pki/entitlement/3382233428779671801.pem) … 3382233428779671801.pem was the OLD cert before the refresh command.
The only solution is, to delete rhsm.sources and redo “subscription-manager refresh”. Afterwards, all is fine again till the next refresh command
I suspect it’s rather got something to do with Katello and pulp/pulp_deb.
Can you please share which version you are using as well as a more percise error message?
The system @maximilian used for opensource.com is still using Pulp 2, while Katello 4.0 uses exclusively Pulp 3. The Katello 4.0.1 release will include a newer version of pulp_deb for Pulp 3 with several critical bugfixes. My best recommendation for now is to wait for Katello 4.0.1 and then try again. If you are still having issues then, please open a new thread posting your exact error.
First thanks for the great job that you are doing here
The weird thning is that :
-for repo “Debian 10 update” sync work but I have only 73 deb packages.
-for repo “Debian 10 main” sync is not working
-for repo “Debian 10 security” sync is not working
Right, you have several different issues here. I will answer one by one.
Regarding Debian updates:
This strikes me as correct/expected since “update” does not contain that many packages.
Regarding Debian 10 security:
This is not what is causing your error, but the way you entered your components won’t work. They need to be entered as a space separated list and not a comma separated list. It should be:
Components: main contrib non-free.
This is very unintuitive design on my part, since Pulp 2 needs comma separated and Pulp 3 needs space separated and they do not provide much sanity checking. I plan to fix this either at the Katello UI level, or the Katello sanity checking level, or else directly in pulp_deb at some point but for now one just needs to know it. There is already a Katello issue that mentions the need to address this: Feature #32514: Improve deb repo form regarding simple vs. structured publishing - Katello - Foreman
In addition to the components, your “Release:” input field needs to contain buster/updates not buster/update. The missing s is why Pulp can’t find the Release file and that is the error you are seing: No valid Release file found for 'buster/update'
Please fix your input and retest the sync.
Regarding Debian main:
Here, everything looks correct in your repository configuration (and indeed the sync has started downloading packages), but it fails to download a specific package because the Debian server is returning a “403 Forbidden”. I can manually download this package (http://ftp.de.debian.org/debian/pool/main/i/inetsim/inetsim_1.3.2+dfsg.1-1_all.deb) just fine, so maybe it is some weird network issue that is nothing to do with Pulp. Can you try simply re-running the sync and checking if it always fails with the same error, or if it is different each time you try?
@techietubby I am not getting the No valid Release file found for ‘buster/updates’. error for the combination of upstream URL: http://ftp.de.debian.org/debian-security/ and release/distribution: buster/updates.
I speculate you accidentally combined buster/updates with http://ftp.de.debian.org/debian/ instead of with http://ftp.de.debian.org/debian-security/. Can you confirm?
“Note that filtering by “releases” and “components” will generally eliminate entire errata, while filtering by “architectures” will simply result in errata that do not contain the binary packages of the architectures not filtered for.”
It’s not relevant to Katello, but it makes me think that maybe filters on debian security repo are not working with the current version of pulp_deb plugin (python3-pulp-deb-2.9.1-1.el7.noarch.rpm).
I have actually fixed the problem with the 0 packages from debian-security (the fix is available in the pulp_deb 2.13.0 release, but probably won’t be available within Katello for some time). The Problem was 100% the component. For debian-security the components are named updates/main in the Release file, instead of just main. As a result when you set Components: main in Katello (that is in the pulp remote), it does not find any components with that name and therefore does not sync anything but the metadata. You should be able to work around the problem by using Components: updates/main instead. The fixed version of pulp_deb will work with either entry (main as well as updates/main).