This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
Install yakkety in an Ubuntu KVM with two network interfaces.
Enabled yakkety-proposed, did apt full-upgrade.
Executed do-release-upgrade.
It upgraded to zesty, including zesty-proposed.
At the end of do-release-upgrade accepted to reboot.
After reboot, the system come up fine, with network
Hello Dimitri, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ * Upgrading s390x, kvm/qemu instances from yakkety to zesty results in a
change of network interface names (e.g. from eth0 to stable/predictable bus_id
name enc3, just like on z/VM and LPAR).
+ * This obviously results in loss of network connectivity as
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
