The verification of the Stable Release Update for haproxy 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
** Patch added: "debdiff of applied patches for Xenial"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+attachment/4521457/+files/applied-deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in
The verification of the Stable Release Update for cloud-initramfs-tools
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
@chengyuanli
could you please verify this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
To manage
This bug was fixed in the package cloud-initramfs-tools -
0.25ubuntu1.12.04.1
---
cloud-initramfs-tools (0.25ubuntu1.12.04.1) precise-proposed; urgency=medium
* no change backport of 0.25ubuntu1.14.04.1 from 14.04 to 12.04
(LP: #1515661)
+ add new binary packages:
Releasing 0.25ubuntu1.12.04.1, please do verify this issue, and if it
still is happening please re-open the bug so it can be addressed in a
subsequent upload.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in
This bug was fixed in the package cloud-initramfs-tools -
0.25ubuntu1.12.04.1
---
cloud-initramfs-tools (0.25ubuntu1.12.04.1) precise-proposed; urgency=medium
* no change backport of 0.25ubuntu1.14.04.1 from 14.04 to 12.04
(LP: #1515661)
+ add new binary packages:
Hello Scott, or anyone else affected,
Accepted bcache-tools into precise-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/bcache-
tools/1.0.7-1~12.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Public bug reported:
When I try to create a snapshot of a running virtual machine using the
following command:
virsh snapshot-create-as --quiesce --domain dns sn1 --diskspec
hda,file=/home/alank/vm/dns-sn1.qcow2 --disk-only --atomic
I receive the following error message: "error: internal error:
Smoke testing also completed on Vivid with OpenStack Kilo
** Tags removed: verification-needed-vivid
--
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/1512292
Title:
[SRU] update to
The verification of the Stable Release Update for ceph 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
This bug was fixed in the package ceph - 0.94.5-0ubuntu0.15.10.1
---
ceph (0.94.5-0ubuntu0.15.10.1) wily; urgency=medium
* New upstream release (LP: #1512292):
- d/p/ceph-radosgw-init.patch: Dropped, included upstream.
- d/p/*: Refresh
* Fixup problems with missing
This bug was fixed in the package haproxy - 1.5.14-1ubuntu0.15.10.1
---
haproxy (1.5.14-1ubuntu0.15.10.1) wily; urgency=medium
* Ensure that haproxy processes are terminated correctly when executing
stop/restart operations, easing backports to pre-systemd versions of
Ubuntu
** Also affects: cloud-initramfs-tools (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1236380
Title:
** Changed in: ceph (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
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/1517432
Title:
Keystone v3 expire dates cannot be parsed
This bug was fixed in the package haproxy - 1.5.14-1ubuntu0.15.10.1
---
haproxy (1.5.14-1ubuntu0.15.10.1) wily; urgency=medium
* Ensure that haproxy processes are terminated correctly when executing
stop/restart operations, easing backports to pre-systemd versions of
Ubuntu
The verification of the Stable Release Update for ceph 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
This bug was fixed in the package ceph - 0.94.5-0ubuntu0.15.10.1
---
ceph (0.94.5-0ubuntu0.15.10.1) wily; urgency=medium
* New upstream release (LP: #1512292):
- d/p/ceph-radosgw-init.patch: Dropped, included upstream.
- d/p/*: Refresh
* Fixup problems with missing
Public bug reported:
See this trace:
http://paste.openstack.org/show/479272/
** Affects: oslo-sphinx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo-sphinx in Ubuntu.
Can you please test with the 4.2.0-19.23 kernel on Xenial as well?
Thanks
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Attached debdiff of all patch and logic applied for instance ID
migration.
** Patch added: "debdiff for testing"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+attachment/4521522/+files/bzr1155-bzr1156-deb.diff
** Changed in: cloud-init (Ubuntu Precise)
Assignee:
Per feedback, instance migration logic is proposed to be in the preinst.
** Patch added: "diff for cloud-init.preinst.diff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+attachment/4521521/+files/cloud-init.preinst.diff
--
You received this bug notification because you
** Branch linked: lp:cloud-init
--
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/1506187
Title:
[SRU] Azure: cloud-init should use VM unique ID
To manage notifications about this
** Changed in: lxc (Ubuntu Xenial)
Status: Triaged => 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/1517107
Title:
$PATH is getting clobbered when starting a
Hello Adam, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chris, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chris, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Martin, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Martin, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- I have a script using the Python3 LXC API that starts up a container.
- If I use an Upstart job to call the script, the $PATH env var is getting
- clobbered and the container fails to start.
+ == SRU ==
+ Rationale: LXC 1.1 and higher mangles the process env to be able
** Branch linked: lp:ubuntu/wily/cloud-init
--
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/1177432
Title:
[SRU] cloud-init archive template should match Ubuntu Server
To manage
This bug was fixed in the package ipmitool - 1.8.13-1ubuntu0.6
---
ipmitool (1.8.13-1ubuntu0.6) trusty; urgency=medium
* debian/patches/lp1509896_fix_scsi_probe_607cfe6.patch: allow for up to
16 devices on the SCSI bus when probing. Fixes the probing failing the
use of the
** Changed in: lxc (Ubuntu)
Status: New => Won't 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/1514960
Title:
lxc-test-checkpoint-restore fails with no explanation why
To
** Also affects: lxc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Wily)
Importance:
** Changed in: lxc (Ubuntu Xenial)
Status: Triaged => 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/1516971
Title:
LXC's preserve_ns fails on < 3.8 kernels
To
The verification of the Stable Release Update for ipmitool 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
** Description changed:
+ == SRU ==
+ Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
+ Test case: Try starting an LXC container on an affected kernel
+ Regression potential: Can't really get any worse. Change has been reviewed
and tested upstream.
+
+ == Original bug report ==
Hello Adam, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kevin, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Nick, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kevin, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Chris, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jean-Baptiste, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brad, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jean-Baptiste, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: nova/juno
Importance: Undecided
Status: New
--
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/1353939
Title:
Rescue fails with 'Failed to terminate process:
Do other iso's, like http://archive.ubuntu.com/ubuntu/dists/wily/main
/installer-amd64/current/images/netboot/mini.iso also cause this for
you?
(I ran with upstream qemu GIT HEAD using that iso and was unable to
reproduce)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: lxc (Ubuntu)
Status: Fix Committed => 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/1514942
Title:
lxc-tests no runtime help (no man page, no
This package is causing a regression in lp:qa-regression-testing's
scripts/test-qemu.py.
I'm running the testcase one more time (after having verified that the
current package did not suffer the same failure), then I'm going to mark this
verification-failed.
--
You received this bug
Moving this bug over to lxcfs.
** 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.
https://bugs.launchpad.net/bugs/1514690
Title:
rebooting container with systemd >= 226
Hello Christopher, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Stéphane, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
That's by design, none of the lxc-test-* binaries clean after themselves
on failure so that the developer running them can go inspect the
remnants to understand what's actually happened.
** Changed in: lxc (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because
Hello Christopher, or anyone else affected,
Accepted lxc into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brad, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brad, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jean-Baptiste, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:~smoser/ubuntu/xenial/cloud-init/lp1506187
--
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/1506187
Title:
[SRU] Azure: cloud-init should use VM unique ID
To
** Description changed:
- The current ipmitool code can fail to find an IPMI device on my
- OpenPower machine, due to bug in the USB SCSI device discovery process.
+ [Impact]
+ The current ipmitool code can fail to find an IPMI device on my OpenPower
machine, due to bug in the USB SCSI device
For 14.04 this is waiting for the current update pending verification
to be completed. If you can help in verifying bug
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1386637,
that could speed up providing all updates.
--
You received this bug notification because you are a
No time to debug, invaliding...
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: lxc (Ubuntu Wily)
Status: New => Fix Committed
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hm, a second run did not reproduce the error. If I can't get it to
happen again in a few hours of re-trying, I'll assume it was a fluke or
related to the host.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
This bug was fixed in the package cloud-init - 0.7.7~bzr1156-0ubuntu1
---
cloud-init (0.7.7~bzr1156-0ubuntu1) xenial; urgency=medium
* New upstream snapshot.
* d/cloud-init.preinst: migrate Azure instance ID from old ID to stable
ID (LP: #1506187).
-- Ben Howard
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 17:57
EDT---
** Attachment added: "fix information not shown when first path is down"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521559/+files/0001-libmultipath-Fix-information-not-shown-when-first-pa.patch
Default Comment by Bridge
** Attachment added: "ilp2fc82ap61 messages log"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521556/+files/ilp2fc82ap61.messages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
Default Comment by Bridge
** Attachment added: "'multipath -v 3' from client ilp1fc85apA4"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521557/+files/file_120998.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Default Comment by Bridge
** Attachment added: "dmesg file"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521554/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 17:59
EDT---
** Attachment added: "'multipath -v 3' from client ilp1fc85apA4"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521560/+files/file_120998.txt
--
You received this bug notification because you are
Default Comment by Bridge
** Attachment added: "ilp1fc85apA4 syslog"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521555/+files/ilp1fc85apA4.syslog.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in
Default Comment by Bridge
** Attachment added: "fix information not shown when first path is down"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521558/+files/0001-libmultipath-Fix-information-not-shown-when-first-pa.patch
--
You received this bug notification because you are a
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 18:01
EDT---
** Attachment added: "ilp1fc85apA4 syslog"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521562/+files/ilp1fc85apA4.syslog.1
--
You received this bug notification because you are a member of
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 18:00
EDT---
** Attachment added: "ilp2fc82ap61 messages log"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521561/+files/ilp2fc82ap61.messages
--
You received this bug notification because you are a member
--- Comment (attachment only) From gmgay...@us.ibm.com 2015-10-06 18:03
EDT---
** Attachment added: "dmesg file"
https://bugs.launchpad.net/bugs/1503305/+attachment/4521563/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1390223 ***
https://bugs.launchpad.net/bugs/1390223
Alright, so this is not the disconnected path issue I thought it was, I
am looking into it more.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
--- Comment From mainam...@in.ibm.com 2015-11-18 11:00 EDT---
*** Bug 128128 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
I adjusted the autopkgtest-cloud infrastructure for this change
yesterday, as this caused some fallout.
I now created a custom cloud image for precise with the -proposed
update, and tests that ran against it confirm that there now are apt
sources for restricted/multiverse/backports, etc:
** Tags added: rls-x-incoming
--
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/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device
Yes, this seems to be something that was copied over from 5.5 and can be
removed.
--
Lars
On 11/18/2015 11:18 AM, 冯宇 wrote:
> +1 Same issue here.
>
> This might be ha_innodb.so and other files not exist in
> /usr/lib/mysql/plugin/, but mysql-server-5.5 contains these files.
>
--
You received
Public bug reported:
lxc in trusty depends now on lxcfs but this is only available in the
backports pocket. This triggers ADT failures:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-trusty/trusty/ppc64el/l/lxc/20151118_111844@/log.gz
et install -y linux-
image-generic linux-headers-generic' --setup-commands
/home/ubuntu/autopkgtest/setup-commands/cloud-vm-setup --- ssh -s
/home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --image
ubuntu/ubuntu-trusty-14.04-amd64-server-20151117-disk1.img --name adt-
trusty-amd64-lx
This appears to be an infrastructure issue, handing off to testing.
** Also affects: auto-package-testing
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
FTR, there is no reason to make this specific to Ubuntu or systemd --
"nofail" is the defined by util-linux, it's not a systemd specific
thing. upstart introduced "nobootwait" some years ago, but it has always
been an upstart specific alias for the official "nofail".
--
You received this bug
** 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/1511899
Title:
Public bug reported:
Keystone v3 returns the token expiration date with microseconds, e.g.
'2015-11-03T18:30:59.99Z'. The parse_iso8601 function cannot deal with
this, so using Keystone authentication always ends with "Failed to parse
ISO8601 expiration date from Keystone response." in the
SRU bug 1512292
--
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/1517432
Title:
Keystone v3 expire dates cannot be parsed by radosgw
To manage notifications about this bug go to:
** Changed in: ceph (Ubuntu Wily)
Assignee: (unassigned) => James Page (james-page)
** Changed in: ceph (Ubuntu Vivid)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in
https://github.com/ceph/ceph/commit/6119b152412ddfa2a614c1862aad52a123a4fe8e
was included in 0.94.5 which is currently working through the SRU
process.
Marking Fix Committed.
** Changed in: ceph (Ubuntu)
Status: New => Triaged
** Changed in: ceph (Ubuntu)
Importance: Undecided =>
Indeed this is fallout from bug 1177432, where cloud-init changed to add
-backports (even on stables).
** Changed in: auto-package-testing
Importance: Undecided => Critical
** Changed in: auto-package-testing
Status: New => In Progress
** Changed in: auto-package-testing
This actually did introduce quite a major behaviour change: "apt-get
source foo" will now download the -backports version, *not* the version
that you would get with "apt-get install".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This appears to be related to the changes applied to the cloud images
under bug: #1177432.
--
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/1517426
Title:
[trusty] lxc: lxc now depends
+1 Same issue here.
This might be ha_innodb.so and other files not exist in
/usr/lib/mysql/plugin/, but mysql-server-5.5 contains these files.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
Public bug reported:
Hello,
We encounter tracebacks in gunicorn-error.log when a client download a
“not modified” page:
gunicorn-error.log <==
2015-06-16 11:39:00 [5565] [ERROR] Socket error processing request.
Traceback (most recent call last):
File
*** This bug is a duplicate of bug 1390223 ***
https://bugs.launchpad.net/bugs/1390223
Alright, this is failing the way it is because it is a race on the
socket being shutdown. If the mediate_deleted flag was removed from the
profile, an additional info flag would show up in the DENIED
*** This bug is a duplicate of bug 1390223 ***
https://bugs.launchpad.net/bugs/1390223
yes, sorry I'm not sure why I missed adding the leading /
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Blueprint changed by Robie Basak:
Work items changed:
Work items:
[racb] nagios-plugins/monitoring-plugins merge and cleanup: INPROGRESS
+ strongswan merge and cleanup: TODO
+ [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
+ puppet merge and cleanup: TODO
+ [paelzer]
I have verified this fix.
** 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-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515661
Title:
[SRU]
Blueprint changed by Robie Basak:
Work items changed:
+ Work items for ubuntu-15.11:
+ [serge-hallyn] etckeeper: TODO
+ [paelzer] NIS merge: INPROGRESS
+
Work items:
[racb] nagios-plugins/monitoring-plugins merge and cleanup: INPROGRESS
strongswan merge and cleanup: TODO
[smoser]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nut (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1483615
1 - 100 of 110 matches
Mail list logo
