This bug was fixed in the package netplan.io - 1.0-1
---
netplan.io (1.0-1) unstable; urgency=medium
* New upstream release 1.0:
- state/status: add support for identifying bridge/bond/vrf members !420
- Netplan status --diff !440
- Netplan state diff !386
- allow CO
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in net
This patch seems to resolve the situation locally.
For now I'll only go with the changes to tests/integration/base.py,
though. As that should be enough to avoid test failures, while the
service units shouldn't change (besides being re-generated 1:1).
I want to better understand what's going on ex
This is related:
https://github.com/canonical/netplan/commit/da6f776dd7e33050124fe2990b715db92c1ddee3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite
The last two autopkgtest runs in the infrastructure are green despite
the trigger and they both show:
258s Unpacking wpasupplicant (2:2.10-21) ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.la
IMO the wpasupplicant trigger is a red herring, as we see the same
failure on a trigger=system/255... test case:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240104_111341_511f7@/log.gz
--
You received this bug notification because you are a member of Ubun
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status
** Merge proposal linked:
https://code.launchpad.net/~ogayot/britney/+git/britney/+merge/458822
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite oft
After further analysis, it looks like the trigger=wpa/2:2.10-21 highly
increases the likeliness 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 e
Added wpa as affected so this bug can show in the proposed migrations
report.
** Also affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
10 matches
Mail list logo
