Re: [Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-12 Thread Dimitri John Ledkov 
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 networking, as
interfaces cannot have multiple names (unlike e.g. hard drives which
can have backwards compatible symlinks).

I'm not even sure yet, if I should be writing more code to e.g.
automatically transform /etc/networking/interfaces with new interface
names.

-- 
Regards,

Dimitri.

-- 
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

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-12 Thread Frank Heimes 
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, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1679674

Title:
  s390x: Interface order in kvm guest image not predictable

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-12 Thread Andreas Scheuring 
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 order in kvm guest image not predictable

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-11 Thread Dimitri John Ledkov 
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
and z/VM. Specifically interfaces names are renamed into: enc2 and enc3
for my xml of the guest, which corresponds to the devno in the xml
definition:

   
  
  
  
  
  
  


  
  
  
  
  
  


I am marking this bug as fix released.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-10 Thread Dimitri John Ledkov 
** 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 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

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

2017-04-05 Thread Kevin W. Rudd 
** 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

Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp