> I think it'd be acceptable to allow other packages through proposed
despite a MySQL dep8 test failure
There should not be any others, as mysql-5.7 only exists in xenial-
proposed, and we test packages against xenial-release as much as
possible.
--
You received this bug notification because
Looks ok, approved and accepted.
** Changed in: ethtool (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ethtool in Ubuntu.
https://bugs.launchpad.net/bugs/1563551
Title:
Sync
It looks like dbconfig-common needs to be adjusted for MySQL 5.7. It
fails on "mysql: [ERROR] mysql: Empty value for 'port' specified."
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Seems Ryan is still investigating whether or not to enable AIO in the
first place. If you decide to disable it, then there's no FFE, and if
you want to enable it and can make sure that it does not negatively
affect other modes, then Adam already gave the OK.
** Changed in: tgt (Ubuntu)
This is conceptually part of Juju 2.0, so the FFE for that should apply
to charm tools too. +1
** Changed in: charm-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
120 kB changelog essentially means "many changes". What testing has been
done with the new version? Do any of the reverse dependencies (cluster-
glue, collectd, heartbeat, zabbix, etc.) need updating as well? How were
these tested with the new openipmi?
** Changed in: openipmi (Ubuntu)
FTR, I did an initial source NEW review of juju2. In the initial MIR bug
1267393 (two years ago) the deal was to *reduce* the embedded code
copies and replace them with golang-google-api-dev & co. build
dependencies. juju-core now does have a handful of those, but still an
awful lot of embedded
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
munin-node -> munin-node
packages' pending triggers which are or may be unresolvable:
ca-certificates: update-ca-certificates
dbus: /etc/dbus-1/system.d
systemd: /etc/init.d
Lamont apparently knows what's going on. He'll restore the -export
versions soon, so that we can switch isc-dhcp back to those.
** Changed in: isc-dhcp (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
** Changed in:
Further bisection shows that 4.3.3-5ubuntu5 is the last version that
works, and 4.3.3-5ubuntu7 is the first version that fails (ubuntu6
cannot be tested as that FTBFSed).
The corresponding diff is http://launchpadlibrarian.net/242313487/isc-
dhcp_4.3.3-5ubuntu5_4.3.3-5ubuntu7.diff.gz -- the
I was about to point out the Delegate= option if docker.service wants to
maintain its sub-cgroups by itself -- but it seems that already landed
upstream two days ago: https://github.com/jheiss/docker/commit/64b87f0
There have been plenty of discussions about that "who owns the cgroup
This still works fine with Linux 4.4.0-8, but fails on 4.4.0-10, so it's
a kernel regression.
This can be reproduced much simpler without LXC:
$ mkdir /tmp/lower /tmp/upper /tmp/work /tmp/merged
$ sudo mount -t overlay overlay
-olowerdir=/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/work
I tried to purge all lxc/lxd packages and install LXC 2.0.0~rc1-0ubuntu1
again, but this now not working at all any more on xenial's kernel --
the container never starts and I get a lot of apparmor violations.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
I'm investigating some failures in autopkgtest's testsuite, and stumbled
over something really weird: In an ephemeral container it is apparently
not possible any more to chmod files that started out being root owned
and got chowned later:
$ sudo lxc-start-ephemeral -o
promoted to main
** Changed in: python-pika-pool (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pika-pool in Ubuntu.
https://bugs.launchpad.net/bugs/1552827
Title:
I tried to purge and reinstall openssh-server on today's cloud image
(with i-s-h 1.29ubuntu1) and ssh.service does start up right away as
expected. So this naïve reproducer doesn't work. Max, how does openssh-
server get installed in your case? Sorry for my ignorance, I don't know
much about
ssh has tons of reverse dependencies, most of which don't have
autopkgtests. However, the risk seems acceptable as the changelog does
not mention any removed features or different interpretation of existing
config options; and this does not depend on anything else, so if this
hypothetically breaks
Given that this seems to be somewhat brittle, would you mind adding some
integration tests for lxc-attach for various combinations of
stdin/stdout/stderr redirection?
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You
This is indeed a regression in lxc-attach. Until 2.0.0~rc1 this DTRT:
$ sudo lxc-attach -n adt-virt-lxc-lbmmpf -- sh -c 'echo ERR>&2' >/dev/null
ERR
but not any more with rc5:
$ sudo lxc-attach -n a -- sh -c 'echo ERR>&2' >/dev/null
# (no output)
** Summary changed:
- latest LXC breaks
Public bug reported:
With lxc 2.0.0~rc5-0ubuntu1 the autopkgtest LXC runner is still broken
(even with bug 1551960 fixed) when stderr is a terminal:
$ adt-run gzip --- lxc -s adt-wily
[...]
adt-run [10:15:45]: ERROR: erroneous package: got 10 lines of results from
extract where 4 expected:
Many thanks for addressing this. Fixing this for an LTS is much
appreciated indeed, as it will make the cloud images much more useful
particularly for "real hardware" use cases, and also get rid of some
gross hacks in e. g. autopkgtest, and fix the broken ppc64el images
along the way (bug
With that fix applied the adt-virt-lxc tests work fine again, so
removing the autopkgtest task again (I added it in case I need to adjust
something to the new LXC in that regard).
** No longer affects: autopkgtest (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
I locally applied https://github.com/lxc/lxc/commit/12752e2 to our
current package and built it. Now it looks better:
# lxc-attach -n a runlevel
N 5
# lxc-attach -n a runlevel /dev/null
N 5
# lxc-attach -n a runlevel /dev/null | cat
So redirecting stdin only now does not show this
Nevermind, I built upstream git master, and that lxc-attach works fine.
Thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551960
Title:
lxc-attach does not work any
Thanks Christian for the fast fix!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551935
Title:
lxc-copy message is the wrong way around
To manage notifications about this bug go to:
Public bug reported:
LXC 2.0.0~rc{2,3,4} break autopkgtest's LXC runner. Downgrading to
2.0.0~rc1 works again. The issue is that lxc-attach stops working
properly with input redirection.
# lxc-start -n a
Until 2.0.0~rc1 I could redirect lxc-attach's stdout:
# lxc-attach -n a runlevel /dev/null
Well, the point is not really about "simpler", but "might change/be
i18n'ed" and thus "is not predictable". However, this is really a side
issue to this report. The non-machine-readability was originally bug
1197754, but it applies to lxc-copy as well. If/once the message is
stable, I can parse
Public bug reported:
$ sudo lxc-copy -n adt-wily -e
Created adt-wily as clone of adt-wily_1WtXPo
This should say "Created adt-wily_1WtXPo as a clone of adt-wily". This
might seem trivial, but is highly relevant when trying to parse that
message to find out the cloned container name. This is
adt-build-lxc only uses LXC commands, it does not do any mounting by
itself. I use ecyrptfs /home as well, so this isn't broken in general.
If you can reproduce this, please attach the full output of the program
you were running, and the output of "journalctl -b" and /var/log/lxc/*.
** Package
pstart (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1541914
Title:
passwd depends on init-system-helpers
Public bug reported:
"lxc" now says "This is a transitional dummy package. It can safely be
removed.", but this isn't true:
$ sudo LANG= dpkg -P lxc
dpkg: dependency problems prevent removal of lxc:
lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43).
lxd depends on lxc.
juju-local depends
** Changed in: libcommons-dbcp-java (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to excalibur-logkit in Ubuntu.
https://bugs.launchpad.net/bugs/1539903
Title:
tomcat-8 in main
Fixed by https://launchpad.net/ubuntu/+source/libcommons-dbcp-
java/1.4-5ubuntu2
** Also affects: libcommons-dbcp-java (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libcommons-dbcp-java (Ubuntu)
Status: New => In Progress
** Changed in: libcommons-dbcp-java (Ubuntu)
** Changed in: jakarta-taglibs-standard (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to excalibur-logkit in Ubuntu.
https://bugs.launchpad.net/bugs/1539903
Title:
tomcat-8 in
** Changed in: bsh (Ubuntu)
Status: New => Fix Committed
** Changed in: bsh (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: excalibur-logkit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member
https://launchpad.net/ubuntu/+source/jakarta-taglibs-standard/1.1.2-4
moves to 3.1, but is currently depwaiting on libservlet3.1-java. It'll
start to build in about an hour.
** Changed in: jakarta-taglibs-standard (Ubuntu)
Status: New => Fix Committed
--
You received this bug
tus: New => Fix Committed
** Changed in: libcommons-logging-java (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to excalibur-logkit in Ubuntu.
https://bugs.launchpad.net/bug
There is nothing to fix in the autopgtest package, so moving to the more
generic project (which also encompasses the infrastructure to run
tests).
** Package changed: autopkgtest (Ubuntu) => auto-package-testing
** Changed in: auto-package-testing
Status: New => Incomplete
--
You
The error message is pretty clear. src/util/virsystemd.c does
if (virDBusCallMethod(conn,
NULL,
,
"org.freedesktop.machine1",
"/org/freedesktop/machine1",
ChristianEhrhardt [2016-02-19 14:02 -]:
> But due to that we found that in our case sse3 can't be guaranteed in the
> test environment - so we agreed on ubuntu-devel that we should detect and
> skip the test then to avoid false positives.
This indeed sounds like the most practical option.
apparmor was already uploaded:
https://launchpad.net/ubuntu/+source/apparmor/2.10-3ubuntu2
Unsubscribing sponsors.
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This was already uploaded without closing this bug:
https://launchpad.net/ubuntu/+source/php7.0/7.0.3-5ubuntu1
** Changed in: php7.0 (Ubuntu)
Status: New => Fix Released
** Changed in: php7.0 (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: php7.0 (Ubuntu)
This bug was fixed in the package jakarta-taglibs-standard - 1.1.2-4
Sponsored for Nish Aravamudan (nacc)
---
jakarta-taglibs-standard (1.1.2-4) unstable; urgency=medium
* Team upload.
* Removed the Servlet, JSP and EL API jars from the classpath specified
in the manifest
Serge Hallyn [2016-02-18 16:39 -]:
> Just to be sure, can you show the systemd version you were using here?
> The intent was to check with systemd from wily-proposed, with the
> regular wily kernel.
I thought the idea was to use a xenial kernel on wily?
--
You received this bug notification
Launchpad Bug Tracker [2016-02-17 19:37 -]:
> - Removal of LXC from 2.0 codebase
Does that mean "in favor of LXD", or "juju-local will be dropped"? I
guess/hope the latter, but making sure :-)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
> Hence my original proposed test for the file's existence.
This isn't very robust, as it blows up if the glob expands to more than
one file. That also Should Not Happen™, but I prefer to just quiesce the
error. I fixed that in http://anonscm.debian.org/cgit/collab-maint/pm-
** Bug watch added: Debian Bug tracker #706570
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706570
** Also affects: tcosmonitor (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706570
Importance: Unknown
Status: Unknown
** Changed in: tcosmonitor (Ubuntu)
I uploaded the adjusted patch to the trusty-proposed SRU queue.
** Tags added: hw-specific
** Changed in: pm-utils (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks Dirk! I committed http://anonscm.debian.org/cgit/collab-maint/pm-
utils.git/commit/?id=1b7600eca which is more liberal about the spelling
now.
** Changed in: pm-utils (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #773647
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773647
** Also affects: pm-utils (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773647
Importance: Unknown
Status: Unknown
** Changed in: pm-utils (Ubuntu)
bug 1539488 is nothing new and not related to systemd.
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers
Bas, any chance to test the update in -proposed so that we can release
that?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers won't start, need
Public bug reported:
Since version 2.0.0beta, lxc-destroy is now verbose even when calling
with --quiet:
$ sudo lxc-clone -o adt-xenial -n foo
$ sudo lxc-destroy --quiet -n foo
Destroyed container foo
Not a biggie, but it broke some expectation in autopkgtest. I'll work
around it there, but
Fix committed to Debian master branch: http://anonscm.debian.org/cgit
/collab-maint/init-system-helpers.git/commit/?id=628cb4328
Will backport to xenial.
** Changed in: init-system-helpers (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you
I now downloaded the current xenial/amd64 Launchpad chroot tarball
(which is really still wily), dist-upgraded that, and installed ofono,
and I can reproduce the regression with that.
** Changed in: init-system-helpers (Ubuntu)
Status: New => In Progress
** Changed in: init-system-helpers
I downloaded the current amd64 cloud image and dissected it with kpartx,
i. e. without booting. /usr/share/zoneinfo/Zulu is correct there, i. e.
127 bytes. So indeed it sounds like this file gets overwritten by cloud-
init.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
I think the bug is here in cloudinit/distros/__init__.py:
def set_etc_timezone(tz, tz_file=None, tz_conf="/etc/timezone",
tz_local="/etc/localtime"):
util.write_file(tz_conf, str(tz).rstrip() + "\n")
# This ensures that the correct tz will be used for the system
)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1543051
Title:
New helpers version fail on "unknown initscript&quo
I don't think we ever support running lxc-android-config *in* a
container, so this doesn't block the removal and merging the new init-
system-helpers.
** Changed in: lxc-android-config (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of
** Changed in: init-system-helpers (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1539016
Title:
Remove
https://platform-qa-jenkins.ubuntu.com/view/Upgrade/job/upgrade_ubuntu-
trusty-xenial-basic-amd64_qemu/74/console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1541914
Uploaded this. It would be great if you could test 2.3.10-1ubuntu2 and
confirm that this works now, as I don't use OpenVPN in that mode.
** Changed in: openvpn (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Yes, I think that makes sense, if that change is still
intended/sensible.
** Changed in: openvpn (Ubuntu)
Status: Confirmed => Triaged
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: openvpn (Ubuntu)
Milestone: None => ubu
Bug 1538960 is unrelated and a local configuration error.
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc
** Changed in: irqbalance (Ubuntu)
Milestone: ubuntu-15.11 => None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1454273
Title:
irqbalance should not run in container - add
Standard LXC images don't have irqbalance. Upstream says that in some
corner cases you might want it in containers too, and as you have to
explicitly install it I don't consider this high importance.
** Changed in: irqbalance (Ubuntu)
Importance: High => Medium
** Tags removed: systemd-boot
** Changed in: openvpn (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511524
Title:
OpenVPN PAM authentication broken on 15.10
The two suggested changes make sense; please drop "Requires=network"
completely, you only need the After=network.target.
But I can't get powernap to run at all in current xenial -- running
"sudo /usr/sbin/powernapd" in a VM or a container immediately exits. It
just writes the pid file and then
** Summary changed:
- openvpn fails after upgrade from 14.10 to 15.04
+ openvpn does not use OPTARGS from /etc/default/openvpn
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1454725
** Changed in: apport (Ubuntu)
Status: New => Fix Committed
** Changed in: memtest86+ (Ubuntu)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Low
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
** Changed in: flash-kernel
Added tasks for all packages in main and restricted. universe and
multiverse are still running.
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Also affects: memtest86+ (Ubuntu)
Importance: Undecided
Status: New
** Also affects: flash-kernel (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1539016
Title:
Remove /bin/running-in-container
To
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1539016
Title:
Remove /bin/running-in-container
To
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Changed in: flash-kernel (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
The only place known to me that does that is /etc/init.d/hwclock.sh,
which is from util-linux. Something similar is also done under upstart
from /etc/init/hwclock.conf where hwclock is called with --systz. This
quite plausibly opens rtc as well.
However, these two scripts aren't being run at all
dy use, so
let's cut out that delta.
I'm currently running an archive grep to find remaining users.
** Affects: init-system-helpers (Ubuntu)
Importance: Low
Assignee: Martin Pitt (pitti)
Status: In Progress
** Changed in: init-system-helpers (Ubuntu)
Status: New =>
*** This bug is a duplicate of bug 1032823 ***
https://bugs.launchpad.net/bugs/1032823
** This bug has been marked a duplicate of bug 1032823
package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
--
You
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1539016
Title:
Remove
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Debian Bug tracker #813007
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813007
** Also affects: gnupg2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813007
Importance: Unknown
lxc-android-config will be fixed by landing
https://code.launchpad.net/~vorlon/lxc-android-config/apport-job-
cleanup/+merge/274497
** Changed in: lxc-android-config (Ubuntu)
Status: New => Fix Committed
** Changed in: lxc-android-config (Ubuntu)
Status: Fix Committed => In
Hello Kees, or anyone else affected,
Accepted openssh into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:6.6p1-2ubuntu2.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
restarting lxcfs helps: The hanging container pid 1 and lxc-stop
finally finish, and the container stops.
** Package changed: lxc (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Sponsored, thank you!
** Changed in: openvpn (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1536568
Title:
please merge openvpn from
Oh, I see what's wrong: They run /var/lib/juju/init/juju-agent-martin-
local/exec-start.sh, which runs
/home/martin/.juju/local/tools/machine-0/jujud
This can't work, as my home directory does not exist until I log in
(it's encrypted). This will equally affect /home on NFS and the like.
* Do
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: rsyslog (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Public bug reported:
I have juju-local deployed on current xenial. This works fine right
after installation (except for bug 1534106), but after a fresh boot
"juju status" hangs. I have two failed units:
$ systemctl --failed
UNITLOAD ACTIVE SUBDESCRIPTION
●
Public bug reported:
Please drop the "Depends: rsyslog-gnutls". rsyslog is not a required
part of the installation any more as we have the systemd journal now.
With enabling persistent journal having rsyslog is just a waste as it
logs everything again but in a much less convenient way.
I
As another data point, I don't see this on the s390x boxes which are
also running xenial userspace with the same LXC setup, but a 4.3 kernel.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
Since I upgraded our armhf autopkgtest boxes from wily to xenial, I very
often get eternal hangs on lxc-stop:
adt-virt-lxc-egctlo RUNNING 10.0.3.154 - - NO
root 15766 0.0 0.0 5044 1488 ?SJan19 0:00 lxc-
stop --kill --name
** No longer affects: init-system-helpers (Ubuntu)
** No longer affects: init-system-helpers (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1533839
Title:
d in: systemd (Ubuntu Wily)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers won't start, need
Tested it myself now as well. I uploaded it to the wily-proposed SRU
queue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1533833
Title:
unprivileged lxc containers won't start, need
** Changed in: systemd (Ubuntu Wily)
Status: New => Triaged
** Summary changed:
- unprivileged lxc containers won't start
+ unprivileged lxc containers won't start, need to put sessions into "pids"
cgroup controlelr
** Summary changed:
- unprivileged lxc containers won't start, need
Really shabby workaround for xenial: Change
/lib/systemd/system/rsyslog.service like this:
[Service]
Type=oneshot
ExecStart=/bin/true
RemainAfterExit=yes
On that note, it would really be nice if juju-local would not require
rsyslog. We have the systemd journal, so having rsyslog installed is
Public bug reported:
installing juju-local pulls in rsyslog (at least on current xenial).
When doing
- juju init
- edit ~/.juju/environments.yaml to set "local" as default
- juju boostrap
this creates a file /etc/rsyslog.d/25-juju-USERNAME-local.conf and
restarts rsyslog. rsyslog then crashes
This is quite a nuisance to do with current apt, but this should do it:
http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=7429f79124
** Project changed: auto-package-testing => autopkgtest (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
As I explained, the notion of "the last thing during boot" is not well-
defined with a partially ordered and parallel init system like systemd
or upstart (or even sysvinit+startpar).
So as long as cloud-init.service declares itself to run after rc-
local.service, then rc-local.service necessarily
> So as long as cloud-init.service declares itself to run after rc-
local.service
Sorry, I meant cloud-final.service.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1468103
Tiago, your service file has even weaker dependencies like the standard
rc-local.service, so it'll run even earlier. It's not good advice to
create blanket "wrappers" around shell scripts without specifying any
dependency.
--
You received this bug notification because you are a member of Ubuntu
> lxc-clone -s -o adt-xenial -n x1
> does that snapshot the way you want?
This seems to work on btrfs, but on other file systems this uses
overlayfs which I'd rather avoid (it breaks too many things).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
1 - 100 of 1675 matches
Mail list logo
