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
Export artifact-dedup optimizations break pulp_rpm export. #4210
Comments
The QuerySet approach introduced a subtle bug the breaks pulp_rpm export. If we want to retain the 'good parts' of that approach, it will need to be its own investigation/PR. fixes pulp#4210.
The QuerySet approach introduced a subtle bug the breaks pulp_rpm export. If we want to retain the 'good parts' of that approach, it will need to be its own investigation/PR. fixes pulp#4210.
The specific test-failure that brought this to light was :
Artifacts needed by the ks-tree mentioned in the test were not exported correctly, and were therefore not being found at import-time. |
Do you know why the queryset approach was interfering? |
I do not. It may be some interaction with the sub-repos of distribution-trees and multiple-repos, that's the only sequence that fails. The current released behavior breaks the main-path workflow, and digging further into "why" was a lower priority than "make it work first". Replacing the approach with a set() means the current state of the attached PR is still significantly better than it has been for the past three years. Maybe we want to do some more investigation "eventually" - but "stopping the bleeding Right Now" is today's priority. |
The QuerySet approach introduced a subtle bug the breaks pulp_rpm export. If we want to retain the 'good parts' of that approach, it will need to be its own investigation/PR. fixes #4210.
Version
main, 18, 21, 22, 23, 28, 29
Describe the bug
After the changes for #4159 were released, pulp_rpm nightly tests started failing. This turns out to be the result of a subtle bug in the optimizations introduced for that fix.
This has to be fixed and released ASAP to all versions #4159 was releasxed into.
To Reproduce
The text was updated successfully, but these errors were encountered: