Possible to get migration-reference/0 result with proposed packages installed

[Sebastien Bacher]

It seems that sending a request with a migration-reference/0 trigger and all-proposed=1 will make the proposed pocket enabled, tricking the infra in thinking it tested against the release pocket when it didn't and letting wrongly a regression through

Example of a recent case which let webkitgtk migrate despite being broken on arm64
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/surf/20220307_225950_e5e88@/log.gz

https://git.launchpad.net/autopkgtest-cloud/commit/?id=8faf684741 was supposed to handle those cases but seems to not be enough, would https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker#n651 the right place to change?

[Julian Andres Klode (juliank)]

worker says:

INFO: Acknowledging request surf {"all-proposed": "1", "requester": "jbicha", "submit-time": "2022-03-07 21:52:03", "triggers": ["migration-reference/0"]}

So yes, ugh, something is broken

[Tim Andersson (andersson123)]

Merge proposal
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/452531

[Tim Andersson (andersson123)]

Fix has made it into master, and will be deployed soon.

[Tim Andersson (andersson123)]

This was deployed last week and I forgot to update the bug.