[Bug 1561096] Comment bridged from LTC Bugzilla

2017-02-13 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2017-02-13 19:37 EDT--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561096 Title: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-05-09 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2016-05-09 19:14 EDT--- State: Working by: furrer on 09 May 2016 17:50:45 #=#=# 2016-05-09 17:50:43 (CDT) #=#=# Action = [rejectfix] I have just installed a fresh install of Ubuntu 16.04 on br16p05.aus.stglabs.ibm.com and followed the setup f

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-18 Thread bugproxy
--- Comment From ru...@us.ibm.com 2016-04-18 10:09 EDT--- FYI: This change was indirectly validated via IBM bug 140408 (we forgot to warn some of the other test teams). ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-12 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2016-04-12 08:58 EDT--- As it's quite horrible to take apart the devpath number (like 71000102) in shell, and it's not entirely clear how that number is built up (i. e. how many digits are the bus number, and how many are the slot ID), would it be poss

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-11 Thread bugproxy
--- Comment From bjki...@us.ibm.com 2016-04-11 16:27 EDT--- It really seems like the right fix here might be to enhance the code generating the location name to better handle ibmveth. If we look at the information below: P: /devices/vio/3002/net/eth1 E: DEVPATH=/devices/vio/3002/n

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-08 Thread bugproxy
--- Comment From prad...@us.ibm.com 2016-04-08 14:24 EDT--- (In reply to comment #23) > > the ideal solution due to the consistency of behavior with the older > > releases > > Just a note: it will behave completely differently to any other network > interface, though, so it's still not con

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-08 Thread bugproxy
--- Comment From ru...@us.ibm.com 2016-04-08 11:53 EDT--- I hate to cause extra work, but a return to the old persistent-net-generator behavior for the ibmveth devices would be the ideal solution due to the consistency of behavior with the older releases. It is what the users are used t

[Bug 1561096] Comment bridged from LTC Bugzilla

2016-04-05 Thread bugproxy
--- Comment From ru...@us.ibm.com 2016-04-05 10:26 EDT--- (In reply to comment #16) > > This creates a name-slip problem for these ibmveth devices depending on the > > timing of other devices (where another NIC will temporarily be assigned a > > name like eth0 before it is renamed by udev