Any word on seeing this package published? This ticket hasn't seen an
update in 4 months. I can confirm that Ubuntu 12.04.3 Server out of the
box on amd64 and i386 will not work with DRDB and requires smb's fixed
debs from #17 and #18 (respectively).
--
You received this bug notification because
It is a bug when its impossible to set the initial password so it always
tells you that your password is invalid because there is no password set
for the keyring. The issue here is that the code Ubuntu adds for Nova
client initializes the keyring incorectly.
** Changed in: python-novaclient
** Also affects: python-novaclient (Ubuntu)
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/1020238
Title:
nova client keeps
You can reproduce this problem very quickly on a freshly installed
Ubuntu 12.04 system with Folsom by following the user manual line for
line due to bug #1064749
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Here's the debug info from Folsom.
$ nova --debug delete 3935bacf-63c5-4b19-9375-f067d75d56e6
REQ: curl -i http://192.168.200.135:35357/v2.0/tokens -X POST -H
Content-Type: application/json -H Accept: application/json -H User-
Agent: python-novaclient -d '{auth: {tenantName: dev,
As pointed out to me by ev0ldave in #openstack the way to fix this is to
figure out exactly what the instance ID is.
$ mysql -u root -p
mysql USE nova;
mysql SELECT id, host, hostname FROM instances;
...
mysql UPDATE instances SET deleted=1, deleted_at=2012-10-10 14:56:30,
vm_state=deleted WHERE
