** Changed in: resolvconf (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to ens
This bug was fixed in the package systemd - 229-4ubuntu17
---
systemd (229-4ubuntu17) xenial; urgency=medium
* Make systemd-networkd-resolvconf-update.{service,path} run earlier
to ensure DNS is configured prior to reaching network-online.target.
(LP: #1649931)
-- Ryan Har
This bug was fixed in the package resolvconf - 1.79ubuntu1.1
---
resolvconf (1.79ubuntu1.1) yakkety; urgency=medium
* debian/resolvconf.service: resolvconf service must run before any of the
possible network configuration services (ifupdown, networkd,
NetworkManager) so use
Ok, I've succeeded in verifying this by adding an artificial
ExecStartPre=/bin/sleep 10 to both old and new resolvconf.service. Old:
# journalctl -o short-precise --unit resolvconf.service --unit
network-online.target --unit systemd-networkd-wait-online.service --unit
systemd-networkd.service
I've tested this now in a 16.10 VM, and I can't verify this SRU because
I can't confirm the buggy behavior. Adjusting the journalctl command
for changed unit names in 16.10, I get:
# journalctl -o short-precise --unit resolvconf.service --unit
network-online.target --unit systemd-networkd-wait-o
Running the test case from the bug description for a yakkety container,
this is the behavior I see with the yakkety-updates version of nplan:
-- Logs begin at Thu 2017-04-20 05:38:36 UTC, end at Thu 2017-04-20 05:40:08
UTC. --
Apr 20 05:38:36.302406 y1 systemd[1]: Started Nameserver information m
I've moved the systemd-resolved issue for unit ordering out of this
bug/SRU into a new one so we can finish out this SRU and handle this
last change to systemd-resolved separately.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860
--
You received this bug notification because you ar
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to e
Details about different release vs. network backend requirements
** Attachment added: "lp1649931-release-network-matrix.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4833940/+files/lp1649931-release-network-matrix.txt
--
You received this bug notification be
@racb
I verified systemd 229-4ubuntu17 with both ifupdown and networkd
configuration.
The specific packages and features is somewhat complicated due to
the different scenarios and change in networking behavior in yakkety+
I've attached a chart with details. Also viewable here:
http://paste.ubu
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs t
> I've verified the SRU test with the package in Xenial proposed.
Which package and what versions please? This shows up as green in
https://people.canonical.com/~ubuntu-archive/pending-sru.html for
systemd, but it's not clear to me from this bug that systemd
229-4ubuntu17 is ready to be released t
For yakkety resolvconf update; I've updated the SRU test-case to
include a more general netplan config for bringing up ethernet devices;
the previous version only worked on lxd (or instances with devices named
eth0).
With the above change; it looks like yakkety/zesty (due to running
systemd-resol
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd +
This bug was fixed in the package resolvconf - 1.78ubuntu4
---
resolvconf (1.78ubuntu4) xenial; urgency=medium
* debian/resolvconf.service: resolvconf service must run before any of the
possible network configuration services (ifupdown, networkd,
NetworkManager) so use netwo
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to ensur
I've verified the SRU test with the package in Xenial proposed. I've
also updated an UbuntuCore16 image with uses networkd and cloud-init to
validate that early networking which requires dns for resolving urls
works.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd +
Hello Ryan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu17
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to
** Patch added: "xenial-dns-before-online-target-lp1649931-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4812597/+files/xenial-dns-before-online-target-lp1649931-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Tou
systemd-networkd-resolvconf-update.service uses default dependencies
which will only run after sysinit.target, however cloud-init.service
needs to run before sysinit.target; systemd apparently dropped running
the service due to the inconsistent order. Adding a
DefaultDependencies=no to systemd-net
Something isn't working here. I also typo'd the test-case, in
particular, the change to the cloud-init.service unit didn't specify
'systemd-networkd-wait-online.service', the sed command missed the 'd'
in networkd.
When I fix that, I find that systemd-networkd-resolvconf-update.service
does NOT r
This has had systemd 231-9ubuntu3 stacked on top into xenial-proposed.
See bug 1647485 for details. When verifying, please test and verify
systemd 231-9ubuntu3, not the previous version, and confirm the package
version you tested in your comment to avoid any misunderstanding.
Thanks!
--
You recei
** Changed in: systemd (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to ensur
I accepted systemd into xenial-proposed but I received an LP timeout
when the script was trying to add a comment. I image you can figure out
what to do from the resolvconf comment though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Changed in: resolvconf (Debian)
Status: Unknown => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to ensur
** Also affects: resolvconf (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
Importance: Unknown
Status: Unknown
** Changed in: resolvconf (Ubuntu)
Importance: Undecided => Medium
** Changed in: resolvconf (Ubuntu Xenial)
Importance: Undecided => Medium
**
Hello Ryan, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: resolvconf (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://b
>> For systemd portion, we carry the
>> systemd-networkd-resolvconf-update.service as a delta from Debian
> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.
Ok, it appears that post-16.04, systemd-networkd-resolvconf-
update.service is dropped fro
On Thu, Dec 15, 2016 at 09:43:48PM -, Ryan Harper wrote:
> I don't disagree (that saying few folks impacted means low).
> This portion was split out from the previous systemd SRU
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912
> in which the changes were classified in the sa
resolvconf (1.79ubuntu4) zesty; urgency=medium
* debian/resolvconf.service: Add missing Wants=network-pre.target.
-- Martin Pitt Thu, 08 Dec 2016 10:21:12
+0100
resolvconf (1.79ubuntu3) zesty; urgency=medium
* debian/resolvconf.service: resolvconf service must run before any of the
pos
On Thu, Dec 15, 2016 at 09:44:32PM -, Ryan Harper wrote:
> On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> > How is this fixed in the development release?
> For systemd portion, we carry the
> systemd-networkd-resolvconf-update.service as a delta from Debian
I'm not sure what you me
** Bug watch added: Debian Bug tracker #847440
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
For systemd portion, we carry the
systemd-networkd-resolvconf-update.service as a delta from Debian
Ryan
--
You received this bug notification because you are a member of Ubuntu
Touch seede
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
There is an upstream resolvconf bug that addresses that package portion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
> Also the having a "Regression Potential" of low just bec
How is this fixed in the development release?
Also the having a "Regression Potential" of low just because not a lot
of people use the service is wrong. A bad change could still horribly
impact the users of the software, regardless of how many users there
are.
** Changed in: resolvconf (Ubuntu)
** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd +
The attachment "xenial_resolvconf-lp1649931.diff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
** Patch added: "xenial_resolvconf-lp1649931.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
42 matches
Mail list logo
