The fix in quantal-proposed is currently complicated by a udev bug
#1092715. The udev trigger from the postinst doesn't seem to pick up
the new rules file in /lib/udev/rules.d, and permissions are not updated
by the trigger.
--
You received this bug notification because you are a member of
Looks like an issue in the postinst's call to 'keystone-manage db_sync'.
Can't seem to reproduce when upgrading between the same versions, using
the default (empty) local sqlite db, but this was probably hit against a
live, remote database?
James, what db backend is in use? Can you confirm the
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using quantal-proposed as an installation source. After successful
bring-up and
** Attachment added: quantal_folsom_n-vol_proposed.tar
https://bugs.launchpad.net/ubuntu/quantal/+source/cinder/+bug/1085255/+attachment/3474523/+files/quantal_folsom_n-vol_proposed.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Attachment added: quantal_folsom_proposed.tar
https://bugs.launchpad.net/ubuntu/quantal/+source/cinder/+bug/1085255/+attachment/3474524/+files/quantal_folsom_proposed.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
** Attachment added: quantal_folsom_quantum_proposed.tar
https://bugs.launchpad.net/ubuntu/quantal/+source/cinder/+bug/1085255/+attachment/3474525/+files/quantal_folsom_quantum_proposed.tar
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
The change needs to be reviewed and merged into the stable/essex branch
upstream before it will be updated in Ubuntu. The review you linked
expired and the change was never merged. Perhaps re-submit it and ping
someone on the stable maintenance team for the required approval?
--
You received
** Changed in: keystone (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1094921
Title:
keystone postinst fails with KeyError: VerNum(4)
To
** Also affects: nova (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.
https://bugs.launchpad.net/bugs/1087092
Title:
nova-rpc-zmq-receiver not included in nova
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
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/1087092
Title:
nova-rpc-zmq-receiver not included in nova packages
To
Definitely used in Folsom (and missing as a dep for Quantal) but a quick
grep of the Essex (precise) source doesn't turn up any uses of
genisoimage.
** Changed in: nova (Ubuntu Quantal)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Noticed juju deployed services were failing to come up using Juju+MAAS
and the newly released cloud-init SRU for 12.04. The node provisioned
thru MAAS okay, but after first boot did not have the required agents
installed. On further investigation, it looks like the required
** Attachment added: user-data.txt
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+attachment/3485134/+files/user-data.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Removing the first parameter in the call to add_sources() seems to fix
the issue:
=== modified file 'CloudConfig/cc_apt_update_upgrade.py'
--- CloudConfig/cc_apt_update_upgrade.py2013-01-16 22:05:40 +
+++ CloudConfig/cc_apt_update_upgrade.py2013-01-16 22:10:42 +
@@ -72,7
** Description changed:
+ [Impact]
+
+ cloud-init can no longer process cloud-config that specify a 'packages'
+ value. This affects any tools (Juju, MAAS) that rely on cloud-init to
+ install various packages as part of its first-boot. This seems to
+ trigger when specifying apt_sources in
Was able to test the proposed package on an EC2 instance using the test
case in the SRU text in bug description. Log attached.
** Attachment added: lp1100491_verification.txt
** Changed in: glance
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1100803
Title:
Glance install fails with Ubuntu Testing Packages
To manage
** Package changed: openstack-dashboard (Ubuntu) = horizon (Ubuntu)
** Changed in: horizon (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
Public bug reported:
This is a meta-bug used for tracking progress of the 2012.2.3 Folsom
stable update to Nova, Horizon, Keystone, Glance, Cinder and Quantum.
** Affects: cloud-archive
Importance: Undecided
Status: New
** Affects: cinder (Ubuntu)
Importance: Undecided
** Also affects: cloud-archive
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/1116671
Title:
Meta bug for tracking Openstack 2012.2.3
Summary (LP: #1055929)
+* debian/static/openstack-dashboard: Recompress static JS and CSS based on
+ changes applied upstream in stable/folsom.
+
+ keystone (2012.2.3+stable-20130206-82c87e56-0ubuntu1) quantal-proposed;
urgency=low
+ .
+[ Adam Gandelman ]
+* Dropped patches, applied
** Changed in: quantum (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: cloud-archive
Status: New = Confirmed
** Also affects: quantum (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: quantum (Ubuntu Quantal)
Status: New = Confirmed
--
** Changed in: cloud-archive
Status: New = Confirmed
** Also affects: horizon (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: horizon (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: nova (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: cloud-archive
Status: New = Confirmed
** Also affects: libvirt (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Quantal)
Importance: Undecided
Status:
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
- SSL everywhere: TODO
+ SSL everywhere: INPROGRESS
HA rabbitmq: TODO
HA mysql: TODO
[gandelman-a] Nova compute deployment ready for live migration: INPROGRESS
HA proxy
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
SSL everywhere: INPROGRESS
HA rabbitmq: TODO
HA mysql: TODO
- [gandelman-a] Nova compute deployment ready for live migration: INPROGRESS
+ [gandelman-a] Nova compute deployment
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
SSL everywhere: INPROGRESS
HA rabbitmq: TODO
HA mysql: TODO
[gandelman-a] Nova compute deployment ready for live migration: DONE
- HA proxy relations for all API servers
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[andreserl] develop juju charms for HA (corosync/pacemaker): INPROGRESS
[jamespage] haproxy charm HA support: DONE
[andreserl] quantum charm HA support: DONE
[andreserl] mysql charm HA support (either drbd - using
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
SSL everywhere: INPROGRESS
HA rabbitmq: TODO
- HA mysql: TODO
+ [andreserl] HA mysql: INPROGRESS
[gandelman-a] Nova compute deployment ready for live migration: DONE
HA proxy
Thanks for spotting this, Filipe. Yes, the stable/folsom packaging
needs to be updated to also include the newly added quantum-ovs-cleanup
script. We're currently including this file in Raring as part of the
quantum-common package. We should do the same for quantal.
--
You received this bug
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
[james-page] Add support for multiple quantum router agents: TODO
[james-page] Add support for quantum lbaas: TODO
- SSL everywhere: INPROGRESS
- HA rabbitmq: INPROGRESS
** Changed in: glance (Juju Charms Collection)
Status: Triaged = Fix Released
** Changed in: cinder (Juju Charms Collection)
Status: Triaged = Fix Released
** Changed in: nova-compute (Juju Charms Collection)
Status: Triaged = Fix Released
--
You received this bug
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
[james-page] Add support for multiple quantum router agents: TODO
[james-page] Add support for quantum lbaas: TODO
[gandelman-a] SSL everywhere: INPROGRESS
[gandelman-a] HA
Ben-
With the information you've provided I'm not convinced this is a sync
but a merge. You've listed some of our delta but gave no reason why any
of it should be dropped.
After a quick closer look:
- The *.postinst changes still look valid, but you haven't specified why they
can be dropped.
Stig, there are several ways. In this case, I did 'bzr branch
lp:ubuntu/puppet cd puppet bzr merge
lp:debian/experimental/puppet'. Alternatively, you can just dget the
source packages from packages.ubuntu.com + packages.debian.org and
generate a debdiff. Here are is the Ubuntu delta from
Hey Ben--
What version of python-novaclient does this affect ? dpkg -l | grep
python-novaclient. I just tried /w whats current in raring (python-
novaclient 1:2.11.1-0ubuntu1), seeing no issue with pkg_resources and
the client seems functional
** Changed in: python-novaclient (Ubuntu)
On second glance, you're runnig /usr/local/bin/nova. Did you pip
install python-novaclient 2.9.0 before apt-get installing the raring
package? I'd remove your local copy and try again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Ben- It looks like you've got two nova clients installed, see Bug
#1153621.
But this seems still to affect python-novaclient:
root@raring-03-11-1634:~# nova --version
Unknown, couldn't find versioninfo file at /usr/lib/python2.7/dist-
packages/novaclient/versioninfo
root@raring-03-11-1634:~# ls
** Also affects: python-novaclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1079022
Title:
nova --version does not
Tagging as affecting upstream as its a tough one to package around. The
clients expect that the versioninfo text-file exist in the module's
path (eg, /usr/lib/python2.7/dist-packages/novaclient/), however, I'm
not sure its okay for the package to be installing that there, hence it
ends up in
Looks like glanceclient needs to be updated/fixed to make use of
openstack-common's version facilities, similar to cinder.
** Also affects: python-novaclient
Importance: Undecided
Status: New
** No longer affects: python-novaclient (Ubuntu)
** Project changed: python-novaclient =
Nothing special in the packaging, the package upgrade process just
basically lays out the new code and calls db_sync.
Took a closer look and have had no luck reproducing with current trunk
(installed from ppa:openstack-ubuntu-testing/grizzly-trunk-testing), but
was able to reproduce reliably
Fairly certain this is a duplicate. The traceback in the original
report is only half the story. Using G3, a db_sync against a populated
database first ends with error AttributeError: 'NamedTuple' object has
no attribute 'project_id' which Bug #1130424 addresses. Subsequent
db_sync's after
** Also affects: nova
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/1155458
Title:
500 response when trying to create a server from a
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[james-page] Complete Quantum charm: DONE
[james-page] Add support for multiple quantum router agents: TODO
[james-page] Add support for quantum lbaas: TODO
[gandelman-a] SSL everywhere: INPROGRESS
- [gandelman-a] HA
Lorin- What is the kernel version?
--
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/1029430
Title:
KVM guests networking issues with no virbr0 and with vhost_net kernel
modules loaded
Public bug reported:
After performing a package update of a deployed Folsom cloud (with
running instances), nova-compute fails to start up with the following
trace back:
2013-03-21 18:39:56.485 17998 INFO nova.manager [-] Skipping periodic task
_periodic_update_dns because its interval is
Public bug reported:
Upgrading a fairly standard Folsom setup to Grizzly using our packages.
After the updated config files are put in place and database has been
migrated, nova's EC2 API fails to authenticate requests with keystone.
The OSAPI end point works just fine.
On the client:
$
This is total configuration / packaging error. After the package
upgrade, the EC2 was set to use the KVS backend, when it was originally
using SQL.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Changed in: keystone (Ubuntu)
Status: New = Confirmed
--
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/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not
Michael, I'd love nothing more, but LP seems to be timing out anytime I
try touching those tasks. :\
** No longer affects: keystone
** No longer affects: nova
** No longer affects: nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Blueprint changed by Adam Gandelman:
Work items changed:
Work items:
[andreserl] write dep-8 test for heartbeat/corosync/pacemaker: POSTPONED
[andreserl] write dep-8 test for tftpd-hpa: POSTPONED
- [gandelman-a] write dep-8 test for haproxy: TODO
- [gandelman-a] write dep-8 tests puppet
Public bug reported:
cinder (and likely other openstack projects that use stevedore) fails to
correctly load scheduling filters. Initially erroring as follows:
2013-04-16 14:19:27ERROR [stevedore.extension] (stevedore 0.7.2
(/usr/lib/python2.7/dist-packages),
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using quantal-proposed as an installation source. After successful
bring-up and
Test coverage log.
** Attachment added: quantal_folsom.tar
https://bugs.launchpad.net/bugs/1116671/+attachment/3651746/+files/quantal_folsom.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Test coverage log.
** Attachment added: quantal_folsom_nova-volume.tar
https://bugs.launchpad.net/bugs/1116671/+attachment/3651748/+files/quantal_folsom_nova-volume.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
Test coverage log.
** Attachment added: quantal_folsom_quantum.tar
https://bugs.launchpad.net/bugs/1116671/+attachment/3651749/+files/quantal_folsom_quantum.tar
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using quantal-proposed as an installation source. After successful
bring-up and
Test coverage log.
** Attachment added: quantal_folsom_nova-volume.tar
https://bugs.launchpad.net/bugs/1029430/+attachment/3651751/+files/quantal_folsom_nova-volume.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
Test coverage log.
** Attachment added: quantal_folsom.tar
https://bugs.launchpad.net/bugs/1029430/+attachment/3651750/+files/quantal_folsom.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Test coverage log.
** Attachment added: quantal_folsom_quantum.tar
https://bugs.launchpad.net/bugs/1029430/+attachment/3651752/+files/quantal_folsom_quantum.tar
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
-0282
+* SECURITY UPDATE: fix denial of service
+ - debian/patches/CVE-2013-1664+1665.patch: disable XML entity parsing
+ - CVE-2013-1664
+ - CVE-2013-1665
+ .
keystone (2012.2.3+stable-20130206-82c87e56-0ubuntu1) quantal-proposed;
urgency=low
.
[ Adam Gandelman
Test coverage log.
** Attachment added: quantal_folsom.tar
https://bugs.launchpad.net/bugs/1055929/+attachment/3651774/+files/quantal_folsom.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using quantal-proposed as an installation source. After successful
bring-up and
Test coverage log.
** Attachment added: quantal_folsom_quantum.tar
https://bugs.launchpad.net/bugs/1055929/+attachment/3651776/+files/quantal_folsom_quantum.tar
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Public bug reported:
python-novaclient's bash completion does not work, the package installs
a broken sym link in /etc/bash_completion.d:
ubuntu@raring-04-24-1156:~$ ls -lh /etc/bash_completion.d/nova.bash_completion
lrwxrwxrwx 1 root root 53 Apr 5 17:39
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
@ Chuck
Can you please post a better test case? I'm trying to reproduce and
verify the fix but I haven't been able to trigger the issue. I've
followed your test case, and even gone as far as setting up remote
access to another system for cinder to create an SSH connection, but
haven't been able
Using a variation of a test case for the same bug found at http://redes-
privadas-virtuales.blogspot.com/2013/02/paramiko-object-with-process-
rng-must.html.
Looks like this is actually still in issue using the patched package in
raring python-paramiko 1.7.7.1-3.1, and the similarly patched
Fixed in upload to saucy, python-glanceclient
1:0.9.0.13.gaddd3c3-0ubuntu1
** Changed in: python-glanceclient (Ubuntu)
Status: Confirmed = Fix Released
** Also affects: python-glanceclient (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: python-glanceclient
** Also affects: python-novaclient (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: python-novaclient (Ubuntu Raring)
Status: New = Confirmed
** Changed in: python-novaclient (Ubuntu)
Importance: Undecided = Medium
** Changed in: python-novaclient (Ubuntu
*** This bug is a duplicate of bug 1172420 ***
https://bugs.launchpad.net/bugs/1172420
** This bug has been marked a duplicate of bug 1172420
python-novaclient installs broken symlink /etc/bash_completion.d
--
You received this bug notification because you are a member of Ubuntu
Server
** Summary changed:
- python-novaclient installs broken symlink /etc/bash_completion.d
+ [SRU] python-novaclient installs broken symlink /etc/bash_completion.d
** Description changed:
python-novaclient's bash completion does not work, the package installs
a broken sym link in
Blueprint changed by Adam Gandelman:
Assignee: (none) = Adam Gandelman
--
Ubuntu Cloud Archive Status Check
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
** Tags added: cloud-archive
--
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/1029430
Title:
KVM guests networking issues with no virbr0 and with vhost_net kernel
modules loaded
To
** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
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/1116671
Title:
Meta bug for tracking Openstack 2012.2.3 Stable
** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
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/1029430
Title:
KVM guests networking issues with no virbr0 and with
** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1097451
Title:
quantum-plugin-nicira miss a dependency
To
** Tags removed: grizzly-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1167421
Title:
Upgrading from folsom to grizzly results in all tenants/users being
Blueprint changed by Adam Gandelman:
Definition Status: Approved = Obsolete
--
OpenStack Juju Charms Next Steps
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-juju-charms
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings
Public bug reported:
This is a meta-bug used for tracking progress of the 2013.1.1 Grizzly
stable update to Nova, Horizon, Keystone, Cinder and Quantum in Ubuntu
13.04.
Note: Glance did not see any backports to upstream stable/grizzly branch
during this period, and is omitted from this update
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Things to discuss:
Tooling
Stable release update cadence
Support period alignment with Ubuntu distro releases (18 - 9 months)
+
+ Upstream stable release schedule:
+
+ stable release proposed dates:
+ 2013.1.1 May 9 - DONE
entity expansion (CVE-2013-1664) LP: 1100282
glance (2012.2.4-0ubuntu1) quantal-proposed; urgency=low
.
[ Adam Gandelman ]
* Dropped patches, applied upstream:
- debian/patches/CVE-2013-1840.patch: [dd849a9]
* Resynchronize with stable/folsom (dbd3d3d7):
- [cfaa2d8] repeated
cinder (1:2013.1.1-0ubuntu1) raring-proposed; urgency=low
.
* Resynchronize with stable/grizzly (a4856c4e) (LP: #1179626):
- [995a310] Can't specify custom backend-name for HP/3par driver
LP: 1175222
- [319f712] SolidFire driver can't be used with extra-specs as in the past
** Also affects: cloud-archive
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/1179626
Title:
Meta bug for tracking Openstack 2013.1.1
** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
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/1065702
Title:
After folsom upgrade, instances can no longer access
** Changed in: cloud-archive
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-eventlet in Ubuntu.
https://bugs.launchpad.net/bugs/1078232
Title:
[SRU] os.waitpid() returns immediately
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New = In Progress
** Changed in: cloud-archive
Assignee: (unassigned) = Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member
** Changed in: cloud-archive
Status: New = In Progress
** Changed in: cloud-archive
Assignee: (unassigned) = Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https
Joseph- The 2013.1.1 update has also been backported to precise via the
Ubuntu Cloud Archive. It is currently sitting in the precise-
grizzly/proposed pocket and will be released into the main, precise-
grizzly/updates pocket when the corresponding 2013.1.1 update for Raring
passes verification.
Blueprint changed by Adam Gandelman:
Whiteboard set to:
User stories:
John is maintaining some openstack juju charms. When he wants to push a
change affecting multiple charms, he does not want to duplicate his work
across bash and shell.
Mike wants to ensure deploying specific configuration
Blueprint changed by Adam Gandelman:
Work items set to:
Work items:
openstack-dashboard python rewrite: TODO
glance python rewrite: TODO
cinder python rewrite: TODO
swift-storage python rewrite: TODO
nova-compute python rewrite: TODO
nova-cloud-controller python rewrite: TODO
Integrate current
Aimon- Please use the grizzly pocket of the Ubuntu Cloud Archive instead
of the trunk PPAs. The PPAs are unsupported. If this is a valid bug
that warrants an update, it will be published to Ubuntu and the Cloud
Archive, not the PPAs. I'm having trouble reproducing this with what we
have packaged
Public bug reported:
observed when upgrading from cinder-api 2012.2.3-0ubuntu2~cloud0 to
1:2013.1-0ubuntu2~cloud0.
The required auth_token middleware has moved from python-keystone to
python-keystoneclient. Cinder's api-paste.ini has been updated to
reflect this:
[filter:authtoken]
Blueprint changed by Adam Gandelman:
Definition Status: New = Review
--
OpenStack Charm work for Saucy/Havana
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
Public bug reported:
cheetah 2.4.4-3ubuntu1 dropped dependency on python-markdown to avoid a
component mismatch (markdown is in universe). Apparently the package
functions fine without it, however, cheetah's requires.txt still lists
it as a dependency:
$ cat Cheetah.egg-info/requires.txt
Is there any way to test this issue using cinder without access to a
storwize device? I've gone as far as creating a mock device using an
ssh server and pointing cinder there, but have not been able to trigger
the issue with the patched and unpatched Ubuntu paramiko packages.
--
You received
Please find the attached test log from the Ubuntu Server Team's CI
infrastructure. As part of the verification process for this bug, the
OpenStack components have been deployed and configured across multiple
nodes using raring-proposed as an installation source. After successful
bring-up and
Test coverage log.
** Attachment added: raring_grizzly_quantum.tar
https://bugs.launchpad.net/bugs/1179626/+attachment/3686266/+files/raring_grizzly_quantum.tar
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Test coverage log.
** Attachment added: raring_grizzly_nova-network.tar
https://bugs.launchpad.net/bugs/1179626/+attachment/3686267/+files/raring_grizzly_nova-network.tar
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: cloud-archive
Status: In
1 - 100 of 879 matches
Mail list logo
