Updating SIAB when deleting a track from SCA admin
Bug #1802356 reported by
Adam Collard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Software Center Agent |
Fix Released
|
High
|
Facundo Batista |
Bug Description
When deleting tracks from SCA's admin interface, we should make sure that SIAB is updated properly.
as per Natalia:
The right thing would be:
1- check that no revision is released to the track being removed, fail if yes;
2- on track delete update snaprevs by cleaning up the entries
Changed in software-center-agent: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in software-center-agent: | |
assignee: | nobody → Facundo Batista (facundo) |
Changed in software-center-agent: | |
status: | Triaged → In Progress |
Changed in software-center-agent: | |
status: | In Progress → Fix Committed |
Changed in software-center-agent: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As discussed on IRC, we won't erase the history from snaprevs (neither by removing the rows or setting their revoked flag). Instead we'll act like the channels are closed and set the most recent entries to deleted, which should be easily done using a full channelmap push with delete_omitted.
This will prevent installations but not e.g. upgrades through epochs. If we do desire full history erasure we can set revoked on a case by case basis, and if it becomes common we can look at automating it once the new SCA->snaprevs API is done (likely next cycle).