On 12 April 2017 at 07:58, Andreas Scheuring
wrote:
> Thanks for this fix. It's solved in 17.04, but won't be backported to
> 16.04. Is that right?
Correct, no backport to 16.04 as is as of now. This is a backwards
incompatible change which can break existing VMs
Yes, that is the current plan.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Tags added: s390x
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks for this fix. It's solved in 17.04, but won't be backported to
16.04. Is that right?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1679674
Title:
s390x: Interface
This change got uploaded into ubuntu on 2017-03-28, before this bug
report was filed, but due to various regressions was not published until
2017-04-08.
With most current Ubuntu 17.04, and 232-21ubuntu2 stable interface names
are used for virtio_net defices based on the bus IDs just like on LPAR
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.04
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1679674
Title:
s390x: Interface order in kvm guest image not predictable
6 matches
Mail list logo