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
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
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.tar
https://bugs.launchpad.net/bugs/1097451/+attachment/3651753/+files/quantal_folsom.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test coverage log.
** Attachment added: quantal_folsom_nova-volume.tar
https://bugs.launchpad.net/bugs/1097451/+attachment/3651754/+files/quantal_folsom_nova-volume.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test coverage log.
** Attachment added: quantal_folsom_quantum.tar
https://bugs.launchpad.net/bugs/1097451/+attachment/3651755/+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.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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
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
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/1055929/+attachment/3651775/+files/quantal_folsom_nova-volume.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-keystoneclient (Ubuntu)
Status: New = Confirmed
** Changed in: python-keystoneclient (Ubuntu)
Importance: Undecided = Medium
** Tags added: cloud-archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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),
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),
Sina-
The propose patch did not get accepted for merging into python-
glanceclient and has since been abandoned/expired. The issue is still
unresolved upstream so you should not expect a fix to make its way out
via Ubuntu or the Ubuntu Cloud Archive until the bug has been addressed
in the
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
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
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
Bugs, which is subscribed to Ubuntu.
** Changed in: keystone (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158563
Title:
After grizzly upgrade, EC2 API requests fail:Could not find:
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
Bugs, which is subscribed
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:
$
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:
$
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
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-glanceclient (Ubuntu)
Status: New = Confirmed
** Changed in: python-glanceclient (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are
Lorin- What is the kernel version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029430
Title:
KVM guests networking issues with no virbr0 and with vhost_net kernel
modules loaded
To manage
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
** 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
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155458
Title:
500 response when trying to create a server from a deleted image
To
Public bug reported:
(Apologies for incorrect desktop environment terminology)
Just upgraded to 13.04 on my laptop. terminator seems to be having
issues with the global menu bar. That is, the terminator windows title
bar ends up being managed in the global menu bar, and leaves me no way
of
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
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
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
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
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 =
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079022
Title:
nova --version does not function as intended
To manage
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 =
Public bug reported:
Seems to affect both Quantal and Raring currently.
# apt-cache policy python-jenkinsapi
python-jenkinsapi:
Installed: (none)
Candidate: 0.1.11-5
Version table:
0.1.11-5 0
500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages
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
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
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
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
** 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
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
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
- 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
This isn't isolated to the PPA, the current Quantum package in Raring
(2013.1~g2-0ubuntu1) suffers from the same issue. Seems to be a number
of binaries cross-referenced between different *.install without the
required breaks/replaces.
--
You received this bug notification because you are a
For reference:
Current raring package 2013.1~g2-0ubuntu1 contains conflicts on the
following:
bin/quantum-ns-metadata-proxy in ('quantum-server.install',
'quantum-l3-agent.install')
bin/quantum-metadata-agent in ('quantum-server.install',
'quantum-l3-agent.install')
In our trunk packaging
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:
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:
Looks like the RestProxy plugin is offered as part of the bigswitch
plugin @ $src/quantum/quantum/plugins/bigswitch and likely needs its own
binary package that is in charge of installing the required config
(shipped in $src/quantum/etc/quantum/bigswitch). I do not know enough
about the plugin to
** 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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055929
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116671
Title:
Meta bug for tracking Openstack 2012.2.3 Stable Update
To
Public bug reported:
Please sync stevedore 0.8-2 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* debian/rules: Fix testsuite so that it will be
FTBFS if the testsuite fails.
* debian/rules: Fix testsuite so that it will be
FTBFS if the
** 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
** Changed in: glance
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100803
Title:
Glance install fails with Ubuntu Testing Packages
To manage notifications about this
Having trouble reproducing this on a fresh 12.04 system. Even tried
purposely installing against an older sqlalchemy version. Are you sure
there is not something wrong with your sqlalchemy module? python -c
'from sqlalchemy import exceptions as sa_exceptions' should give you an
idea.
**
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100491
401 - 500 of 2059 matches
Mail list logo
