** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641468
Title:
systemd-resolve: fallback from resolve causes lookup of local network
hosts to fail
To manage notifications
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647178
Title:
systemd-resolved unable to resolve certain subdomains
To manage notifications about this bug go to:
This is still being discussed upstream, so let's get to an agreement
there first, land it in upstream master, and then backport the change.
Note that there is not much point with debdiffs, it's easier to cherry-
pick the fix directly into the packaging branches with gbp pq and debian
> # Generated by NetworkManager
> nameserver 127.0.1.1
OK, that's definitively unexpected. It looks like NM is still using a
different plugin for managing /etc/resolv.conf and that thinks it's
using the dnsmasq plugin (127.0.1.1) while not actually starting
dnsmasq. That part is understood and
I'm afraid this is by design and wontfix, see
https://github.com/systemd/systemd/issues/4821#issuecomment-264995354
for details. This isn't something which we reasonably can/should change
downstream, so I suggest to direct discussions to the upstream bug.
Thanks!
** Changed in: systemd (Ubuntu)
The verification of the Stable Release Update for python-cassandra-
driver has completed successfully and the package has now been released
to -updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event
OK, thanks. I'm afraid I need the NM log and /etc/resolv.conf with NM
1.4.2-2ubuntu4 without "dns=dnsmasq".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647133
Title:
dns=dnsmasq does not work
> Before=networking.service
> +Before=systemd-networkd.service
FTR, this should be generalized to Before=network-pre.target. This is
also applicable to Debian.
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu)
Status: New
** Changed in: ubuntustudio-meta (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646036
Title:
Drop obsolete pm-utils from Ubuntu
To manage
This still leaves apt, mercurial, and why to be investigated.
** Changed in: glibc (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646064
Title:
> dns=dnsmasq
Ah -- please remove that from /etc/NetworkManager/NetworkManager.conf,
this is not currently working (this is known, this needs to be fixed in
a better way).
** Summary changed:
- Network-manager 1.4.2-2ubuntu4 brakes network connection (Zesty)
+ dns=dnsmasq does not work any more
The verification of the Stable Release Update for procps has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Can you please attach your /etc/NetworkManager/NetworkManager.conf ? NM
is not supposed to create /etc/resolv.conf any more, so I suppose
something else is going on. Can you please reproduce the failed state
and then do
cat /etc/resolv.conf
and copy the output, and run
journalctl -u
> In CUPS everything is OK and as intended.
No -- as above, the maintainer scripts need to stop cups.{socket,path}
first before stopping cups.service. Also, as it seems you can entirely
drop that .path unit as it's fairly useless -- we don't start cups on
demand, but it always starts on boot (in
Till's log shows that cups.path triggers after cups got stopped:
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.path: Got notified about unit
deactivation.
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.path: Changed running -> waiting
Dec 02 10:59:15 till-x1carbon systemd[1]: cups.socket:
** Changed in: plainbox-provider-checkbox (Ubuntu)
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
** Changed in: powernap (Ubuntu)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: ubuntustudio-meta (Ubuntu)
Assignee: (unassigned) => Martin Pi
** Bug watch added: github.com/systemd/systemd/issues #4821
https://github.com/systemd/systemd/issues/4821
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4821
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: Confirmed =>
Hello Harry,
Harry [2016-12-03 15:02 -]:
> Please note, that in my setup, the network is lost immediately after
> rebooting with the new network-manager (1.4.2-2ubuntu4).
Thanks for filing bug 1647133, tracking that issue there.
--
You received this bug notification because you are a
> Requires=cups.service in /lib/systemd/system/cups-browsed.service the
shutdown of CUPS should shutdown cups-browsed first.
No -- Requires/Wants start/stop other units, but they *do not imply
ordering*. If you need to order services against each other you must
additionally specify Before/After=.
First PR sent upstream: https://github.com/systemd/systemd/pull/4808
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/1644330
** Bug watch added: github.com/systemd/systemd/issues #4801
https://github.com/systemd/systemd/issues/4801
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4801
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
> Interestingly, "cups.service: Start request repeated too quickly."
appears on a successful run.
This would usually happen if you try things in a loop, (5 or more
restarts in 10s); run "systemctl reset-failed " in between to
reset the counter.
The journal shows an obvious loop, and at that
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636375
Title:
systemd-resolved does not allow you to connect using subdomains using
search domains which are in
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644330
Title:
systemd-resolved assumes that /etc/hosts for one address family means
it doesn't ask DNS for another
To
I tried this on zesty, and in comment #20 Robie tried on xenial, and we
both get:
> Warning: Stopping cups.service, but it can still be activated by:
> cups.path
(I additionally get cups.socket there too). Thus:
> However, in the real world failure case, cups.path is stopped before
>
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
This is a duplicate of bug 1624729, but for some reason Launchpad keeps
timing out in trying to mark it as such, so I'm closing this.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- package systemd 229-4ubuntu4 failed to install/upgrade: triggers looping,
abandoned
+ several packages failed to install/upgrade: triggers looping, abandoned
--
You received this bug notification
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 failed to install/upgrade: triggers
First error in the log:
Setting up libunity-webapps0:amd64 (2.5.0~+16.04.20160201-0ubuntu1) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
xserver-xorg-video-amdgpu-pro -> xserver-xorg-video-amdgpu-pro
packages' pending triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to
install/upgrade: triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to
install/upgrade: triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to
install/upgrade: triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1646767
package systemd 232-6 failed to install/upgrade: gatilhos em "loop",
abandonado
** This bug is no longer a duplicate of bug 1646767
package
FTR:
-r 1 root root 0 Feb 11 2015 /var/cache/cups/org.cups.cupsd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642966
Title:
package cups-daemon 2.1.3-4 failed to install/upgrade:
I didn't reproduce this yet, answering Till's questions first.
> Does systemd care about keepalive files?
No, there is no such concept. You can certainly build such a thing using
path units and others, but no Linux init system kills processes willy-
nilly from the outside (except on shutdown, of
Sorry, wrong commit:
https://cgit.freedesktop.org/udisks/commit/?id=f641062
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
To manage
Silly me! Should be fixed with
https://cgit.freedesktop.org/udisks/commit/?id=054d9c4201f
** Changed in: udisks2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http://autopkgtest.ubuntu.com/packages/udisks2/zesty/i386 now has two
failures with core dumps. I extracted the stack trace from the topmost
one.
This one is interesting:
f = Frame 0xb662ccec, for file src/tests/test_polkitd.py, line
184, in spawn
http://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#python-virtualenv agrees ☺
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626201
Title:
missing
Sorry about the env var confusion -- in fact $ENABLE_DBGSYM is an
internal variable in dh_strip, so that's definitively wrong.
$DH_BUILD_DDEBS is still present in our version of debhelper:
$dh{ENABLE_DBGSYM} = 0 if not $ENV{'DH_BUILD_DDEBS'};
but got dropped in Debian, so let's not use that
** Description changed:
I went through the current http://people.canonical.com/~ubuntu-archive
/proposed-migration/update_excuses.html#glibc regressions, and these
packages cannot trivially be excluded to be unrelated, so they need a
closer look:
Public bug reported:
I went through the current http://people.canonical.com/~ubuntu-archive
/proposed-migration/update_excuses.html#glibc regressions, and these
packages cannot trivially be excluded to be unrelated, so they need a
closer look:
As xenial-release and yakkety-release have the same ido version, I
forward-copied the xenial SRU to yakkety. This needs to be verified too,
so that both can eventually be released. Otherwise x would have a higher
version than y.
** Also affects: ido (Ubuntu Yakkety)
Importance: Undecided
core-dev cannot commit to the ubuntustudio seeds, so I sent a MP.
** Changed in: ubuntustudio-meta (Ubuntu)
Status: New => 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/1646036
** Changed in: xubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646036
Title:
Drop obsolete pm-utils from Ubuntu
To manage notifications
This also affects powernap, aside from meta packages this is the only
remaining pm-utils reverse dependency.
** Also affects: powernap (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Drop useless Recommends: pm-utils
+ Drop obsolete pm-utils from Ubuntu
--
You
** Changed in: kubuntu-meta (Ubuntu)
Status: New => Fix Committed
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646036
.. but powernap actually uses pm-utils commands all over the place, so
this would need to be ported properly to either "systemctl suspend" and
friends (preferred) or directly talk to /sys/power/state (but this would
prevent userspace inhibitors to work).
** Also affects: kubuntu-meta (Ubuntu)
Public bug reported:
pm-utils has been dead upstream for many many years, and in Ubuntu we
stopped using it since Ubuntu 15.04. However, confusingly we still
install it by default as plainbox-provider-checkbox recommends it.
Please drop this recommends. It's completely useless in Ubuntu, and for
your system, to make sure
it behaves the same?
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645631
Title:
Sending files fails because obex not loaded
To manage notifications about this bug go to:
The -dbg packages got dropped in favor of the automatically created
-dbgsym packages a while ago. This is happening on a large scale in
Debian and Ubuntu. You can use the -dbgsym ones from
http://ddebs.ubuntu.com/pool/universe/p/plasma-workspace/, see
https://wiki.ubuntu.com/DebuggingProgramCrash
md (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local-
resolver has the two outstanding issues to switch NM over to resolved
too. These are unblocked now: the new resolved DNS plugin is in upstream
master since around September, and NM 1.4 landed in zesty-proposed
yesterday. Let's land
This is the more invasive approach which by and large works with current
dpkg. The main inconvenience is that by specifying the file name instead
of output dir debhelper now has to divine the full file name and thus
parse DEBIAN/control.
IIRC this patch does not yet work, but it should be close.
A few weeks back I was experimenting with two approaches, but now I
don't seem to find enough time to get back to this. So for posterity,
this is the naïve approach that just sets -DPackage-Type=ddeb. However,
dpkg does not actually respect that for this case, so this has no
effect. Adam said that
*** This bug is a duplicate of bug 1626436 ***
https://bugs.launchpad.net/bugs/1626436
Thanks for confirming!
** This bug has been marked a duplicate of bug 1626436
[4.8 regression] boot has become very slow
--
You received this bug notification because you are a member of Ubuntu
Bugs,
At least for me the reason was bug 1626436. Can you try the test kernel
there and see if that helps?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: sbuild (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Indeed this does not happen any more with the upstream master build from
https://launchpad.net/~pitti/+archive/ubuntu/systemd/+packages, so 233
will fix this.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member
** Changed in: resolvconf (Ubuntu)
Assignee: Martin Pitt (pitti) => Canonical Foundations Team
(canonical-foundations)
** Changed in: resolvconf (Ubuntu)
Milestone: ubuntu-16.11 => ubuntu-16.12
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: systemd (Ubuntu Xenial)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for cl
There is some chance that this got fixed with
https://github.com/systemd/systemd/commit/c5a97ed1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620780
Title:
dev-sda2.device job running and times
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504254
Title:
IdleAction=suspend specified in logind.conf m
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579130
Title:
need to support renaming of devices in contai
** Changed in: apport (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446537
Title:
apport hook fails in add_info with TypeError: '
** Changed in: dkms (Ubuntu Trusty)
Assignee: Martin Pitt (pitti) => (unassigned)
** No longer affects: dkms (Ubuntu Wily)
** Changed in: dkms (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: autopkgtest (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461577
Title:
Need a way to copy files to the test bed
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed: No s
** Changed in: init-system-helpers (Ubuntu Xenial)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596056
Title:
output of invoke-rc.d for syst
** Changed in: network-manager (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615044
Title:
"unmanaged-devices=" lis
** Changed in: apport
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605954
Title:
start_sessiondbus.py assert failure: *** Error in `/usr/
** Changed in: postgresql-9.3 (Ubuntu Trusty)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1399759
Title:
[trusty] Ability to use newer
*** This bug is a duplicate of bug 1613297 ***
https://bugs.launchpad.net/bugs/1613297
No response in a month, so marking this a duplicate for now. Please
unduplicate as appropriate if it's something different after all.
** Changed in: unity (Ubuntu)
Assignee: Martin Pitt (pitti
I successfully ran the test case against ubuntu20.9 in -proposed. I also
verified that using losetup and mount on loop devices still works:
$ sudo losetup -f --show debian-stretch-DI-alpha7-amd64-netinst.iso
/dev/loop0
$ sudo mount /dev/loop0 /mnt
mount: block device /dev/loop0 is
Right, this should at least be documented in the manpage. The NM
renderer already produces an appropriate error message.
** Changed in: netplan
Importance: Undecided => Low
** Changed in: netplan
Status: New => In Progress
** Changed in: netplan
Assignee: (unassigned) =&g
snapd is not completely ready for trusty yet, as it needs quite a lot of
adjustments to work in that old environment:
https://github.com/snapcore/snapd/pull/2128 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also see this with exfat, so it rather seems to be related to fuse (as
both ntfs-3g and exfat use fuse). Curiously I do not see this when
running the tests on my laptop or on the Scalingstack cloud infra, just
when I run them in QEMU.
--
You received this bug notification because you are a
> Curiously I do not see this when running the tests on my laptop
And of course in the minute I write this it does happen again (I ran the
test maybe 20 times today, and only just now it happened):
[11359.569157] INFO: task systemd-udevd:341 blocked for more than 120 seconds.
[11359.569163]
I ran it five times on the production infrastructure and it does not
reproduce there either, so a nasty heisenbug :-(
I instead changed the test to archive a core dump if the test crashes,
so that this can be debugged post-mortem:
https://anonscm.debian.org/cgit/pkg-
This does not reproduce locally or with autopkgtest-virt-qemu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
To manage notifications
This is apparently fixed in xenial-proposed, but the release is blocked
(see bug 1637215).
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: snapd (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because
This is not fixed in zesty yet, as it's blocked in -proposed on several
test failures: http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#snapd
This also blocks the SRU release, in addition to the new xdelta universe
dependency.
** Changed in: snapd (Ubuntu)
** Changed in: udisks2 (Ubuntu)
Status: Triaged => 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/1585382
Title:
test_internal_fs_allowed crashes with SIGABRT
To manage
Hello Stéphane, or anyone else affected,
Accepted lxd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxd/2.0.8-0ubuntu1~ubuntu16.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Reopening for trusty as the change was reverted in bug 1644428.
** Changed in: samba (Ubuntu Trusty)
Status: Fix Released => In Progress
** Tags removed: verification-done-trusty
** Tags added: verification-failed
** Tags removed: verification-needed
--
You received this bug
For the record, this just needs to be verified to fix the regression and
still generally work. This should *not* be delayed for the usual 7 day
maturing period as this fixes a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Lyle, or anyone else affected,
Accepted samba into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.3.11+dfsg-
0ubuntu0.14.04.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Downgrading lxd from zesty's 2.6 to yakkety's 2.4.1 (which was also the
zesty version until last week) fixes this. So this is somewhere between
an lxd regression or juju needing to be updated for lxd 2.6. As lxd
usually gets backported fairly quickly, raising severity.
** Also affects: lxd
Another attempt (back at zesty): I lxc exec'ed into the container and
ran "ssh-import-id lp:pitti" as ~ubuntu, and now I can ssh to the
created container. But juju bootstrap doesn't seem to recognize this and
re-try, it just still sits there attempting to ssh. There is no ssh
client process
This is perfectly reproducible on a pristine zesty cloud image in a VM
after installing and configuring lxd first, then juju-2.0.
I also tried on a pristine xenial cloud VM, and I don't even get that
far:
$ juju-2.0 bootstrap lxd localhost
Creating Juju controller "lxd" on localhost/localhost
As a data point, I was doing the same last week in zesty, and it worked
perfectly. Also juju-core itself did not change since then (it's the
same version as in yakkety), so something underneath it broke.
I confirmed this bug with 2.0 final in zesty-proposed, same behaviour.
** Also affects:
Public bug reported:
In current zesty, "juju-2.0 bootstrap lxd localhost" does:
Creating Juju controller "lxd" on localhost/localhost
Looking for packaged Juju agent version 2.0-rc3 for amd64
Launching controller instance(s) on localhost/localhost...
- juju-5fc6db-0
Fetching Juju GUI 2.2.3
I suppose you want this for yakkety too, so backported:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-yakkety=648c659e9
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as
Xenial fixes:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=aeff48d716
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=310753a6
** Changed in: systemd (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as networking is not yet
available when cloud-init.service runs.
cloud-init service unit deps look like this:
[Unit]
Description=Initial
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as networking is not yet
available when cloud-init.service runs.
cloud-init service unit deps look like this:
[Unit]
Description=Initial
Thanks Po-Hsu. This is clearly a bug within test-snapd-tools, possibly
fixed by bug 1641243. Is there a simpler "hello world" type snap that
has a service that can be used to verify this without running into the
apparmor profile issue?
Steps 7 to 9 can be done independently.
--
You received
I just landed the last PR (https://github.com/systemd/systemd/pull/4710)
in upstreamd master that fully fixes networkd for early boot. The
complete set is too intrusive to backport, but we don't need to in
xenial: Transient (DHCP-acquired) hostname and timezone have never
worked in xenial, and it
** Description changed:
- Hello,
+ The current packaged systemd for Yakkety does not have the Mellanox
+ netdev udev naming set for systemd patch installed
+ (https://github.com/systemd/systemd/commit/4887b656c22). The current
+ version for zesty does. I installed the ppa for this on to my
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
301 - 400 of 54145 matches
Mail list logo
