Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Wed, Sep 27, 2017 at 05:11:06PM +0200, Michael Biebl wrote: > Am 27.09.2017 um 17:06 schrieb Marc Haber: > > On Wed, Sep 27, 2017 at 04:22:09PM +0200, Michael Biebl wrote: > >> Ok, I've usertagged the bug for now so it shows up at [1] as a possible > >> candidate for a backport for a stretch

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Wed, Sep 27, 2017 at 04:22:09PM +0200, Michael Biebl wrote: > Ok, I've usertagged the bug for now so it shows up at [1] as a possible > candidate for a backport for a stretch stable upload. > Your patch applies (with a bit of fuzz) to our stretch/v232 branch. > That said, it would be great if

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Am 27.09.2017 um 17:06 schrieb Marc Haber: > On Wed, Sep 27, 2017 at 04:22:09PM +0200, Michael Biebl wrote: >> Ok, I've usertagged the bug for now so it shows up at [1] as a possible >> candidate for a backport for a stretch stable upload. >> Your patch applies (with a bit of fuzz) to our

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Am 27.09.2017 um 16:04 schrieb Marc Haber: > On Wed, Sep 27, 2017 at 03:47:34PM +0200, Michael Biebl wrote: >> Do you need those fixes for the stretch/stable package or is it >> sufficient if we fix that for sid/buster (and stretch-bpo)? > > It would be great for that to be in a stretch point

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Wed, Sep 27, 2017 at 03:47:34PM +0200, Michael Biebl wrote: > Am 25.09.2017 um 08:50 schrieb Marc Haber: > > tags #869995 patch > > thanks > > > > I have worked in the last days with Susant Sahani to isolate this > > issue and can confirm that his patches: > >

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Am 25.09.2017 um 08:50 schrieb Marc Haber: > tags #869995 patch > thanks > > I have worked in the last days with Susant Sahani to isolate this > issue and can confirm that his patches: > https://github.com/systemd/systemd/pull/6907/commits/e6800d3cfb48542634c25c24a6aae7587d97eb4f >

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

tags #869995 patch thanks I have worked in the last days with Susant Sahani to isolate this issue and can confirm that his patches: https://github.com/systemd/systemd/pull/6907/commits/e6800d3cfb48542634c25c24a6aae7587d97eb4f

Processed: Re: Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Processing commands for cont...@bugs.debian.org: > tags #869995 patch Bug #869995 [systemd] interface stuck in "configuring" if SLAAC prefix announced with preferred lifetime zero Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 869995:

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Fri, 8 Sep 2017 21:34:25 +0200 Michael Biebl wrote: > Am 04.09.2017 um 11:05 schrieb Marc Haber: > > This bug severely affects systemd-networkd's usability in Debian stable > > and has been without maintainer attention for a month. > > > > Is there any way to help? > > The

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Am 04.09.2017 um 11:05 schrieb Marc Haber: > This bug severely affects systemd-networkd's usability in Debian stable > and has been without maintainer attention for a month. > > Is there any way to help? The best course of action would be to raise this issue upstream at

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

This bug severely affects systemd-networkd's usability in Debian stable and has been without maintainer attention for a month. Is there any way to help? Greetings Marc -- - Marc Haber | "I don't trust

Processed: Re: Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Processing commands for cont...@bugs.debian.org: > retitle #869995 interface stuck in "configuring" if SLAAC prefix announced > with preferred lifetime zero Bug #869995 [systemd] interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state Changed Bug title

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

retitle #869995 interface stuck in "configuring" if SLAAC prefix announced with preferred lifetime zero thanks While investigating whether going back to stretch's systemd will solve the issue, I found out that it does already exist in stretch and that the fact that systemd-wait-online gets stuck

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

to be in DNS). I think this warrants an "important" priority, if not a release critical one. Please consider that. Greetings Marc On Sat, Aug 19, 2017 at 11:39:06AM +0200, Marc Haber wrote: > From: Marc Haber <mh+debian-b...@zugschlus.de> > Subject: Bug#869995: interface stays in

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

forwarded #869995 https://github.com/systemd/systemd/issues/6359 thanks Hi Felipe, I finally got aound to verifying against the github issue. On Fri, Jul 28, 2017 at 10:49:20AM -0400, Felipe Sateler wrote: > Does the problem go away if you remove all the static configuration? This > may be

Processed: Re: Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

Processing commands for cont...@bugs.debian.org: > forwarded #869995 https://github.com/systemd/systemd/issues/6359 Bug #869995 [systemd] interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state Set Bug forwarded-to-address to

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Fri, Jul 28, 2017 at 10:49:20AM -0400, Felipe Sateler wrote: > Does the problem go away if you remove all the static configuration? I have reduced the systemd network file to: [7/232]mh@testsid85:~ $ cat /etc/systemd/network/testsid85.network [Match] Name=e* [Network] DNS=fec0:0:0:::1

Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

On Fri, Jul 28, 2017 at 10:00 AM, Marc Haber < mh+debian-packa...@zugschlus.de> wrote: > Package: systemd > Version: 234-2 > Severity: normal > > Hi, > > this is on a KVM VM running Debian unstable with a custom kernel. I do > see this on other machines as well and have not yet investigated >