Public bug reported:
[Impact]
Heat uses 'scheduler hints' to instruct the cloud that some resources
need special treatment, for instance that two cinder volumes have to be
created on different backends.
Without this patch, cinder client is broken and hints aren't properly
formatted leaving witho
** Patch added: "lp_1404110_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-cinderclient/+bug/1404110/+attachment/4283947/+files/lp_1404110_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cinde
** Attachment added: "test_scheduler_hints.py output"
https://bugs.launchpad.net/ubuntu/+source/python-cinderclient/+bug/1404110/+attachment/4283948/+files/test_scheduler_hints.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pyt
Additional notes:
Disabling HTTP-level compression by default is not a decent option to
solving this. Mitigation is mostly on an application level, then,
however there are third-party modules that can be included (in the
Universe binaries) which would add length hiding as a potential
mitigation m
** Tags removed: need-duplicate-check
--
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/1404052
Title:
package nova-common 1:2014.2.1-0ubuntu1 failed to install/upgrade:
subprocess inst
Public bug reported:
Tried to install nova on an up to date 14.10 Ubuntu version.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nova-common 1:2014.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: nvi
Public bug reported:
We have released LXC 1.0.7 upstream:
https://linuxcontainers.org/lxc/news
This will be the third upstream bugfix release to hit trusty. The
upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here:
https://lists.ubuntu.com/archives/technical-b
@marco-bettio,
I am not being able to backtrace your submitted crash, Did you removed the
hand-compiled version?
Could you check that are you using the latest archive package version
squid_3.3.8-1ubuntu6.2_amd64 ?
Thanks.
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1397130 ***
https://bugs.launchpad.net/bugs/1397130
This bug was fixed in the package libvirt - 1.2.8-0ubuntu18
---
libvirt (1.2.8-0ubuntu18) vivid; urgency=medium
* mutex cgmanager actions (Thanks to Don Bowman for finding the cause)
(LP:
This bug was fixed in the package libvirt - 1.2.8-0ubuntu18
---
libvirt (1.2.8-0ubuntu18) vivid; urgency=medium
* mutex cgmanager actions (Thanks to Don Bowman for finding the cause)
(LP: #1397130) (LP: #1367702)
-- Serge HallynThu, 18 Dec 2014 13:28:03 -0600
** Changed in
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => kilo-1
--
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/1380792
Title:
reques
** Branch linked: lp:ubuntu/trusty-proposed/pacemaker
** Branch linked: lp:ubuntu/utopic-proposed/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1382842
Title:
pacemake
** Branch linked: lp:ubuntu/trusty-proposed/pacemaker
** Branch linked: lp:ubuntu/utopic-proposed/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemake
Stephane
The network itself is pretty stock; the mtu on the switches is set to
9000; other than that its pretty much the standard cisco configuration
for the switch model.
I have the full details (but can't put them here :-)).
--
You received this bug notification because you are a member of Ub
** Changed in: libvirt (Ubuntu)
Status: Incomplete => In Progress
** Also affects: libvirt (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Trusty)
Importance:
Hello Rafael, or anyone else affected,
Accepted pacemaker into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-1ubuntu2.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new pack
Hello Ante, or anyone else affected,
Accepted pacemaker into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-1ubuntu2.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new packag
Hello Rafael, or anyone else affected,
Accepted pacemaker into utopic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-4ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new pack
Hello Ante, or anyone else affected,
Accepted pacemaker into utopic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/1.1.10+git20130802-4ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new packag
We need to decide how we're going to handle this.
The GCE tooling (and therefore documentation) suggest that if instance-
level keys are supplied, then project-level keys are disregarded. Do we
want to mirror this?
I'm torn on this one. On the one hand, we already don't match the GCE
docs in the
Discussed on IRC again. cgmanager changes the systemd controller and
thus interferes with systemd. Also, in Ubuntu (not upstream or in
Debian), we have a systemd patch to put logind sessions into all cgroup
controllers (not just the systemd one) for supporting LXC user
containers, which would poten
I installed the archive package instead and I have this error in the
log:
2014/12/18 16:32:35.829| cc(263) Recv: 32 bytes from [fe80::206:4fff:fe9b:d135]
2014/12/18 16:32:40.831| cc(263) Recv: 24 bytes from [fe80::206:4fff:fe9b:d135]
2014/12/18 16:32:45.830| cc(263) Recv: 32 bytes from [fe80::206:
The verification of the Stable Release Update for juju-core 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
This bug was fixed in the package juju-core - 1.20.11-0ubuntu0.14.04.1
---
juju-core (1.20.11-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1386144).
* Packaging changes relating to new upstream release:
- d/control: add build dependency on lsb-release.
The verification of the Stable Release Update for juju-core 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
The verification of the Stable Release Update for juju-core 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
This bug was fixed in the package juju-core - 1.20.11-0ubuntu0.14.04.1
---
juju-core (1.20.11-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1386144).
* Packaging changes relating to new upstream release:
- d/control: add build dependency on lsb-release.
This bug was fixed in the package juju-core - 1.20.11-0ubuntu0.14.04.1
---
juju-core (1.20.11-0ubuntu0.14.04.1) trusty; urgency=medium
* New upstream release (LP: #1386144).
* Packaging changes relating to new upstream release:
- d/control: add build dependency on lsb-release.
This bug was fixed in the package python-logutils - 0.3.3-2ubuntu1
---
python-logutils (0.3.3-2ubuntu1) vivid; urgency=medium
* Merge from Debian unstable (LP: #1401461), remaining changes:
- d/p/test-failures-fatal.patch: Make unit test failures fatal.
* Dropped, equivalents
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
SQL error during alembic.migration when populating
@marco-bettio,
Did you compiled this manually? Could you try with the archive package
instead?
I can't get the debugging symbols for your crash
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.n
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/python-logutils
/vivid-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-logutils in Ubuntu.
https://bugs.launchpad.net/bugs/1401461
Title:
Please merge python-logutils
Hi Jorge,
I recreated the error so the crash report is related to the following log
entry:
/var/log/squid3/cache.log
2014/12/18 14:09:24.128| nger.cc(213) Recv: Pass [2a00:1450:4002:801::1016]
off to ICMPv6 module.
2014/12/18 14:09:24.128| cc(194) SendEcho: Send Icmp6 packet to
[2a00:1450:4
** Changed in: installation-report (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: installation-report (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openss
@marco-bettio
Could you upload the crash files ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1384943
Title:
[SRU] Pinger crashes with segfault in libc
To manage notifications ab
utopic and trusty fixes uploaded for sru team review.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage n
utopic and trusty fixes uploaded for SRU team review
** Changed in: pacemaker (Ubuntu Utopic)
Status: New => In Progress
** Changed in: pacemaker (Ubuntu Utopic)
Importance: Undecided => High
** Summary changed:
- SRU breaks pacemaker in 14.04
+ pacemaker should have a binary version
** Branch linked: lp:ubuntu/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage notifications abo
** Branch linked: lp:ubuntu/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1382842
Title:
SRU breaks pacemaker in 14.04
To manage notifications about this bug go to:
ht
This bug was fixed in the package pacemaker - 1.1.11-1ubuntu1
---
pacemaker (1.1.11-1ubuntu1) vivid; urgency=medium
* Merge from Debian experimental, remaining changes:
- d/control: Build-Depends on libcfg-dev.
- Corosync's pacemaker plugin is disabled, hence not built:
This bug was fixed in the package pacemaker - 1.1.11-1ubuntu1
---
pacemaker (1.1.11-1ubuntu1) vivid; urgency=medium
* Merge from Debian experimental, remaining changes:
- d/control: Build-Depends on libcfg-dev.
- Corosync's pacemaker plugin is disabled, hence not built:
Public bug reported:
Ubuntu 14.04.1 tls trusty
Using library: libvirt 1.2.2
Using API: QEMU 1.2.2
Running hypervisor: QEMU 2.0.0
When you create a snapshot through "virsh snapshot-create-as" when a virtual
machine is on,
then the source tag in the xml is changed.
But when you reboot the HOST,
** Branch linked: lp:ubuntu/vivid-proposed/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1368737
Title:
Pacemaker can seg fault on crm node online/standby
To manage no
** Branch linked: lp:ubuntu/vivid-proposed/pacemaker
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1382842
Title:
SRU breaks pacemaker in 14.04
To manage notifications about thi
** Changed in: pacemaker (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: pacemaker (Ubuntu Utopic)
Importance: Undecided => High
** Changed in: pacemaker (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
S
The right resolution to this problem is to pair the pacemaker binary
package with exact versions of pacemaker libraries;
** Also affects: pacemaker (Ubuntu Vivid)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: In Progress
** Also affects: pacemaker (Ubuntu Uto
** Also affects: pacemaker (Ubuntu Vivid)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: In Progress
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Utopic)
Importance: Undecided
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1214379, so is being marked as such.
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
Public bug reported:
after auto update?
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-g
** Changed in: charmhelpers (Juju Charms Collection)
Status: In Progress => Fix Committed
** Package changed: hacluster (Juju Charms Collection) => nova-cloud-
controller (Juju Charms Collection)
** Also affects: swift-proxy (Juju Charms Collection)
Importance: Undecided
Status:
50 matches
Mail list logo
