Unable to filter legacy tasks by --reserved-resource filter
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
pulpcore-3.63.1
pulp-rpm-3.27.2
pulp-container-2.22.0
Describe the bug
Following migration from pulpcore-3.49 to pulpcore-3.63, we are unable to filter legacy tasks (those created while running on 3.49) with --reserved-resource filter. Neither HREF or PRN argument works.
To Reproduce
- install pulpcore-3.49.22, pulp-rpm-3.26.1
- create some repos with remotes set to Red Hat CDN
- sync those repos
- filter tasks with --reserved-resources-record by supplying a sample repo HREF as the arg, SUCCESS!
- migrate to pulpcore-3.63.1, pulp-rpm-3.27.2 (Pulp migrations executed OK).
- filter tasks with --reserved-resources and the same arg, no match yielded, FAILURE
Expected behavior
The same result should be presented when using the same arg (provided as HREF) both prior and post Pulp migration. Alternatively, filtering by PRN with new Pulp core should yield the same result set as filtering by HREF in the old Pulp core. Another option would be to write an additional Pulp migration for reserved resources (so that the HREFs there are converted to PRNs), is that feasible? Dunno.
Additional context
Tasks themselves are migrated just fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the migration from pulpcore-3.49.22 to 3.63.1 using the reported repository sync steps. Compare --reserved-resources-record with --reserved-resources using the same repository HREF, then test the PRN form. Done means legacy tasks return the same expected result after migration, or the migration limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100