** Package changed: dovecot (Ubuntu) => apparmor (Ubuntu)
--
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/1512131
Title:
Apparmor complains about multiple /run/dovecot file access
To
** Changed in: trove
Assignee: khushbu (khushbuparakh) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1451134
Title:
Default connection parameters
Marked this bug as invalid because this is just a config change. Let me
know if there are questions raised. Thanks.
** Changed in: trove
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in
@oleg,
yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks a lot Jeremy for the the link and clarification.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1422046
Title:
cinder backup-list is always listing all tenants's
sponsored to precise/trusty/vivid (though i'm unsure vivid is useful
since it's not the current stable)
--
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/1481388
Title:
NTP :
Correct, we consider that latter case a "security hardening opportunity"
and I'm triaging this report as one now (class D in our taxonomy
https://security.openstack.org/vmt-process.html#incident-report-taxonomy
). Depending on severity and available time from editors in the Security
Team, these
looks good to me.
--
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/525674
Title:
apt-check hangs, preventing login via SSH
To manage notifications about this bug go to:
** No longer affects: lxc (Ubuntu)
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
To manage
** No longer affects: trove
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1451134
Title:
Default connection parameters fails when running dbsync
To manage notifications
This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.14
---
cloud-init (0.7.5-0ubuntu1.14) trusty; urgency=medium
* d/patches/lp-1177432-same-archives-as-ubuntu-server.patch: use the
same archive pockets as Ubuntu Server (LP: #1177432).
-- Ben Howard
The verification of the Stable Release Update for cloud-init 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
Public bug reported:
I'm investigating lxc-tests and have very little idea what they actually
do. I had hoped to read a man page, or even just pass --help to them to
get some idea of what each is actually doing.
For example, lxc-test-apparmor, I know it does something with apparmor,
but no idea
Public bug reported:
I ran lxc-test-checkpoint-restore and it failed. So I decided to try
one additional attempt to verify the failure. However now I am unable
to re-run the test because apparently the container already exists
(previous test did not clean up after itself), however, lxc list
This bug was fixed in the package cloud-init - 0.7.7~bzr1091-0ubuntu11
---
cloud-init (0.7.7~bzr1091-0ubuntu11) vivid; urgency=medium
* d/patches/lp-1177432-same-archives-as-ubuntu-server.patch: use the
same archive pockets as Ubuntu Server (LP: #1177432).
-- Ben Howard
** Description changed:
SRU JUSTIFICATION
[IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" ==
"nofail." However, with Ubuntu 15.10, this is no longer the case. As a
result, snapshotted, stopped and restarted, or migrated Cloud instances
may fail to boot if the
This bug was fixed in the package cloud-init - 0.7.7~bzr1149-0ubuntu3
---
cloud-init (0.7.7~bzr1149-0ubuntu3) wily; urgency=medium
* d/patches/lp-1177432-same-archives-as-ubuntu-server.patch: use the
same archive pockets as Ubuntu Server (LP: #1177432).
-- Ben Howard
This bug was fixed in the package cloud-init - 0.7.7~bzr1155-0ubuntu1
---
cloud-init (0.7.7~bzr1155-0ubuntu1) xenial; urgency=medium
* New upstream snapshot.
* cc_mounts: use 'nofail' rather than 'nobootwait' if system uses systemd.
(LP: #1514485).
-- Scott Moser
** Changed in: ceph (Ubuntu Vivid)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1507244
Title:
Missing erasure coding plugins for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ceph (Ubuntu Vivid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
With headers left in place. Thanks for your help coreycb!
** Patch added: "python-novaclient_2.22.0-0ubuntu2.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1499510/+attachment/4516345/+files/python-novaclient_2.22.0-0ubuntu2.debdiff
--
You received this bug notification because you
The download template (which is recommended) installs no ssh and no
ubuntu password.
--
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/1514080
Title:
lxc-templates lacks template for
Public bug reported:
on a default 15.10 installation, I have installed lxc-tests and am
running through them individually.
lxc-test-checkpoint-restore fails to run because the package criu is not
installed
ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
/usr/bin/lxc-test-checkpoint-restore:
The behavior of the test is perfectly correct.
This test depends on a CRIU version which can't be found in the Ubuntu
archive and criu itself isn't available on most architectures.
As mentioned in the other bug report, lxc-tests is meant to be used by
autopkgtest through our autopkgtest test
Pushed to all packaging branches.
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
--
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/1514942
Title:
lxc-tests no runtime
I'll update the package description to make it clear that users aren't
supposed to install that package :)
--
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/1514942
Title:
lxc-tests no
The lxc-tests package was introduced so that autopkgtest can run all the
LXC tests on upload through the debian/tests/exercise script.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
@Serge,
Thanks for the clarification; I'll revert the status to un-marked.
** No longer affects: lxc (Ubuntu)
--
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/1480411
Title:
rm -r *
Suspected duplicate with Bug #1514234 for EC2.
--
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/1514485
Title:
[SRU] cloud-init should use "nofail" instead of "bootwait"
To
Thanks, indeed that's an issue introduced when switching away from
upstart, I've changed the package back to use the Debian version of the
script, which works, and forwarded them your suggested change on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804705
** Bug watch added: Debian Bug
Public bug reported:
Ran the ste lxc-test-checkpoint-restore and that failed, but there is no
explanation in the output as to why it failed. All the output I was
able to create says it created the container fine, but then just failed
for some reason:
I: Configuring libsemanage1:amd64...
I:
Hello Ben, or anyone else affected,
Accepted cloud-init into wily-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.7~bzr1149-0ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
On Fri, May 29, 2015 at 7:32 AM, Mario Splivalo
wrote:
> Hi, Jeff.
>
> Is this still the issue? I just tried deploying maas with ubuntu trusty,
> installing just 'maas' package, which then install everything that was
> needed (incuding maas-dns). The maas version in
*** This bug is a duplicate of bug 1514558 ***
https://bugs.launchpad.net/bugs/1514558
Looks like this is the same as bug 1514558. (Maybe created twice by
Launchpad, it seems to do that sometimes.) I've taken the liberty of
marking this as a duplicate.
** This bug has been marked a duplicate
Hi,
What version of criu do you have installed? What's the host? Can you
show the output of /tmp/checkpont/{dump,restore}.log after the failure?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Please refer the fix I made for Fedora
http://pkgs.fedoraproject.org/cgit/open-vm-
tools.git/commit/?id=17141dd91c321fc41f7d1874d64e8ea7d055fcc9.
It is a simple packaging step to be done in your pre-uninstall step.
Could you please look into it?
--
You received this bug notification because you
As Jeff said, I believe this is fixed in MAAS 1.7.
I worked on a related race condition having to do with migrating MAAS-
managed BIND variables to the MAAS database.
If you are installing MAAS on a machine which will *not* host the MAAS
database, there is still somewhat of a race condition, in
Confirmed on Azure. Marking as verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1514485
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1266840
Title:
maas-dns failed to install completely on Trusty
To
** Changed in: ntp (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1125726
Title:
boot-time race between /etc/network/if-up.d/ntpdate and
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
That was a red herring, actually. The cause of failure appears to be
the next line.
After fixing that so that the mkdir succeeds, it still fails on
Failed to allocate manager object: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:~brian-turek/ubuntu/trusty/openvswitch/fix-
for-1314887
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1314887
Title:
ifupdown hook
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
I had missed restart lxc-net.
Unfortunately, that didn't make any difference.
kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log
--logpriority 3 -F
lxc-start: conf.c: instantiate_veth:
The verification of the Stable Release Update for cloud-init 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
This bug was fixed in the package cloud-init - 0.7.7~bzr1149-0ubuntu4
---
cloud-init (0.7.7~bzr1149-0ubuntu4) wily; urgency=medium
* d/patches/lp-1514485-nofail_for_ephemeral_mounts.patch: Use nofail
mount option in fstab instead of bootwait (LP: #1514485).
-- Ben Howard
Public bug reported:
1)
Description:Ubuntu 15.10
Release:15.10
2)
openvswitch-testcontroller:
Installed: 2.4.0-0ubuntu4
Candidate: 2.4.0-0ubuntu4
Version table:
*** 2.4.0-0ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
100
1. Disabling Glance API v1 in glance-api.conf prevents nova from doing any
sapshots at all. From nova-api.log indicates it's insisting on v1:
This issue has got reproduced in our setup(Kilo).
2.Talking about second scenario creating image using Glance CLI by API v1 and
v2 owner attribute is
Yes, confirmed. After fixing the Glance configuration as noted in
comment #1, also image creations via Glance CLI using API v1 do assign
ownership correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Sure, I completely agree with that.
There should be a way to differentiate security issues in terms of
"vulnerability" (which is not the case here) and security issues in
terms of "risks of destroying data" due to a bug (which is the case
here).
--
You received this bug notification because you
thank you for your report, could you report that bug to debian as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1514431
Title:
vsftpd does not support non-ASCII (UTF8)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1477198
Title:
Stop doesn't work on 14.04 (start-stop-daemon
This bug does still affect lxc on Ubuntu Trusty when using the 3.13
kernel in conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
** Also affects: lxc (Ubuntu)
Importance
This bug does still affect lxc when using kernel 3.18 or above in
conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
** Also affects: lxc (Ubuntu)
Importance: Undecided
** Changed in: haproxy (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1477198
Title:
Stop doesn't work on 14.04 (start-stop-daemon
This bug does still affect lxc (as per comment #5) when using kernel
3.18 or above in conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
--
You received this bug
Public bug reported:
At present, if a system is installed onto a bcache'd device, it will
fail at first boot as the device will not be recognised. It is necessary
to chroot into the system and install bcache-tools manually. This should
be handled by the installer, as it would be for other exotic
With cgfs i actually wasn't able to start the container in the first
place. I've now fixed at least that.
it wasn't the mkdir which was failing, but the subsequent attempt to
attach itself to it. That's because while cgmanager used to chown the
child files after creating a directory for us,
Public bug reported:
OS : Ubuntu 14.04 LTS server i386 ( with all packages obtained from Ubuntu
repos )
Kernel : Linux 3.13.0-66-generic, i686
Running StrongSwan 5.1.2.
Found it was necessary to edit the apparmor profile to permit
"strongswan-plugin-farp" to
be loaded at 'ipsec start'.
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757
** This bug has been marked a duplicate of bug 1407757
multi-arch packages cannot be installed due to dpkg wrongly detecting them
as already installed
--
You received this bug notification because you
** Changed in: rpcbind (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1312976
Title:
Make NFS client/server work under systemd
To
This can be trivially fixed by adding
noload => res_pjsip.so
in the modules section of etc/asterisk/modules.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Title:
Public bug reported:
can't install this package in lubunto 14. osgeo live 9
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: odbc-mdbtools:amd64 0.7.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27
Uname: Linux 3.13.0-67-generic x86_64
ApportVersion:
Doh', it's because I had a total brainfart while writing 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/1514690
Title:
rebooting container with systemd >= 226 fails to create
When I test this using cgfs-backed lxcfs, the mkdir of init.cgroup fails after
setresuid(10, 10, 0).
This is odd since doing it manually using sudo -u \#10 -g \#10 mkdir
/sys/fs/cgroup/systemd/lxc/x1/x works fine.
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nspr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nspr in Ubuntu.
https://bugs.launchpad.net/bugs/1401419
** Changed in: bacula (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1299249
Title:
bacula-common: bsmtp: bsmtp.c:377 Fatal
What does
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo netstat -lap| grep LISTEN
show now that you've updated bind9's configuration?
** This bug is no longer a duplicate of bug 1240757
Bridge not created if
This is still the case in Ubutnu 14.04 LTS.
** Changed in: xen (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/966957
Title:
Could not change
[Expired for keystone (Ubuntu) because there has been no activity for 60
days.]
** Changed in: keystone (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
[Expired for cgroup-lite (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cgroup-lite (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgroup-lite in Ubuntu.
I believe what's happening is that systemd tries to mkdir init.scope
before the directory has been deleted and gets -EEXIST; then the kernel
finishes deleting it, then systemd tries to move itself to it but it is
gone.
Waiting for one more debugging build to verify.
--
You received this bug
72 matches
Mail list logo