-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing content checksums list results in errors and crashloopbackoff #1344
Comments
It all started with attempt to pull content from remote https://repo.mongodb.org/yum/redhat/9/mongodb-org/6.0/x86_64/RPMS/ When attempting to sync repo from that remote:
As adding sha1 fails as described above. |
Hi, @vkukk Thank you for keep providing detailed issue descriptions!
which, as you mentioned, failed because of the forbidden sha1 checksum.
which deployed the checksum job and redeployed pulpcore pods, but they all ran fine. As a second test, I created a new namespace, did another installation of Pulp, and, this time, I tried to first sync a sample RPM repo from pulp:
after that I tried to sync mongo repo (the same way I did before), which failed with the forbidden sha1 checksum again, and when I updated pulp CR I could see the same errors (I'll investigate them later) as you provided in the checksum jobs (for some reason it deployed 2 jobs, I'll also investigate this later), but the redeployed pulpcore (api/content/worker) pods started without errors and re-triggering the sync task worked. With that being said, do you remember to sync any other repo (before trying to sync mongo repo) or to do something else? Would you mind checking if this command fixes the error?
|
I have managed to reproduce it. When I initially created mongo repo, it had At start:
Check what is available at https://pulp3.tld/pulp/content/mongo-6/tst/Packages/m/ Decide to remove package version limitation.
Now change pulp CR config. Considering that sha256 is default and sync error was about sha1 being forbidden, add sha1 to allowed list.
Now apply updates to Pulp
Watch how pulp-update-content checksums jobs fail.
pulp-api pods crash with:
Running suggested command manually:
Yet when I delete now some pod in crashloop, it will continue crashing:
|
Can you try the command again with reporting enabled: |
Version
Please provide the versions of the pulp-operator and pulp images in use.
Describe the bug
Added section to config:
Applied changes to Pulp deployment and all api, content and workers are crashing.
Expected behavior
Pulp would work and accept listed content checksums.
Additional context
Job to update content checksums is failing
The text was updated successfully, but these errors were encountered: