Ok thanks, that's helpful. Something seems to be wrong with the python-
cryptography package. It seems to intend to install cffi but it is
obviously not happening.
** Changed in: cloud-archive
Status: Incomplete => Triaged
** Changed in: cloud-archive
Importance: Undecided => High
**
Testing has completed successfully for ocata-proposed between regression
testing successfully and the following results testing qemu/libvirt with
microcode updates: https://paste.ubuntu.com/p/X45Gghqvkk/
** Tags removed: verification-ocata-needed
** Tags added: verification-ocata-done
--
You
** No longer affects: cloud-archive/icehouse
** Changed in: cloud-archive
Status: New => Triaged
--
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/1744882
Title:
Add SPEC_CTRL
** Tags added: verification-pike-done
--
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/1744882
Title:
Add SPEC_CTRL and IBRS changes
To manage notifications about this bug go to:
Hello ChristianEhrhardt, or anyone else affected,
Accepted qemu into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
Regression testing with tempest successful on pike-proposed:
==
Totals
==
Ran: 102 tests in 1330.1886 sec.
- Passed: 94
- Skipped: 8
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 644.0600 sec.
--
You received this bug notification because
Regression testing with tempest successful on ocata-proposed:
==
Totals
==
Ran: 102 tests in 1543.5582 sec.
- Passed: 94
- Skipped: 8
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 908.5919 sec.
--
You received this bug notification
Hello ChristianEhrhardt, or anyone else affected,
Accepted qemu into kilo-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
Hello ChristianEhrhardt, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance:
This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.6~cloud1
---
libvirt (2.5.0-3ubuntu5.6~cloud1) xenial-ocata; urgency=medium
.
* d/p/ubuntu/0001-gnutls-use-AC_CHECK_FUNCS.patch,
d/p/ubuntu/0002-gnutls-properly-backup-CFLAGS-and-LIBS.patch:
Enable
Hello lyarwood, or anyone else affected,
Accepted libvirt into ocata-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Also marking as invalid for the cloud-archive based on Christian's
comments. The libvirt packages in the xenial cloud archives are
unchanged from the corresponding Ubuntu release they've been backported
from.
** Changed in: cloud-archive
Status: New => Invalid
--
You received this bug
This bug was fixed in the package libvirt - 3.6.0-1ubuntu6~cloud0
---
libvirt (3.6.0-1ubuntu6~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (3.6.0-1ubuntu6) artful; urgency=medium
.
* d/p/ubuntu-aa/0037-virt-aa-helper...: grant
OpenStack regression testing passed successfully on pike-proposed:
xenial-pike-proposed with stable charms:
Ran: 102 tests in 1588.4030 sec.
- Passed: 93
- Skipped: 9
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 687.2787 sec.
This bug was fixed in the package websockify - 0.6.0+dfsg1-1~cloud2
---
websockify (0.6.0+dfsg1-1~cloud2) trusty-kilo; urgency=medium
.
* Fix hanging nova-novncproxy and can't be restarted (LP: #1715254)
- [PATCH] Make websockify respect SIGTERM
- [PATCH] Remove
Hi Akshay, This has been released for Ocata.
** Changed in: cloud-archive/ocata
Status: Fix Committed => Fix Released
--
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/1720397
qemu (1:2.8+dfsg-3ubuntu2.9~cloud1) xenial-ocata; urgency=medium
* reverted "Backport support for GICv3/vITS save/restore (LP 1710019)."
as there was an arm regressions found in zesty-proposed (cancelled before
SRU release).
--
You received this bug notification because you are a
This fix has been reverted in qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 to align
with Zesty. qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 has now been released to
ocata-updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: cloud-archive/ocata
Status: Fix Released => Triaged
--
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/1710019
Title:
support GICv3 ITS save/restore & migration
To
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.8~cloud0
---
qemu (1:2.8+dfsg-3ubuntu2.8~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.8+dfsg-3ubuntu2.8) zesty; urgency=medium
.
* Backport support for GICv3/vITS
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
Regression testing has passed successfully.
zesty-ocata-proposed with stable charms:
==
Totals
==
Ran: 102 tests in 1897.0150 sec.
- Passed: 93
- Skipped: 9
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 1011.5607 sec.
zesty-ocata-proposed
** Tags removed: verification-ocata-needed verification-pike-needed
** Tags added: verification-ocata-done verification-pike-done
--
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/1720397
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.1~cloud0
---
qemu (1:2.10+dfsg-0ubuntu3.1~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.10+dfsg-0ubuntu3.1) artful; urgency=medium
.
*
Hello Sean, or anyone else affected,
Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Invalid
** Changed in: cloud-archive/pike
Status: New => Triaged
** Changed in: cloud-archive
Status: Invalid => Fix Released
--
You received this
Hello dann, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Sean, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello ChristianEhrhardt, or anyone else affected,
Accepted libvirt into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
Hello ChristianEhrhardt, or anyone else affected,
Accepted libvirt into queens-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
Thanks for the patches Seyeong. Assuming those fix the problem this only
affects websockify < 0.8.0, which are releases prior to Yakkety/Newton.
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Also affects: cloud-archive/icehouse
Importance: Undecided
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Changed in: cloud-archive/pike
Status: New => Triaged
** Changed in: cloud-archive
Status: New => Triaged
** Changed in: cloud-archive/pike
Importance: Undecided => Critical
** Changed in:
Regression testing with OpenStack tempest for Ocata has completed
successfully.
xenial-ocata proposed stable charms:
==
Totals
==
Ran: 102 tests in 1742.1837 sec.
- Passed: 93
- Skipped: 9
This bug was fixed in the package libvirt - 3.6.0-1ubuntu5~cloud0
---
libvirt (3.6.0-1ubuntu5~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (3.6.0-1ubuntu5) artful; urgency=medium
.
*
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3~cloud0
---
qemu (1:2.10+dfsg-0ubuntu3~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.10+dfsg-0ubuntu3) artful; urgency=medium
.
* fix enablement of qemu-kvm service
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
OpenStack regression tests have passed successfully for xenial-pike-
proposed with this package.
pike-proposed with next charms:
==
Totals
==
Ran: 102 tests in 1904.7099 sec.
- Passed: 93
- Skipped: 9
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for
Hello ChristianEhrhardt, or anyone else affected,
Accepted libvirt into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
Hello Ernie, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Ernie, or anyone else affected,
Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** No longer affects: cloud-archive/pike
** Changed in:
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Fix
Hi Andy,
I've verified this on both xenial-proposed [1] and zesty-proposed [2].
I tested using https://github.com/openstack-snaps/snap-test to deploy a
minimal OpenStack cloud, deployed an instance on top of it, and created
a snapshot from that instance.
Thanks,
Corey
[1] xenial-proposed
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Also affects: libvirt (Ubuntu Artful)
Importance: Medium
Assignee: Corey Bryant (corey.bryant)
Status: Triaged
** Also affects: libvirt (Ubuntu Zesty)
Importance: Undeci
Switching the status back to New for upstream nova since there may be a
need to switch from host-model to host-passthrough in nova.
** Changed in: nova
Status: Opinion => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Can't seem to target this to yakkety atm, launchpad is erroring for 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/1623700
Title:
[SRU] multipath iscsi does not logout of sessions
Hua, Can you update the regression potential for the Ubuntu SRU details
please? 'None' isn't really a good answer, especially with Gustavo's
comment above. Can we check if any other patches have landed upstream
wrt his comment?
** Also affects: cloud-archive/mitaka
Importance: Undecided
This is going to need to land in yakkety and newton before it gets backported
to xenial. I've initiated the upstream backport to newton:
https://review.openstack.org/#/c/447018/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1551963
Title:
wrong haswell cpu features in cpu_map.xml
To manage
** Changed in: cloud-archive
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/1641532
Title:
machine-types trusty and utopic are not unique
Uploaded to liberty-staging ppa for the cloud archive. That'll need to
be promoted to liberty-proposed once it builds successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Testing of migrations from liberty with the following patch were
successful. However we may need to hold off on uploading to liberty
until later releases are fixed. http://paste.ubuntu.com/23827800/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: cloud-archive/liberty
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
** Changed in: cloud-archive/liberty
Status: New => In Progress
** Changed in: cloud-archive/liberty
Importance: Undecided => Critical
--
** Tags removed: verification-liberty-needed
** Tags added: verification-liberty-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1601986
Title:
RuntimeError:
David, you could try adding "Restart=on-failure" back to the init file
as a test. If it works, we could look into backporting that to xenial,
however I'm hesitant to do that until we know better why they dropped
the restart bits in the first place.
--
You received this bug notification because
This may have been fixed as of the 1.1.15-1 version of the pacemaker
package. Prior to commit 071796e, "Restart=on-failure" was patched out.
I've attached the diff of the commit that reverted that.
** Patch added: "pacemaker-071796e.diff"
David, what release of ubuntu/openstack does this affect? I'd like to
see if we can get a package update in a PPA for you to test with.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
** Also affects: cloud-archive/icehouse
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: Confirmed => Invalid
** Changed in: cloud-archive/icehouse
Status: New => Fix Committed
** Changed in: cloud-archive/icehouse
Importance: Undecided => Medium
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1601986
Title:
RuntimeError: osrandom engine already registered
To
A new version of python-cryptography with this fix has been uploaded to
liberty-staging and is awaiting promotion to liberty-proposed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
** Changed in: cloud-archive
Status: New => Fix Released
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
commit 9837cb15b84fea92ffce3306d14160a8c11b1c65 is included in mitaka
and above, so I'm marking this as fix released for python-cryptography
in Ubuntu. We'll target a fix for the Liberty cloud-archive.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects:
I think this is fixed by the following commit to python-cryptography.
commit 9837cb15b84fea92ffce3306d14160a8c11b1c65
Author: Paul Kehrer
Date: Mon Aug 24 08:00:10 2015 -0500
make engine addition idempotent
Threading issues keep cropping up. ENGINE_add
Hi Dave,
Thanks for reporting this. Did you upgrade from a prior version of
python-cryptography by any chance? It looks like a prerm script is
failing on a getrandom() call, however I don't see a prerm script in the
xenial package or any other prior releases that I could find. From the
I tested out openstack-dashboard for ocata with python-django 1.10.3 and
python-django-compressor 2.1, and all looks to be working fine. I also
upgraded from python-django 1.8.7 -> 1.10.3 with no issues. It's worth
noting that my testing was limited to backported packages on xenial, and
I don't
** Changed in: cloud-archive
Status: New => Invalid
--
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/1640676
Title:
[SRU] libvirt 1.2.12 live-migration corrupts some instances
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Changed in: cloud-archive/kilo
Status: New => Triaged
** Changed in: cloud-archive/kilo
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server
** Tags removed: verification-kilo-needed
** Tags added: verification-kilo-done
--
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/1612089
Title:
Fix for CVE-2016-5403 causes crash on
** Tags removed: verification-icehouse-needed
** Tags added: verification-icehouse-done
--
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/1612089
Title:
Fix for CVE-2016-5403 causes
** No longer affects: cloud-archive/newton
--
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/1612089
Title:
Fix for CVE-2016-5403 causes crash on migration if memory stats are
enabled
Importance: Undecided
Status: New
** Also affects: cloud-archive/liberty
Importance: Undecided
Status: New
** Changed in: cloud-archive/icehouse
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Changed in: cloud-archive/kilo
Assignee: (unassigned) => Corey
I think we need to carefully consider the side-effects of merging a new
python-django. Debian sid is now at 1.10 and it's caused quite a bit of
breakage. It looks like a number of upstream projects are not updated
wrt django 1.10 feature changes. One example is horizon, see Thomas'
patches
** Changed in: openstack-pkg-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547122
Title:
xenial: nova-api-metadata not
** Changed in: python-keystonemiddleware (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-keystonemiddleware in Ubuntu.
https://bugs.launchpad.net/bugs/1533724
Title:
[SRU]
** Also affects: python-keystonemiddleware (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: python-keystonemiddleware (Ubuntu Xenial)
Status: New => Triaged
** Changed in:
** Also affects: python-keystonemiddleware (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-keystonemiddleware (Ubuntu)
Status: New => Triaged
** Changed in: python-keystonemiddleware (Ubuntu)
Importance: Undecided => Medium
--
You received this bug
This bug was fixed in the package python-funcsigs - 1.0.2-1
Sponsored for Jeremy Bicha (jbicha)
---
python-funcsigs (1.0.2-1) experimental; urgency=medium
* Team upload.
* New upstream release
* Fixed VCS URLs (https).
* Changed upstream url to new one
* Changed build
Looking at the upstream code for glance_store stable/liberty
(https://github.com/openstack/glance_store) there are optional
dependencies listed in setup.cfg [extras], which include swiftclient.
It looks like these need to be added to the package's debian/control
Suggests or Depends section for
Matt, I'm going to also target this bug at upstream also since you're
saying that you're not using the swift backend but the glance_store code
is using the swift driver.
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: python-glance-store (Ubuntu Wily)
Status: New => Invalid
** Description changed:
New point releases for misc openstack components for the mitaka release:
- python-glance-store 0.9.2
nova 12.0.4
neutron 7.1.1
neutron-lbaas 7.1.1
neutron-fwaas 7.1.1
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: In Progress => Invalid
** Changed in: cloud-archive/kilo
Importance: Undecided => Medium
** Changed in: cloud-archive/kilo
Assignee: (unassigned) => Rafael David
** Also affects: nova (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: python-glance-store (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: neutron-lbaas
** Changed in: cloud-archive/liberty
Importance: High => Undecided
--
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/1569502
Title:
[SRU] liberty point releases
To manage
** Changed in: neutron (Ubuntu)
Status: Invalid => New
** Changed in: neutron-fwaas (Ubuntu)
Status: Invalid => New
** Changed in: neutron-lbaas (Ubuntu)
Status: Invalid => New
** Changed in: neutron-vpnaas (Ubuntu)
Status: Invalid => New
--
You received this bug
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: Invalid
** Changed in: cloud-archive/mitaka
Status: Invalid => In Progress
** Also affects: neutron (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: neutron-fwaas (Ubuntu Xenial)
** Also affects: cloud-archive/kilo
Importance: Undecided
Status: New
** Changed in: cloud-archive/kilo
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pyt
Hi Chris and James,
Testing of this SRU has completed successfully on wily-proposed and
liberty-proposed.
Thanks,
Corey
** Tags removed: verification-liberty-needed verification-needed
** Tags added: verification-done verification-liberty-done
--
You received this bug notification because you
Hi Tobias,
This should be moving along soon. All of the point releases mentioned
in this bug have been uploaded to the wily review queue
(https://launchpad.net/ubuntu/wily/+queue?queue_state=1_text=) and
are awaiting SRU team review. Once they land in wily-proposed we'll
begin backporting to
Are you deleting all of the contents from /usr/share/openstack-
dashboard/static/ prior to collecting/compressing static assets?
If so, I don't think this is something that you should be doing, since
part of the package install copies the contents of openstack_dashboard/
to
Hello Marcin, What version of python-django-compressor do you have
installed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1574082
Title:
Unable to manually compress js and css
Thanks Brian. I've uploaded a new version of cinder.
--
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/1569502
Title:
[SRU] liberty point releases
To manage notifications about this
** Description changed:
Context: openstack juju/maas deploy using 1510 charms release
on trusty, with:
openstack-origin: "cloud:trusty-liberty"
source: "cloud:trusty-updates/liberty
* Several openstack nova- and neutron- services, at least:
nova-compute, neutron-server,
** Also affects: oslo.messaging
Importance: Undecided
Status: New
** Also affects: python-oslo.messaging (Ubuntu)
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.
Thanks for catching that Brian. If you can reject cinder we'll get that
fixed up with a new upload.
--
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/1569502
Title:
[SRU] liberty point
In that case, if this is for kilo then python-keystoneclient should be
installed when neutron-server is installed. It is specified as a run-time
dependency in our kilo package's d/control file:
http://bazaar.launchpad.net/~ubuntu-server-dev/neutron/kilo/view/head:/debian/control#L411
--
You
** Changed in: python-oslo.messaging (Ubuntu Wily)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1515278
Title:
[SRU]
I just noticed I opened this against the wrong project. Nonetheless I'm
no longer able to recreate this.
** Changed in: nova (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Assuming this is for Mitaka, I don't think this is a valid bug. Neutron
dropped it's dependency on keystoneclient in Mitaka in favor of
keystoneauth. If you still think this is a bug, please provide some
more information on symptoms that you're seeing.
Note: We generally populate run-time
101 - 200 of 526 matches
Mail list logo