Processed: Re: Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 879518 normal Bug #879518 [ifupdown] ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please

Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Guus Sliepen
severity 879518 normal thanks On Sun, Oct 22, 2017 at 04:35:58PM +0200, Daniel wrote: > Severity: critical > Justification: breaks the whole system Downgrading to normal since this bug doesn't fit the definition of critical: “Makes unrelated software on the system (or the whole system) break,

Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Daniel Huhardeaux
I investigate further and discover that the the message "recursion detected in parent-lock" appears in *ALL* vlan interfaces (.1 .2 .100 .1001 .1002), not only the 2 first one as I reported. After having removed all pre-up bone and pre-up bone.vlan in interfaces file, I was able to again set

Bug#879518: ifupdown: fail to start with bridge_stp on and recursion detected in parent-lock with vlan after jessie upgrade

2017-10-22 Thread Daniel
Package: ifupdown Version: 0.8.19 Severity: critical Justification: breaks the whole system This setup was perfectly running on Jessie. After upgrading to Stretch, all the network stuff was down, doesn't matter if local, VMs or Internet. In the interfaces file below we changed the bridge-stp to