#247: upgradepath: possible broken-updates scenario for new packages --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Component: tests | Keywords: --------------------+------------------------------------------------------- Here is a scenario that will create broken upgrade path and our current tests will not catch it:
1. Package foo is available for F12 (foo-1.0-1.fc12), but not for F13. 2. foo-1.0-1.fc13 is sent to f13-updates-pending as a new package update. upgradepath passes. 3. foo-2.0-1.fc12 is sent to f12-updates-pending. Since there is still no foo in F13 (AutoQA passed but it has not been pushed by RelEng team), upgradepath passes. 4. foo-2.0-1.fc12 is pushed to f12-updates. 5. foo-1.0-1.fc13 is pushed to f13-updates. 6. Broken upgrade path.
What can we do about it?
We can break the scenario between steps 4 and 5. But we can't probably do that just by watching -pending tags. This requires cooperation from the updates manager (i.e. Bodhi). Bodhi must know that if some foo build enters f12-updates, and there is also another foo build in f13-updates- pending, it must notify us (over Fedora Message Bus) and ask us to retest the latter build.
We can also break the scenario between steps 2 and 3. When we run upgradepath on foo in f12-updates-pending, we can take into account not just f13-updates, but also f13-updates-pending. But this is quite controversial. Some builds in -updates-pending may be denied by RelEng team, but we could have failed some other builds because of them.
We will probably solve this ticket only when we have advanced infrastructure ready (ResultDB, Fedora Message Bus). Without it this seems pretty hard to be solved properly.
#247: upgradepath: possible broken-updates scenario for new packages --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Component: tests | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by jlaska):
Replying to [ticket:247 kparal]:
We will probably solve this ticket only when we have advanced
infrastructure ready (ResultDB, Fedora Message Bus). Without it this seems pretty hard to be solved properly.
Agreed. It might be handy for future reference to pull out some sample failures that fit the description from autoqa- results@lists.fedorahosted.org. That would also help highlight the frequency of this issue.
#247: upgradepath: possible broken-updates scenario for new packages --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: minor | Milestone: Future tasks Component: tests | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by kparal):
* priority: major => minor * milestone: => Future tasks
autoqa-devel@lists.fedorahosted.org