This bug has not seen any activity in the last 6 months, so it is being
automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team
** Changed in: maas
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
** Changed in: ifupdown (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesyste
** Changed in: maas
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To manage
This bug was fixed in the package ifupdown - 0.8.10ubuntu1.2
---
ifupdown (0.8.10ubuntu1.2) xenial; urgency=medium
* networking.service: exclude loopback device lo in ExecStop (LP: #1629972)
This prevents the stop of networking.service from taking down the
loopback 'lo' inte
Verification was done by using MAAS to enlist, commission, and deploy
xenial (with the fix) on a machine. Previously, it failed to shut down,
because the root disk got unmounted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesys
Hello LaMont, or anyone else affected,
Accepted ifupdown into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.10ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
This is tangled up into the MAAS IPv6 SRU happening in bug 1621507.
Please check that bug for verification-done before accepting ifupdown
into xenial-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
This bug was fixed in the package ifupdown - 0.8.13ubuntu3
---
ifupdown (0.8.13ubuntu3) yakkety-proposed; urgency=medium
* networking.service: exclude loopback device lo in ExecStop (LP:
#1629972)
-- Scott Moser Fri, 14 Oct 2016 13:53:32 -0400
** Changed in: ifupdown (Ubuntu Ya
I've adjusted the description, including SRU template of this bug to
better fit what we found out and the solution that was applied.
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ The systemd networking.service unit will bring down the loopback device (lo)
+ when it is stopped.
** Changed in: ifupdown (Ubuntu Xenial)
Status: Confirmed => 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/1629972
Title:
networking stop incorrectly disconnects from (network) ro
I've verified that networking.service does not take down 'lo' interface
with the proposed version in yakkety (0.8.13ubuntu3).
Below, first I show the problem in 0.8.13ubuntu2 and then install
the proposed version and show it fixed.
$ lxc launch ubuntu-daily:yakkety y1
$ sleep 10
$ lxc exec y1 /
** Changed in: maas
Milestone: 2.1.2 => 2.1.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To manage notif
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To manage notif
This bug was fixed in the package ifupdown - 0.8.13ubuntu4
---
ifupdown (0.8.13ubuntu4) zesty; urgency=medium
* no-change rebuild for upload to zesty.
ifupdown (0.8.13ubuntu3) yakkety-proposed; urgency=medium
* networking.service: exclude loopback device lo in ExecStop (LP:
#162
Hello LaMont, or anyone else affected,
Accepted ifupdown into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.13ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
This is currently in the yakkety-proposed queue at 0.8.13ubuntu3 [1]
and the zesty proposed queue at 0.8.13ubuntu4 [2]
--
[1]
https://launchpad.net/ubuntu/yakkety/+queue?queue_state=1&queue_text=ifupdown
[2] https://launchpad.net/ubuntu/zesty/+queue?queue_state=1&queue_text=ifupdown
** Also a
** Changed in: ifupdown (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To
** Bug watch added: Debian Bug tracker #841106
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841106
** Also affects: ifupdown (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841106
Importance: Unknown
Status: Unknown
--
You received this bug notification because
> ifdown -a --exclude=lo
Indeed, nicely spotted! So this would make a difference on machines
which still have "lo" in /etc/network/interfaces (which hasn't been
necessary/recommended since 2014), but I figure we still have too many
places (installer/cloud image builder etc.) which write that. So
I don't see a matching Debian bug report, so please forward this fix to
Debian as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (net
It seems that the issue here is networking.service does:
/sbin/ifdown -a --read-environment
but it should do:
ifdown -a --exclude=lo
As is seen in the equivalent upstart job (/etc/init/networking.conf).
$ m="ifdown -a --read-environment";
$ sed -i "s,$m, --exclude=lo," /lib/systemd/system/net
I ran into this with iSCSI root. Installing cloud-init resulted in
problems rebooting.
If I install the ifupdown patch (without cloud-init installed), that
triggers the bug for me.
Spinning up a clean instance, installing cloud-init, letting it run (so
the conditions that cause the bug are trigg
** Changed in: maas
Milestone: 2.1.0 => 2.1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To manage notif
+ExecStop=/bin/sh -c 'for f in "$@"; do [ -e "$f" ] || continue; echo "$f
existed."; exit 1; done; exit 0' -- /run/initramfs/open-iscsi.interface
/run/network/network-root-fs
ExecStop=/sbin/ifdown -a --read-environment
This will leave networking.service in "failed" state on stop -- *if* you do
I've subscribed pitti, in an effort to a.) have him review my changes
b.) ask if there is any other way to do this. i've verified in ifupdown
source that 'ifdown -a' will ultimately get '/bin/ip link set dev eth0
down' called.
--
You received this bug notification because you are a member of Ubu
I have a branch of ifupdown at
https://code.launchpad.net/~smoser/ubuntu/+source/ifupdown/+git/ifupdown/+ref/lp-1629972
and just uploaded to https://launchpad.net/~smoser/+archive/ubuntu/ppa
It seems to work for me.
Please test.
--
You received this bug notification because you are a member of
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => High
** Changed in: ifupdown (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: ifupdown (Ubuntu Xenial)
Importance: Undecided => High
--
You received th
ifupdown is actually behaving correctly in this case. It's likely that
cloud-initramfs-tools should be marking the interface "iface foo inet[6]
manual" in every case, since that's the indicator that seems to prevent
ifdown from downing the interface.
When I had it do that, what I then found was t
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Milestone: None => 2.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnec
** Description changed:
With the switch to systemd, all support for iscsi root (and other)
filesystems disappeared, since shutdown yanks the rug out from under us.
Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
creates..), the DEV check should be expanded to include i
31 matches
Mail list logo