Pruning assumes all oopses in the system will be referenced from a single project/project-group
Bug #1003627 reported by
James Westby
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Python OOPS Date-dir repository |
Fix Released
|
Low
|
Robert Collins | ||
| python-oops-tools |
Triaged
|
Low
|
Unassigned | ||
Bug Description
./bin/prune takes --project and --project-group as arguments that specify which LP
projects to check for oops references before deleting them.
If you have a multi-tenant oops server then you are likely to have references in
multiple projects, and putting all of those projects in one project group isn't going
to be practical.
Therefore it should be possible to specify the options multiple times, and for the
code to include all of the projects when looking for references.
Or perhaps it should just look across the whole of Launchpad, so that we don't have
to manually maintain a list of projects to check.
Thanks,
James
Revision history for this message
| James Westby (james-w) wrote | #1 |
| Changed in python-oops-datedir-repo: | |
| status: | New → Triaged |
| Changed in python-oops-tools: | |
| status: | New → Triaged |
| Changed in python-oops-datedir-repo: | |
| importance: | Undecided → Low |
| Changed in python-oops-tools: | |
| importance: | Undecided → Low |
| tags: | added: oops |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 1003627] Re: Pruning assumes all oopses in the system will be referenced from a single project/project-group | #2 |
| Changed in python-oops-datedir-repo: | |
| assignee: | nobody → Robert Collins (lifeless) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Adding datedir-repo as that is where the code to consult Launchpad lives, and so one of the
projects that will need to change.