Public bug reported:
[Impact]
Sean Feole discovered that if you ifdown/ifup the NIC on an X-Gene 2 system,
the NIC does not come back online. While the interface is reported as up, you
cannot ping the system. In addition to the obvious problems this causes for a
sysadmin, it also breaks software that does this automatically, such as juju
when it sets up a host bridge.
[Test Case]
Boot an X-Gene 2 system, and start pinging it from a remote system. Assuming
the pinged interface is eth0, run:
$ sudo ifdown eth0; sudo ifup eth0
System will cease responding to pings.
[Regression Risk]
(Still under investigation)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722579
Title:
xgene nic unresponsive after ifdown/ifup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722579/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
