removing sts tag, as this is still marked new for vlan in debian; any
vlan delta to debian should be handled elsewhere and is more than this
bug's patches.
** Tags removed: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: ifupdown (Ubuntu)
Status: In Progress => 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/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
This bug was fixed in the package ifupdown - 0.7.47.2ubuntu4.5
---
ifupdown (0.7.47.2ubuntu4.5) trusty; urgency=medium
* We are not even reading the contents of the per-interface state files
when running ifquery, so there is no need to lock them. Not locking
will allow ifque
This bug was fixed in the package vlan - 1.9-3ubuntu10.6
---
vlan (1.9-3ubuntu10.6) trusty; urgency=medium
* Revert change for lp1573272; instead fix by redesigning when vlan
interfaces are created; after raw-device ifup, not during raw-device
udev processing. (LP: #1701023)
This bug was fixed in the package vlan - 1.9-3.2ubuntu1.16.04.5
---
vlan (1.9-3.2ubuntu1.16.04.5) xenial; urgency=medium
* Revert change for lp1573272; instead fix by redesigning when vlan
interfaces are created; after raw-device ifup, not during raw-device
udev processing.
This bug was fixed in the package ifupdown - 0.8.10ubuntu1.4
---
ifupdown (0.8.10ubuntu1.4) xenial; urgency=medium
* We are not even reading the contents of the per-interface state files
when running ifquery, so there is no need to lock them. Not locking
will allow ifquery t
This bug was fixed in the package vlan - 1.9-3.2ubuntu5.17.10.1
---
vlan (1.9-3.2ubuntu5.17.10.1) artful; urgency=medium
* Revert change for lp1573272; instead fix by redesigning when vlan
interfaces are created; after raw-device ifup, not during raw-device
udev processing.
This bug was fixed in the package ifupdown - 0.8.16ubuntu2.1
---
ifupdown (0.8.16ubuntu2.1) artful; urgency=medium
* We are not even reading the contents of the per-interface state files
when running ifquery, so there is no need to lock them. Not locking
will allow ifquery t
This bug was fixed in the package ifupdown - 0.8.17ubuntu1.1
---
ifupdown (0.8.17ubuntu1.1) bionic; urgency=medium
* We are not even reading the contents of the per-interface state files
when running ifquery, so there is no need to lock them. Not locking
will allow ifquery t
I think this aged long enough in -proposed - releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To man
This bug was fixed in the package vlan - 1.9-3.2ubuntu6
---
vlan (1.9-3.2ubuntu6) bionic; urgency=medium
* Revert change for lp1573272; instead fix by redesigning when vlan
interfaces are created; after raw-device ifup, not during raw-device
udev processing. (LP: #1701023)
trusty:
root@lp1701023:~# dpkg -l | grep ifupdown
ii ifupdown 0.7.47.2ubuntu4.4
amd64high level tools to configure network interfaces
root@lp1701023:~# dpkg -l | grep vlan
ii vlan 1.9-3ubuntu10.5
xenial:
root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep ifupdown
ii ifupdown 0.8.10ubuntu1.4
amd64high level tools to configure network interfaces
root@lp1701023-x:/etc/network/interfaces.d# dpkg -l |grep vlan
ii vlan
tested on artful with:
root@lp1701023-a:~# dpkg -l | grep ifupdown
ii ifupdown 0.8.16ubuntu2.1
amd64high level tools to configure network interfaces
root@lp1701023-a:~# dpkg -l | grep vlan
ii vlan
tested bionic per comment 19 with:
root@lp1701023-b:~# dpkg -l | grep ifupdown
ii ifupdown 0.8.17ubuntu1 amd64
high level tools to configure network interfaces
root@lp1701023-b:~# dpkg -l | grep vlan
ii vlan 1.9-3.2u
This bug was fixed in the package vlan - 1.9-3.2ubuntu6
---
vlan (1.9-3.2ubuntu6) bionic; urgency=medium
* Revert change for lp1573272; instead fix by redesigning when vlan
interfaces are created; after raw-device ifup, not during raw-device
udev processing. (LP: #1701023)
I sent an email to ubuntu-server list requesting anyone with vlan
ifupdwon config to give these -proposed pkgs a test.
I'll also perform verification for them when I have a chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Hello Sven, or anyone else affected,
Accepted ifupdown into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.7.47.2ubuntu4.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Sven, or anyone else affected,
Accepted ifupdown into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.16ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Sven, or anyone else affected,
Accepted vlan into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu5.17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
> I would feel better if a wider call-for-testing could be done on these
> packages
> in bionic-proposed
yes i agree; the mailing lists that comes to mind is ubuntu-server, do
you have any other ML suggestion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Seeing that the previous change caused regressions, I would feel better
if a wider call-for-testing could be done on these packages in bionic-
proposed, performing tests on various different configurations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hello Sven, or anyone else affected,
Accepted vlan into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu6 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
> could we get the SRU template information included in this bug?
doh. sorry, been awfully busy lately. added.
** Description changed:
+ [impact]
+
+ in bug 1573272, the vlan pkg was changed to perform a full ifup inside
+ its if-pre-up.d/vlan script. This allowed correct ordering of ifup for
@ddstreet - could we get the SRU template information included in this
bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
> Neither issue is fixed by the downgrade
ok, thanks, so those are ifupdown issues unrelated to this vlan
regression - please feel free to open bug(s) for them. I'll start an
sru for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Neither issue is fixed by the downgrade. As said, neither seems to have
to do with vlan but with ifupdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubunt
> We migrated from separate files in /etc/networking/interfaces.d to just
> declaring
> everything in the single /etc/networking/interfaces file. This overcomes a
> lot of
> issues with regards to bringing interfaces up in the proper order and "ifup
> -a"
> now works perfectly again
great.
> (
Hi @ddstreet. Completely understand your need to limit the scope of this
bug. Just shared our findings, but feel free to ignore the stuff in #28
under item 2. We did a lot of extensive testing over the weekend with
the latest version of your PPA package and here are our main findings:
1) We migrat
I updated the ifupdown pkg builds in my test ppa using the upstream
(debian) patch, which is a variation of my previous patch. Anyone
affected by this regression please test with the latest ifupdown and
vlan pkgs from my ppa.
--
You received this bug notification because you are a member of Ubun
> Unfortunately it turns out this change does not fix the issue of interfaces
> not
> coming up correctly for a bond with a (static) network configuration
Please keep in mind this bug is *specifically* about the regression
caused by the change from bug 1573272, as described in this bug
descriptio
We've been doing a lot more testing and debugging and I'd like to share
our findings:
1) Unfortunately it turns out this change does not fix the issue of interfaces
not coming up correctly for a bond with a (static) network configuration. The
race condition seems to be removed so at least there
Debian's included a variation of my patch to ifupdown, so I'll update my
ppa to use that patch instead and do some testing, then start sru'ing
both ifupdown and vlan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** 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/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
comple
> @ddstreet tested with the latest version of ifupdown and vlan from your PPA
> with
> my 4 testscenario's and can confirm it works as expected. Interfaces come up
> correctly both when doing an "ifup -a" and during boot.
Excellent, thanks.
> One small thing I've noticed is a variation in the nu
@ddstreet tested with the latest version of ifupdown and vlan from your
PPA with my 4 testscenario's and can confirm it works as expected.
Interfaces come up correctly both when doing an "ifup -a" and during
boot.
One small thing I've noticed is a variation in the number of "Set name-
type for VLA
** Changed in: vlan (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/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To
** 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/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
** Bug watch added: Debian Bug tracker #896433
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433
** Also affects: ifupdown (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #89643
Test pkgs for both ifupdown and vlan available in this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu Trusty)
Status: New => In Progress
** Changed in: ifupdown (Ubuntu Trusty)
Assignee: (unassigned)
Also re: testcase 3, I could only reproduce it on reboot and ifup -a; it
did not fail when i tried hotplugging the interface (modprobing its
driver).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17010
@smu-u, please do let me know if you are seeing this issue in X/A/B.
Otherwise, I'll assume you only see this issue in trusty, which matches
what I found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
For testcase 3, from this bug, I'm able to reproduce it on trusty using
vlan 1.9-3ubuntu10.5, and using the pkg from my ppa it is fixed.
I'm not able to reproduce testcase 3 in xenial or later, so there is
nothing to verify re: testcase 3 (this bug's reported error) in X/A/B.
However, my redesign
Test case #1 (bug 1573272), part (a) and (b) only:
I'm unable to reproduce test case #1 failure on trusty, because upstart
is used instead of systemd. I'm not sure if that means the race
condition doesn't affect trusty, or if i'm just not able to properly
introduce a upstart delay to bond0 to eas
For testcase 2, from bug 1759573, I can't reproduce the reported hang
from that bug.
@tom-verdaat, can you provide simpler/clearer reproduction steps, or can you
test with the vlan pkg from this ppa to verify it fixes the problem you're
seeing:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1
There are 3 test cases here to verify this:
1) the original bug 1573272. Test case is in that case's description. Note
this test case needs to be (using trusty version numbers):
a) FAIL with vlan 1.9-3ubuntu10.1
b) PASS with vlan 1.9-3ubuntu10.5 (current version)
c) PASS with the proposed
Also, for each of those test cases, this fix needs to be tested for:
a) normal bootup
b) ifup -a
c) physical device hotplug (e.g. insmod driver, or hotplug removable nic)
all cases should bring up the configure the associated vlans correctly.
--
You received this bug notification because you ar
Anyone experiencing this bug, can you please test with the vlan package from
this test ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023
I still need to do more testing with it as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The reason that udev calls /lib/udev/vlan-network-interface is because
of hotplugging.
During boot up, as network interfaces are detected by the kernel, they
are reported to udev, and udev passes each to vlan-network-interface.
If the vlan-network-interface script detects that a new interface is
c
The reason the if-pre-up.d/vlan script was changed to call ifup for its
raw-device, was for bug 1573272, where the problem was a race condition
between the VLAN and its raw-device; if the VLAN interface was processed
through if-pre-up.d/vlan before the raw-device was fully configured,
then in some
This bug is caused in two different ways, both not directly from
ifupdown or vlan, but instead because of 'helpful' actions in the
ifenslave and bridge-utils if-pre-up scripts.
First, as reported in this bug, the bridge-utils package adds a
if-pre-up.d/bridge ifupdown script, and in that script
marking this as affecting T/X/A/B, although I need to specifically check
each.
** Also affects: vlan (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Bionic)
Importance: High
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also af
from bug 1759573, looks like this does affect X as well as T.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
It appears this ifupdown locking issue doesn't happen in Xenial, but
I'll do more testing to confirm that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubunt
@smu-u can you please test with the vlan pkg from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023
it fixes this specific issue in my test, but I'd like to make sure it
works for you also.
I want to do some more testing with the change as well because ifupdown
is so fragile in
** Tags added: regression-update sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To manage notifications a
I reproduced this hang on trusty and I'm investigating.
** Changed in: vlan (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: vlan (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubunt
Well I can't say I'm too surprised that something broke, the
ifupdown<->vlan<->udev love triangle of creating and configuring vlans,
is a bit of a mess. I'll take a look at this as soon as I have a
chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
The changelog since 10.1 mentions #1573272 three times, looks like that
was a tough nut to crack. I'm subscribing ddstreet for consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Titl
** Changed in: vlan (Ubuntu)
Importance: Undecided => High
** Also affects: vlan (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: vlan (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: vlan (Ubuntu Trusty)
Importance: Undecided => High
--
You receiv
This diff resulted in the boot breaking again:
http://launchpadlibrarian.net/324174495/vlan_1.9-3ubuntu10.1_1.9-3ubuntu10.4.diff.gz
- reverting the change fixed the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Apologies, I had my versions screwed up. Disregard my previous comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
co
Can we get someone to fix this policy violation, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To ma
Note: This behavior is in direct violation of the Debian documentation:
https://wiki.debian.org/NetworkConfiguration#Bringing_up_an_interface_without_an_IP_address
Specifies:
Note: If you create the VLAN interface only to put it into a bridge, there is
no need to define the VLAN interface manuall
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vlan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on t
66 matches
Mail list logo
