Comment 5 for bug 2048388

After further analysis, it looks like the trigger=wpa/2:2.10-21 highly increases the likelihood of the error to occur.

At this point, I do not think that there is any regression in wpa 2:2.10-21 compared to 2:2.10-20. The changeset is minimal. OTOH I think the trigger=wpa/... alters the order of events and somehow consequently makes the race condition more likely to occur.

FWIW, with a trigger=wpa/..., wpasupplicant gets upgraded before running the ethernets test:

 96s Unpacking wpasupplicant (2:2.10-21) over (2:2.10-20) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-proposed//noble/s390x/n/netplan.io/20240109_171235_03058@/log.gz

Whereas. without the trigger, it gets installed:

127s Unpacking wpasupplicant (2:2.10-21) ...

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ogayot-noble-proposed//noble/s390x/n/netplan.io/20240109_162248_f656d@/log.gz