I attempted to fix this, but haven't gotten anywhere. I am seeing the
following errors:
Removing maas-region-controller (1.8.0~beta2+bzr3777-0ubuntu1) ...
* Stopping web server apache2
*
I think this is a bug with dbconfig-common. It looks like Zbbix is still
having this issue:
https://support.zabbix.com/browse/ZBXNEXT-2587
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~mpontillo/maas/packaging-fix-db-purge
** Changed in: maas
Importance: Medium = High
** Changed in: maas
Assignee: (unassigned) = Mike Pontillo (mpontillo)
** Changed in: maas
Milestone: None = 1.8.0
** Changed in: maas
Status: New = Triaged
--
You
I'm running Precise. The 'Pass lo as faked tundev to NM' patch results
in Network Manager setting a 172.16.X.X IP on lo on VPN connect. Since
this replaces 127.0.0.1, other software breaks. Then, on VPN
disconnection, Network Manager takes lo down.
This can be trivially confirmed by running
I just saw this one again. I found a relevant discussion here:
https://lists.alioth.debian.org/pipermail/dbconfig-common-
devel/2006-September/000627.html
Here's the relevant quote from Sean Finney (the maintainer of dbconfig-
common):
i can reproduce your problem... looking in my postgres
*** This bug is a duplicate of bug 1044559 ***
https://bugs.launchpad.net/bugs/1044559
Note: If you try to purge the database, it actually fails in this case,
and the database is left intact.
See comments on bug #1044559.
** Also affects: maas
Importance: Undecided
Status: New
**
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntuid=07d6481d7a7a5
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
As for what creates the Before=network.target for networking.service
(aka /etc/init.d/networking): this is defined in /etc/insserv.conf.
We should definitely not be blocking network.target indefinitely on
boot waiting for the results of /etc/init.d/networking.
Agreed. Conceptually we should
With bug 1440978 fixed locally I can now reproduce this.
ifup@eth0.service indeed takes some 3 minutes to time out, then the
getty finally appears. So let's run the ifup@ in the background; at
least in Ubuntu we didn't block on these under upstart either, and as I
wrote before the main reason for
** Changed in: juju-core
Status: In Progress = Fix Committed
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: juju-core (Ubuntu)
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** No longer affects:
** Changed in: nginx (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1438440
Title:
nginx-extras does not include Chunkin module
To manage
This should be fixed in current vivid.
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
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/1376717
Title:
lxc fails to
Chunkin has been replaced by the chunked module which is enabled by
default. This is present since nginx 1.3.9.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1438440
Title:
Public bug reported:
$ sudo lxc-destroy -n adt-vivid
[sudo] password for martin:
lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev:
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev:
failed
Public bug reported:
With latest vivid's LXC, starting a vivid container now fails on
mounting the cgroups:
$ sudo lxc-create --name=v -t ubuntu -- -r vivid
$ sudo lxc-start -n v -F
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
systemd 219 running in system mode. (+PAM
This is just cosmetical. We actually do want to continue upstart support
at least until the next LTS (and also for Ubuntu touch), so we can't
just rip that out wholesale yet. But it shouldn't produce that confusing
error for sure.
** Changed in: openssh (Ubuntu)
Importance: Undecided = Low
**
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like this is coming from the source tree in ext/rack/example-
passenger-vhost.conf which is from upstream, so this bug should be
reported upstream. Based on a look at the source it looks like this bug
also
Hello Rafael,
Sorry for the late reply, We tested the PPA and it's good, Could you
please create a SRU with it.
Thanks,
Kamal
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
Tag block-proposed has been removed to be able to update the package in vivid.
We don't plan to update trusty package with 1.22.0 for now.
I'll post an update to this bug when we make decision on package update in
trusty.
** Tags removed: block-proposed
--
You received this bug notification
So what is the new recommended way to setup cgroups that should always
exist even after a reboot?
I found a lot of documentation about cgroups.conf but it simply does not
work on 14.04.
Or are cgroups generally a concept that is being abandoned? Is there an
alternative method to limit resources?
Juju 1.22.0 can't provision instances which run vivid because it doesn't
support systemd. Systemd support has been introduced in Juju 1.23 and we
plan to package this release when it becomes stable (now in beta).
However, I think that having 1.22 in vivid is much better than having
Juju 1.20 (what
I'm using cloud-init on CentOS, but would really like this functionality
as well. For the time being, I'll be trying to reuse the upstream AWS
pieces.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
At the least can we update the documentation to reflect this change?
In particular the deb package that states:
THIRD PARTY MODULES: Auth PAM, Chunkin,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
13:40 strikov rbasak: i did a research on CVE attached to the bug and came to
conclusion that it was attached incorrectly
13:41 strikov rbasak: this CVE is about a different thing and I have no idea
why it was attached
Looking at the CVE details I agree, so unlinking.
** CVE removed:
trusty-backports verified
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1420572
Title:
[SRU] race between neutron-ovs-cleanup and nova-compute
To manage notifications about this bug
On Tue, Apr 07, 2015 at 02:35:35PM -, Martin Pitt wrote:
Steve Langasek [2015-04-07 14:22 -]:
I'm not sure what you mean by this. We absolutely did block on our network
interfaces when using upstart; just with a 2 minute timeout for any
misconfigured interfaces.
Right, but that
Please can you explain why you think this is a bug? As far as I
understand, you now need to install upstart-sysv if you want to keep
your system running upstart on Vivid. But ordinarily users should not be
affected because they should all have been migrated to systemd, unless
there is a bug that
http://anonscm.debian.org/cgit/collab-
maint/nginx.git/commit/debian/control?id=a5bbc3a1c68241e0db0257bfa34c9ce55c090285
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1438440
Title:
Thank you Kamal,
I'll be providing the debdiffs and asking for sponsorship/upload for the
SRU real soon.
Cheers,
Rafael
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
https://bugs.launchpad.net/bugs/1409904
We have a similar problem with `seabios' but upgrading to 1.7.5 is not
helping. https://bugs.launchpad.net/fuel/+bug/1435501
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1318803
trusty-proposed verified
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1420572
Title:
[SRU] race between neutron-ovs-cleanup and nova-compute
To manage notifications about this bug
Public bug reported:
Today I encountered a bug during the installation of mysql-server-5.6
(5.6.23-1~exp1~ubuntu5).
The output log is:
Setting up mysql-server-5.6 (5.6.23-1~exp1~ubuntu5) ...
2015-04-07 14:45:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is
deprecated. Please use
I got the same problem :/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1441177
Title:
mysql-server-5.6 (5.6.23-1~exp1~ubuntu5) installation problem on Vivid
To manage
Thanks @Michael
@Thomas, this must have taken about 2 mins to fix and would have saved
me hours of issues - this is not a typo but wrong documentation, anyhow
- thanks for at least letting me know.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@mpchlets
I don't make SRU policy I only follow it. This is one minor package
listing that is incorrect - ultimately it affects a very very limited
portion of the package and there isn't really a bug needing fixing here.
The policy is that it actually has to fix a substantial bug. In the
past
mpchlets:
That'd be a different bug, but that type of bug does not qualify for an
SRU or any updates in stable releases. It's likely this can be changed
later in Debian or elsewhere, if it hasn't already been changed, however
it will not get an update in stable releases due to the fact that
juju 1.22.0 is fit for purpose. The client can work with agents and
servers in public and private clouds. The Juju charm store only supports
LTS services. It is not possible to place a vivid charm in the store.
The only vivid users impaired by missing systemd support are charm
developers and
I've replaced the topic, and the description a little, to match the
'issue' per comment #2. I've also updated the bug status to Won't Fix
since this doesn't qualify for any SRU.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in
On Tue, Apr 07, 2015 at 06:43:35AM -, Martin Pitt wrote:
So let's run the ifup@ in the background; at least in Ubuntu we didn't
block on these under upstart either,
I'm not sure what you mean by this. We absolutely did block on our network
interfaces when using upstart; just with a 2
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.6 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
Steve Langasek [2015-04-07 14:22 -]:
I'm not sure what you mean by this. We absolutely did block on our network
interfaces when using upstart; just with a 2 minute timeout for any
misconfigured interfaces.
Right, but that should only be done by services which depend on
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
I have found some additional information on how this bug would be
reproduced, let me explain:
If you visit this URL: http://cdimage.ubuntu.com/ubuntu-
gnome/releases/15.04/ , there are four alpha/beta releases of 15.04 in
that directory: alpha-1, alpha-2, beta-1 and beta-2.
Now check the
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers
--
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/1439988
Title:
package init-system-helpers 1.22ubuntu4
Hm, still occurring, armhf-only. I'll need to find a working armhf to
test on.
I'm confused about the errors tracking page though - it seems to say
this happens only in vivid using 0.33-2. That is a very old version.
** Changed in: cgmanager (Ubuntu)
Status: New = Fix Released
**
** Tags added: systemd-boot
--
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/1436691
Title:
Essential files are missing
To manage notifications about this bug go to:
** Package changed: upstart (Ubuntu) = init-system-helpers (Ubuntu)
** Changed in: init-system-helpers (Ubuntu)
Assignee: Adam Conrad (adconrad) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers
You have been subscribed to a public bug:
1)
Description:Ubuntu Vivid Vervet (development branch)
Release:15.04
2)
upstart:
Installed: 1.13.2-0ubuntu9
Candidate: 1.13.2-0ubuntu10
Version table:
1.13.2-0ubuntu10 0
500 http://mirror.cloud.online.net/ubuntu-ports/
init-system-helpers should also get a Replaces/Breaks on the old
upstart-bin package.
Right. But instead it Breaks/Replaces upstart instead, which is wrong.
This mistake was accidentally uploaded because of some coordination
issues. Confusingly both upstart-bin 1.13.2-0ubuntu9 and upstart
Blueprint changed by Corey Bryant:
Work items changed:
Work items for ubuntu-15.01:
Try Mojo for Openstack bundle and HA testing: DONE
Write Mojo spec and helpers for Openstack Deploys: DONE
Add Mojo support into OSCI: DONE
Add support for Ceph Rados gw HA: DONE
Add unicast support to
*** This bug is a duplicate of bug 1436956 ***
https://bugs.launchpad.net/bugs/1436956
As far as I know, in the scenario I described in my previous comment,
the apt-get dist-update process will NOT require the install of either
systemd-sysv or upstart-sysv. It will just update upstart to the
Some of this likely is due to (acknowledged) basic thread-safety issues
in libdbus, and there is discussion on the dbus mailing list about how
to address it (in libdbus)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
Specifically you seem to have deleted essential directories such as
*** This bug is a duplicate of bug 1436956 ***
https://bugs.launchpad.net/bugs/1436956
** Changed in: upstart (Ubuntu)
Status: Confirmed = Invalid
** This bug has been marked a duplicate of bug 1436956
Critical system files such as /sbin/shutdown and /sbin/init missing after
** Changed in: cgmanager (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1421068
Title:
task can administer some sibling cgroups
The idea is that the Priority: required init package is always
installed, which depends on systemd-sysv | upstart-sysv. upstart-bin is
history, that's upstart now (and as you already found out, upstart-
sysv now contains /sbin/init).
Any idea how init got missing on your system?
** Summary
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers
--
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/1436956
Title:
Critical system files such as
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
I plan to change the status of this bug for 12.04 (precise) and 14.04 (trusty)
to Won't Fix.
In this comment I want to explain why I came to this decision.
This bug had CVE-2013-4449 linked to it. I don't think that this CVE is
relevant because the patch proposed in this bug doesn't resolve the
This bug was fixed in the package juju-core - 1.22.0-0ubuntu1
---
juju-core (1.22.0-0ubuntu1) vivid; urgency=medium
* New upstream release (LP: #1416051).
* d/patches/fix-detect-new-release.patch: Added upstream patch to redeem
the ability to handle future Ubuntu releases
This bug was fixed in the package init-system-helpers - 1.22ubuntu8
---
init-system-helpers (1.22ubuntu8) vivid; urgency=medium
* Make init Essential: yes again, it's the only way to guarantee a
sane upgrade path for people without ubuntu-minimal (LP: #1436956)
-- Adam Conrad
This bug was fixed in the package init-system-helpers - 1.22ubuntu8
---
init-system-helpers (1.22ubuntu8) vivid; urgency=medium
* Make init Essential: yes again, it's the only way to guarantee a
sane upgrade path for people without ubuntu-minimal (LP: #1436956)
-- Adam Conrad
** Changed in: init-system-helpers (Ubuntu)
Assignee: (unassigned) = Adam Conrad (adconrad)
** 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
Even with qemu-img installed, the test fails. This appears to be due to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680307
Please see this demonstration of the busted qemu-img on Precise:
http://paste.ubuntu.com/10764770/
** Bug watch added: Debian Bug tracker #680307
On 04/07/2015 01:32 PM, Oleg Strikov wrote:
Client may crash itself
by passing incorrect cipher suite to the API. While that's sad, it
doesn't crash slapd itself
To the contrary, it certainly does crash slapd itself. Anyone
upgrading will at some point silently switch from a slapd that
Hello Chris,
This bug has been verified against keystone 1:2014.1.4-0ubuntu2.
Thanks,
Corey
** 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 keystone in Ubuntu.
Hello Chris,
This bug has been verified against the 2014.1.4-0ubuntu2 versions of the
affected packages.
Thanks,
Corey
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1436691 ***
https://bugs.launchpad.net/bugs/1436691
** This bug has been marked a duplicate of bug 1436691
init package is missing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** This bug is no longer a duplicate of bug 1436956
Critical system files such as /sbin/shutdown and /sbin/init missing after
updating upstart
** Changed in: init-system-helpers (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member
Public bug reported:
I'm using Ubuntu 15.04 dev with init 1.22ubuntu8 and on executing apt-
cache show init I'm seeing that the Description-en field says that
there are 3 available init systems while it lists only 2.
** Affects: init-system-helpers (Ubuntu)
Importance: Undecided
@Martin Pitt: In my case this happened likely because I'm configuring my
system to be minimalist. This means that I'm removing all packages which
are not needed (and init wasn't needed for a working system). The
upgrade caused then that the new package upstart-sysv hasn't made it to
such systems
Hello Chris,
This bug has been verified against nova 2014.1.4-0ubuntu2 for trusty.
Thanks,
Corey
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1420572
Title:
[SRU] race between
Hi Chirs,
I have installed the package - version 1:2014.2.2-0ubuntu2. And I don't
see the above mention problem anymore. Thanks for the fix.
Thanks,
Liang
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
This bug was fixed in the package systemd - 219-6ubuntu2
---
systemd (219-6ubuntu2) vivid; urgency=medium
* Merge fixes from Debian experimental branch.
* ifup@.service: Run ifup in the background during boot, to avoid blocking
network.target. (LP: #1425376)
* Drop
Public bug reported:
---
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: puppetmaster-common (not installed)
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.14.7-0ubuntu8.2
Architecture:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1441354
Title:
package puppetmaster-common (not installed) failed to install/upgrade:
tentata
** Tags removed: need-duplicate-check
--
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/1441369
Title:
package init-system-helpers 1.22ubuntu5 failed to install/upgrade: a
** Information type changed from Private Security to Public
--
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/1441369
Title:
package init-system-helpers 1.22ubuntu5 failed
Public bug reported:
numactl sometimes crashes when enumerating hardware:
root@node1:~# numactl --hardware
available: 648 nodes (0-647)
Segmentation fault
Further analysis shows that libnuma is using an uninitialised pointer,
which value depends on program layout. When layout is sufficiently
FYI, a potentially-related precise rbd libvirt issue:
https://bugs.launchpad.net/charms/+source/nova-compute/+bug/1427660
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1440948
Do you know if a CVE has been assigned to this issue? I don't directly
see how it could be used to cross privilege boundaries. Is there
something I've missed?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
A CVE hasn't been assigned.
Presumably an attacker could manipulate the environment before an
application's libnuma call to have the uninitialised pointer point to
information in memory they'd like to extract, or cause a denial.
If an application that gained privileges (capabilities, setuid etc)
I've attached the debdiff with the fix.
** Patch added: debdiff with upstream fix
https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1441388/+attachment/4369005/+files/numactl_2.0.9%7Erc5-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server
*** This bug is a duplicate of bug 1426994 ***
https://bugs.launchpad.net/bugs/1426994
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1426994, so it is being marked as such. Please
Thanks Jason for confirming! I'm closing that then. Please reopen if you
run into this again.
** Changed in: qemu (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
The attachment debdiff with upstream fix 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 tag, and
87 matches
Mail list logo
