Newly registered Python indexes are wrong
Closed this issue · 11 comments
Describe the bug
{
"url": "https://pulp.operate-first.cloud/https://pulp-api-5c5f4669d8-qgvvh/pypi/gym-donkeycar/simple"
},
{
"url": "https://pulp.operate-first.cloud/https://pulp-api-5c5f4669d8-qgvvh/pypi/test/simple"
},
{
"url": "https://pulp.operate-first.cloud/https://pulp-api-5c5f4669d8-qgvvh/pypi/hello-world/simple"
To Reproduce
Steps to reproduce the behavior:
- Go to stage environment
- Check registered Python indexes available on Pulp
- See the error
Expected behavior
Index URLs registered should be valid.
/priority critical-urgent
/assign @Gregory-Pereira
/triage accepted
/lifecycle active
Just to clarify by staging environment
, you mean where the job is actually running on OCP4 in thoth-frontend-prod
correct? At first I thought you were referring to a separate staging deployment of Pulp similar to https://pulp.operate-first.cloud.
Just to clarify by
staging environment
, you mean where the job is actually running on OCP4 inthoth-frontend-prod
correct?
I mean OCP4 deployment where the ingestion is done. It should be thoth-frontend-stage in OCP4.
Just to clarify by
staging environment
, you mean where the job is actually running on OCP4 inthoth-frontend-prod
correct?I mean OCP4 deployment where the ingestion is done. It should be thoth-frontend-stage in OCP4.
I mean, the deployment is OCP4 stage where the ingestion runs. The job itself runs in thoth-frontend-stage. Hope it clarifies and and sorry for the confusion.
Currently testing changes introduced in pull 36 on OCP4 thoth-frontend-stage. Ran without issues.
Currently testing changes introduced in pull 36 on OCP4 thoth-frontend-stage. Ran without issues.
The container succeeded, but I cannot see any indexes actually registered. There should be the donkeycar index present, but it is not listed in the /python-package-index
listing.
Got It, I haven't seen this job run before so thanks for sharing, I will look into it. Can you tell me where you were expecting to see that /python-package-index
so I can dig into it?
Got It, I haven't seen this job run before so thanks for sharing, I will look into it. Can you tell me where you were expecting to see that
/python-package-index
so I can dig into it?
I think it is due to pulp-pypi-sync-job not being updated in the stage (it was still running old code). I've tried to bump the image version, let's see. Thanks for digging into this 👍🏻
I can confirm the job registers indexes correctly. Thanks again for your time. 💯
Perfect, thanks for all the help Frido!