[Bug 1561096] Comment bridged from LTC Bugzilla
bugproxy
bugproxy at us.ibm.com
Mon May 9 23:21:30 UTC 2016
------- Comment From cdeadmin at 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 from the WIKI to use
"eth0" as its network access. I completed the install and it was
working as desired.
I then added two adapters to the partitions' configuration using the HMC
GUI under I/O to add "As Desired" to the partition, a Mason adapter at
location FHZ0145-P2-C6 and a Travis_EN adapter at location
CSS00HL-P1-C5. I then rebooted the partition to activate both adapters
in prep for an attempt at two TER completions.
I attempted to run "build_net help" to set up the network but when I ran
the command, it appeared to hang. I exited the instance and checked the
state of the network access by running the command "mount
iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock" to make
sure the test/tools directory was mounted. The command returned:
(0) root @ br16p05: /root
# mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock
mount.nfs: Failed to resolve server iofnim.aus.stglabs.ibm.com: Temporary failure in name resolution
I then checked the /etc/network/interfaces file I had modified for
network access for the Ubuntu 16.04 according to the WIKI via .ISO and
it is set up as it was when I originally set up the fresh install.
Thinking the interface may have an issue, I ran "ifdown eth0" and it
returned:
(0) root @ br16p05: /root
# ifdown eth0
ifdown: interface eth0 not configured
To double-check there is more at play here, I also ran "ifup eth0" just
to see what it returned:
(0) root @ br16p05: /root
# ifup eth0
Cannot find device "eth0"
Failed to bring up eth0.
As the setup for eth0 DOES exist in /etc/network/interfaces, I ran
"ifconfig -a" to view the existing interfaces and it returned this:
(0) root @ br16p05: /root
# ifconfig -a
enP1p160s0f0 Link encap:Ethernet HWaddr 00:c0:dd:10:1d:c4
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:256
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:249
enP1p160s0f1 Link encap:Ethernet HWaddr 00:c0:dd:10:1d:c6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:256
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:250
enp1s0 Link encap:Ethernet HWaddr e4:1d:2d:54:70:82
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
enp1s0d1 Link encap:Ethernet HWaddr e4:1d:2d:54:70:83
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ibmveth2 Link encap:Ethernet HWaddr 46:de:e7:23:26:02
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
As the first four interfaces appear in the naming convention for past
instances of network adapters in Linux, the only one left (with the
exception of "lo" is "ibmveth2" which is not set up either but appears
to show a similar issue of the original defect where the name "eth0" is
being replaced by something else that is subsequently not set up.
I will attempt to modify /etc/network/interfaces for "ibmveth2" after
copying the original interfaces file to /etc/network/interfaces.old,
reboot the partition and see if that will allow network access in case a
developer would like to look at the fresh install overnight.
NOTE: The modification to set up "ibmveth2" in /etc/network/interfaces
appeared to work after rebooting the partition but I am unable to ssh or
telnet into the partition from an LCB as I get these returns:
$ ssh root at 9.3.137.40
root at 9.3.137.40's password:
Received disconnect from 9.3.137.40: 2: Invalid ssh2 packet type: 192
$ telnet 9.3.137.40
Trying 9.3.137.40...
telnet: connect to address 9.3.137.40: Connection refused
Please advise.
#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1561096
Title:
STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under
Ubuntu 16.04 with added adapters (ibmveth)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Bug description:
Problem Description : I had installed a fresh install of Ubuntu 16.04
from an ISO image and had set up the partition as directed in the
Wiki. I had set up the networking as directed in the WIKI and was able
to ping "iofnim" and was able to perform updates and upgrades to the
Ubuntu installation without issue.
I had checked to make sure (by adding them to an existing AIX
partition) that the Mason and Travis_EN adapters to be added were at
the latest microcode levels. I assigned them to the partition to be
used (br16p05) and then shut down the partition and restarted it to
allow the partition to activate the adapters.
After the partition restarted, I attempted to build the network using
build_net and during its run noticed that the output for the adapters
was returning "Network is unreachable". After it completed, I
attempted to mount iofnim using the command:
"mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock"
which returned a "Failed" error message.
I then ran "ifconfig -a" to check on the state of the network which
had been working until I rebooted the partition after adding the
adapters.
I found the unconventional names for both the Mason and the Travis_EN
adapters contained in the output from "ifconfig -a" but also found
that "eth0", with which I had originally set up the network access for
the partition during setupp, was no longer listed but instead "eth1"
was now listed and none of the networking data including IP's reported
from "ifconfig -a" were set.
I consulted with Thiru and he asked I write it up and include a tar
file created from /var/log which I have attached to the defect.
As an additional note, I was able to go back into
/etc/network/interfaces and modify the settings for "eth0" to now be
set to "eth1" and after bringing the port down and back up, was able
to again ping out and access the network.
Please advise.
== Comment: #7 - Kevin W. Rudd - 2016-02-11 12:32:49 ==
Thank you for the additional info. This is not quite the same as the bug I referenced earlier. It is actually a match for bug 122308 .
Canonical:
This is the same basic issue as originally worked in LP Bug 1437375
The ibmveth based devices are not associated with PCI bus locations,
and still rely on the legacy eth? naming. The problem here is that
the 75-persistent-net-generator.rules file that used to set up the 70
-persistent-net.rules file for these devices has been removed in 16.04
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).
Please add back persistent-net-generator support for non-PCI-based
devices like this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561096/+subscriptions
More information about the foundations-bugs
mailing list