Fixed with upload of 2012.1~e2-0ubuntu3
** Changed in: glance (Ubuntu)
Status: Triaged => 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/907543
Title:
python-glanc
Correction, by e2 snapshot I mean e2 *milestone* (glance
2012.1~e2-0ubuntu1)
** Changed in: glance (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad
** Summary changed:
- Should glance user's shell be /bin/false?
+ Should nova user's shell be /bin/false?
--
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/890362
Title:
Should nova user
*** This bug is a duplicate of bug 907543 ***
https://bugs.launchpad.net/bugs/907543
** This bug has been marked a duplicate of bug 907543
python-glance fails to install during postinst: update-python-modules: not
found
** Changed in: glance (Ubuntu)
Status: New => Fix Released
--
Public bug reported:
Setting up python-prettytable (0.5-1ubuntu2) ...
Setting up python-novaclient (2.6.7~bzr128-0ubuntu1) ...
ubuntu@ip-10-252-25-136:~$ nova
Traceback (most recent call last):
File "/usr/bin/nova", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/pyt
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): TODO
[gandelman-a] nova-network - Add VLAN net manager support: TODO
[gandelman-a] glance - ceph interface
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): TODO
[gandelman-a] nova-network - Add VLAN net manager support: TODO
[gandelman-a] glance - ceph interface
N instance_id' ()
(nova): TRACE:
MySQL 5.5 on Precise has switched from using MyISAM as the default
storage engine to InnoDB. When InnoDB is configured as the default,
migrations need to make sure FK constraints are removed. This seems to
only be an issue on systems that use InnoD
** Changed in: nova
Assignee: Adam Gandelman (gandelman-a) => (unassigned)
** Changed in: nova (Ubuntu)
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
Kenyon--
Looking into this further and other similar bugs, it seems this is the
expected behavior of logrotate. In this case, the logrotate output is
non-fatal and, although annoying, does not cause logrotate to abort its
run and fail to process other rotate configs. Puppet is a special case
in
Public bug reported:
facter (1.6.4-2) unstable; urgency=low
* Move dmidecode from Depends to Recommends (Closes: #651501)
-- Stig Sandbeck Mathisen Fri, 09 Dec 2011 09:40:16
+0100
facter (1.6.4-1) unstable; urgency=low
* New upstream release
* Add dependency on dmidecode
-- Stig San
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a mem
** Changed in: nova (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nova (Ubuntu)
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.
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
- nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): TODO
+ nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
- Deploy openstack-integration-tests in Ubuntu QA lab with target default
configurations: INPROGRESS
- Define re-testing triggers and implement as designed: INPROGRESS
+ [gandelman-a] Deploy openstack-integration-tests in
** Changed in: nova (Ubuntu)
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/916992
Title:
Database migration v064 fails against MySQL 5.5 + Inn
Note: This will likely be marked invalid soon, as the openstackx library
is soon to be marked deprecated and removed in favor of python-
novaclient.
Another note: the osapi_extensions flag has been renamed to
osapi_compute_extensions.
--
You received this bug notification because you are a membe
Jean-Baptiste, thanks for reporting this. Can you provide the
squid.conf that you end up with after upgrade that is causing the
problems? Also, was this an upgrade from squid3 (oneiric) to squid3
(precise), or a transition from squid (oneiric) to squid3 (precise)?
--
You received this bug noti
** Changed in: nova (Ubuntu)
Status: In Progress => Fix Committed
--
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/923817
Title:
nova-network fails due to absence of policy.json
Confirmed that, with the given config, a transition to squid3 results in
403s as described
** Changed in: squid3 (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https:/
@Jean-Baptiste:
The issue is that precise has transitioned to squid3. The new location
for squid.conf is /etc/squid3/squid.conf. After upgrade, squid(3) was
restarted using the default packaged config that was installed at
/etc/squid3/squid.conf after update. Replacing
/etc/squid3/squid.conf
** Changed in: nova (Ubuntu)
Status: New => 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/922232
Title:
Volumes fail to attach without discovery using tgt
To mana
Hi Jens-
Thanks for reporting this. This sounds like a tough one to debug, any
chance you've hit this again since reporting? I assume this is on a
production system and there's no chance of you trying to reproduce on
demand. In the event that you do hit this again, before rebooting, can
you capt
Public bug reported:
CI is picking up a failure of the volumes exercise. I believe this is
a result of: https://review.openstack.org/#change,3586
May just be a packaging bug, but volume attach fails on the compute
node:
12-02-06 13:57:14,819 DEBUG nova.utils [-] Running cmd (subprocess): sudo
** Changed in: nova (Ubuntu)
Status: In Progress => 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/915614
Title:
Add policy.json to packages
To manage notification
*** This bug is a duplicate of bug 926412 ***
https://bugs.launchpad.net/bugs/926412
Seems to be caused by issue described in bug #926412
Fix proposed at https://review.openstack.org/#change,3778 which I've
just verified fixes the volume issue.
Marking as duplicate
** This bug has been mark
@shake-chen,
Thanks for reporting. Are you hitting this on a new installation of
packages or upgrading from a previous version? If an upgrade, does
removing the '=True' from --force_dhcp_release in /etc/nova/nova.conf
resolve the issue for you? The config file that is shipped with a the
newest
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): BLOCKED
[gandelman-a] nova-network - Add VLAN net manager support: TODO
[gandelman-a] glance - ceph interface
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
- [gandelman-a] Deploy openstack-integration-tests in Ubuntu QA lab with target
default configurations: INPROGRESS
+ [gandelman-a] Deploy openstack-integration-tests in Ubuntu QA lab with target
default configurations: DONE
Hi Alvaro-
This is run in the post-installation step of the nova-common package,
which is installed with nova-compute-xen. It is the expected behavior
and happens to help users who want to install all nova components on a
single node and have something ready to use out-of-the-box. Note that
this
policy.json is installed with all nova-* components via nova-common
package
** Changed in: nova (Ubuntu)
Status: Incomplete => Invalid
--
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/bu
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work Items:
- [gandelman-a] Hardware detection and inventory snippet: INPROGRESS
+ [gandelman-a] Hardware detection and inventory snippet: POSTPONED
[zulcss] Add hardware inventory to cobbler API: POSTPONED
[davewalker
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work Items:
[davewalker] replace "install ubuntu cloud" on the CD boot menu with "Cloud,
Cluster or Automated Installation": TODO
- [gandelman-a] add SSL support to cobbler-enlist: TODO
- [gandelman-a] add auto-ge
Hey Andrew, thanks for reporting. It seems there was an error when
forward-porting the FIFO console log patch from oneiric to
precise/essex. I believe Chuck is the process of refreshing it and
fixing it, so it the newer version of the patch will include the changes
required to get a proper libvi
It looks like metadata handler fetches instance IP infomration via
ec2utils.get_ip_info_for_instance():
def get_ip_info_for_instance(context, instance):
"""Return a list of all fixed IPs for an instance"""
try:
return get_ip_info_for_instance_from_cache(instance)
except (Value
Looking at it a bit more with Daviey, it turns out the later calls thru
the network layer will update the cache, but we never get that far
because its consistently returning an outdated cache hit with an empty
floating_ips list.
--
You received this bug notification because you are a member of U
Work being done in the proposal would help here, too:
https://review.openstack.org/#change,4269
--
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/933818
Title:
public-ipv4 metadata url no
openstackx has been removed as a dependency
** 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.
https://bugs.launchpad.net/bugs/906654
Title:
nova should depend
** Changed in: glance (Ubuntu)
Status: In Progress => Fix Released
--
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/932466
Title:
glance db migrations deadlock against precise m
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): BLOCKED
[gandelman-a] nova-network - Add VLAN net manager support: TODO
[gandelman-a] glance - ceph interface
Marking as confirmed as I've run into this last week when deploying to
the CI lab. I've only hit it once and was unable to reproduce during
subsequent deployments. nova-compute was exhausting all memory and
eventually being killed off by OOM killer.
** Also affects: nova
Importance: Undecided
** Changed in: nova (Ubuntu)
Status: New => Confirmed
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
** 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/938763
Title:
nova compute manager traceback during _sync_power_states
Hi Andrew, thanks for the report. To be clear, was this an upgrade from
the Oneiric/Diablo to Preicse/Essex, or an upgrade between version of
Essex? Also, is it correct to assume that, at the time of the upgrade,
there were instances running on the compute node? Thanks
--
You received this bug
** 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/934118
Title:
Floating ips not available to instances after upgrade
To
The following is a list of configuration options from 2.7 that have not
been ported to squid3, as of 3.19:
http://squidcache.cybermirror.org/squid/squid-3.1.19-RELEASENOTES.html#ss6.1
There are many. Currently, squid3 will fail to parse config + start if
any of these yet-to-be-ported options exi
It appears this is a packaging issue, as nova-volume.upstart does not create
/var/lock/nova like other nova-* jobs. We should check that all nova-*
upstart jobs ensure the directory exists, because the commit above adds a
periodic task to all nova services that will fail if the directory is
n
marking invalid as this has been fixed for some time in ubuntu
** Changed in: glance (Ubuntu)
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/928383
Title
Public bug reported:
Error in preinst:
Selecting previously unselected package keystone.
Unpacking keystone (from .../keystone_2012.1~e4-0ubuntu1_all.deb) ...
adduser: The group `keystone' does not exist.
id: keystone: No such user
chown: invalid user: `keystone:keystone'
dpkg: error processing
Matters are slightly more complicated because the existing squid
packages (both the original squid(v2) and squid3) do not track
squid.conf as a conffile, probably because the example configuration is
generated at build time.
After discussing the matter with several Ubuntu devs, it appears there
ar
08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
root@server-22:/var/lib/cloud/instance# curl 169.254.169.254/1.0/1.0/
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
** Affects: nova
Importance: Undecided
Assignee: Adam Gande
Johannes- The bug is that it does not route anywhere. AFAICS, its in
the list (with the rest of the versions reported) to maintain ec2
compatibility. In fat, I came across the issue when testing a tool
designed for EC2 on nova.
On EC2, for example:
adam@ath0:~$ curl http://169.254.169.254/
1.0
** Changed in: keystone (Ubuntu Precise)
Status: In Progress => Fix Released
--
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/881304
Title:
issues with ec2 middleware
To mana
Hey Glen-- Thanks for reporting this and helping us make Ubuntu better!
I believe the issue here is that 'puppet config print' returns 0 on
failure. The maintainer script is 'set -e', but in this case the errors
are not caught. I'm wondering the script should be attempting to parse
"err: " from
** Changed in: puppet (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/950183
Title:
puppetmaster-passenger postinst creates wrong certificate
** Changed in: puppet (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/950183
Title:
puppetmaster-passenger postinst creates wrong certific
Note: As of 2012.1~rc1~20120308.2103-0ubuntu1, keystone.conf now
contains a 'bind_host' option to configure which address the servers
listen.
--
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
** Changed in: nova (Ubuntu)
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/948595
Title:
Default api-paste.ini does not properly route metadat
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
[gandelman-a] Deploy openstack-integration-tests in Ubuntu QA lab with target
default configurations: DONE
Define re-testing triggers and implement as designed: DONE
Collaborate on defining charm use workflow between
** 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/954692
Title:
cannot detach volume from terminated instance
To manage notif
Steps to reproduce:
1. create volume
2. boot an instance (tested with cirros)
3. attach volume
4. in instance: 'sudo poweroff'
5. after kvm machine has stopped on compute node, terminate instance. results
in traceback on compute.log:
(nova.rpc.amqp): TRACE: File
"/usr/lib/python2.7/dist-pa
I believe this has since been fixed:
https://review.openstack.org/#change,4611
This may be a duplicate of bug #914974.
Paul, can you test on a more recent version of nova if you have access
to such a deployment? Using the latest trunk I was unable to reproduce.
--
You received this bug notific
** Changed in: nova
Status: New => In Progress
** Changed in: nova
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://bugs.launchpad.ne
Bogged down with other things ATM, but spent some time looking at this
last night.
nova.compute.manager._shutdown_instance() raises an exception if the
instance is already in POWEROFF state. It looks like this conditional
has existed forever:
if current_power_state == power_state.SHUTOF
Public bug reported:
Creating security groups that authorize themselves (and probably other
groups) cannot be deleted from nova.
To reproduce:
(SIDE NOTE: I couldn't get euca2ools to create the test case because its
using some deprecated authorize_security_group call. To do this, I had
to edit
** 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/956366
Title:
self-referential security groups can not be deleted
To m
Chris-
I'm a little uncomfortable wrapping self.driver.destroy in a try/except
block until there is a common exception language virt drivers can use to
raise specific, fatal exceptions. I'm thinking of a scenario where
libvirt/xs cannot shutdown instance, raises, and compute continues on
with vol
** Changed in: nova (Ubuntu)
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/938702
Title:
"nova-manage fixed list" no longer works
To manage n
** Changed in: nova (Ubuntu)
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/934534
Title:
metadata ami-launch-index always returning "1"
To ma
** 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/934515
Title:
--meta key=value cannot accept
*** This bug is a duplicate of bug 943031 ***
https://bugs.launchpad.net/bugs/943031
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://
Public bug reported:
Using most recent Ubuntu packages, the keystone-all deamon does not log
anything to its default logfile /var/log/keystone/keystone.log
The current upstream source ships a logging.conf.sample that seems to be
lifted directly from the glance project. As a work around, the ubun
** Changed in: nova (Ubuntu)
Importance: Undecided => High
--
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/959289
Title:
missing nova-consoleauth init/init.d file
To manage notifica
** 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/959426
Title:
nova services start before mysql on boot
To manage notif
** Changed in: nova (Ubuntu)
Importance: Undecided => Critical
--
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/960276
Title:
a bad AMI can hang an entire compute node
To manage noti
We've been carrying a nova patch to resolve a possible DoS in Bug
#832507 ( libvirt-use-console-pipe.patch ) I've confirmed that this
patch introduces a deadlock somewhere when the serial console gets
spammed. 'dd if=/dev/urandom of=/dev/ttyS0 bs=1024 count=1500' from
within the instance is enou
*** This bug is a duplicate of bug 948719 ***
https://bugs.launchpad.net/bugs/948719
** This bug has been marked a duplicate of bug 948719
uninstall keystone error
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubu
@Vincent
Here is the logging conf sitting in the -proposed branch linked here, to
be uploaded with rc1: http://paste.ubuntu.com/895301/
Note that the default log level doesn't produce much output, changing
[logger_root]
level=WARNING
handlers=file
to
[logger_root]
level=DEBUG
handlers=file
pr
I spent some time on this yestreaday, to clarify-
I don't really see the git checkouts an issue. The pending test to
swift tests that do this do so only if there is an error importing it
from already installed libraries. That is, it should be imported
locally instead of cloned remotely if we lis
This is not resolved by the fix for bug 943031 which, AFAICS, fixes the
issue of an existing db connection going away. The bug here is at
service start up, ie starting nova-compute with a mysql server that is
not up (yet) ends in:
(nova): TRACE: OperationalError: (OperationalError) (2003, "Can't
The fix in bug 943031 was recently re-implemented in Glance @
https://review.openstack.org/#change,5552 While this change currently doesn't
resolve the issue of an unreachable database on service startup, it can easily
be extended to check the ability to actually connect thru the sqlalchemy eng
** 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/965356
Title:
unnecessary dep: nova-api -> nova-cert
To manage notification
** Package changed: openstack-dashboard (Ubuntu) => python-novaclient
(Ubuntu)
--
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/959262
Title:
[Errno 13] Permission denied: '
** Also affects: nova
Importance: Undecided
Status: New
** Tags added: essex-rc-potential
--
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/959262
Title:
[Errno 13
** Changed in: python-novaclient (Ubuntu)
Importance: Undecided => High
--
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/959262
Title:
[Errno 13] Permission denied: '/var
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
--
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/960276
Title:
a bad AMI can hang an entire compute node
To manage notif
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
** Changed in: glance (Ubuntu)
Status: New => Triaged
--
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/959426
Title
Thanks Thierry. Is this something we should expect to trickle into
milestone-proposed, or should we prepare to carry a patch?
--
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/9
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
nova-cloud-controller - Split into charms after Juju supports multiple units
on a machine (or colocation): BLOCKED
- [gandelman-a] nova-network - Add VLAN net manager support: TODO
+ [gandelman-a] nova-network - Add VLAN
** Package changed: keystone (Ubuntu) => horizon
--
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/966038
Title:
Downloadable user OpenStack credential files (settings... OpenStack)
Blueprint changed by Adam Gandelman:
Whiteboard changed:
Work items:
[gandelman-a] Deploy openstack-integration-tests in Ubuntu QA lab with target
default configurations: DONE
Define re-testing triggers and implement as designed: DONE
- Collaborate on defining charm use workflow between
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubun
Did a bunch of house-cleaning on the nova packaging today, current list
of offences has dropped considerably, but still needs some work:
W: nova-compute: executable-not-elf-or-script
usr/share/pyshared/nova/rootwrap/compute.py
W: nova-compute: maintainer-script-needs-depends-on-adduser postinst
W
Fixed in Ubuntu with rc2 upload (nova-2012.1~rc2-0ubuntu1)
** Changed in: nova (Ubuntu)
Status: Triaged => 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/959426
Titl
Fixed in Ubuntu as of glance-2012.1~rc2-0ubuntu1
** Changed in: glance (Ubuntu)
Status: Triaged => 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/959426
Title:
nov
Fixed in Ubuntu as of python-novaclient 2012.1~rc2-0ubuntu1
** Changed in: python-novaclient (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.la
This is a bug, and is not surfacing in devstack testing because devstack
hasn't yet moved to precise. Oneiric MySQL is configured with MyISAM
storage engine by default, which means FK constraints are non-existent
in the backend and are essentially meaningless. MySQL on Precise uses
InnoDB as the
** Branch unlinked: lp:~openstack-ubuntu-testing/horizon/precise-essex-
proposed
--
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/966069
Title:
/etc/apache2/conf.d/dashboard.conf cont
Marking as invalid. After resolving Bug #959426 , glance and nova now
retry database connection at service startup at a configurable interval,
which also resolves the issue when the database is located on another
host but is unreachable.
** Changed in: glance (Ubuntu)
Status: New => Invali
** Changed in: glance (Ubuntu)
Status: New => Fix Released
--
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/967887
Title:
Glance's auto-recovery of db connections is incompatibl
301 - 400 of 887 matches
Mail list logo
