[Yahoo-eng-team] [Bug 1668267] [NEW] Nova ignores to update the quota for VMs in error
Public bug reported: When VMs goes to ERROR state after the block device mapping nova updates the quota for adding the instance/CPU/RAM to the quota but when we delete those VMs nova forgets the release/update the CPU/RAM/Instance quota Steps to reproduce: 1. Set the quota limit for volumes to 10 and VMs to 50 2. create 20 VMs by using option boot from volume from horizon Observation: 10 VMs comes to active state and 10 goes to ERROR state (As expected) 3. delete all VMs Expectation: CPU/RAM/Instance used quota will come to "0" Actual: CPU/RAM/Instance quota is not coming to "0" CPU used quota shows 10 (As the VM is created from M1.SMALL flavor) Instance quota shows 10 RAM quota shows 20480MB which is quite unexpected Its seems it is a blocker for Ocata release I am running from the stable/Ocata ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1668267 Title: Nova ignores to update the quota for VMs in error Status in OpenStack Compute (nova): New Bug description: When VMs goes to ERROR state after the block device mapping nova updates the quota for adding the instance/CPU/RAM to the quota but when we delete those VMs nova forgets the release/update the CPU/RAM/Instance quota Steps to reproduce: 1. Set the quota limit for volumes to 10 and VMs to 50 2. create 20 VMs by using option boot from volume from horizon Observation: 10 VMs comes to active state and 10 goes to ERROR state (As expected) 3. delete all VMs Expectation: CPU/RAM/Instance used quota will come to "0" Actual: CPU/RAM/Instance quota is not coming to "0" CPU used quota shows 10 (As the VM is created from M1.SMALL flavor) Instance quota shows 10 RAM quota shows 20480MB which is quite unexpected Its seems it is a blocker for Ocata release I am running from the stable/Ocata To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1668267/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1564110] Re: OpenStack should support MySQL Cluster (NDB)
** Changed in: nova Status: Opinion => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564110 Title: OpenStack should support MySQL Cluster (NDB) Status in Ceilometer: Incomplete Status in Cinder: Opinion Status in Glance: New Status in heat: New Status in Ironic: Confirmed Status in OpenStack Identity (keystone): Incomplete Status in neutron: Incomplete Status in OpenStack Compute (nova): Confirmed Status in oslo.db: New Bug description: oslo.db assumes that a MySQL database can only have a storage engine of InnoDB. This causes complications for OpenStack to support other MySQL storage engines, such as MySQL Cluster (NDB). Oslo.db should have a configuration string (i.e. mysql_storage_engine) in the oslo_db database group that can be used by SQLalchemy, Alembic, and OpenStack to implement the desired support and behavior for alternative MySQL storage engines. I do have a change-set patch for options.py in oslo_db that will add this functionality. I'll post once I'm added to the CLA for OpenStack. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1564110/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1267551] [NEW] nova not able to delete secgroup using ID
Public bug reported: While trying to delete a secgroup using nova secgroup-delete command using secgroup ID nova fails to delete the secgroup The issue comes when we have multiple secgroup with same name ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1267551 Title: nova not able to delete secgroup using ID Status in OpenStack Compute (Nova): New Bug description: While trying to delete a secgroup using nova secgroup-delete command using secgroup ID nova fails to delete the secgroup The issue comes when we have multiple secgroup with same name To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1267551/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 893586] Re: Snapshot while creating: stays in queue state forever and instance goes to several intermediate states like ERROR and SHUTOFF state
Reopening as per the above comment... ** Changed in: nova Status: Invalid = New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/893586 Title: Snapshot while creating: stays in queue state forever and instance goes to several intermediate states like ERROR and SHUTOFF state Status in OpenStack Compute (Nova): New Bug description: 1. Run a vm 2. Create a snapshot of running instance 3. Wait till snapshot is in active state 4. Create a vm from snapshot 5. when the vm is in building state take a snapshot of the vm Observation: 1. image stays in queue state for ever 2. instance goes to shutoff state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/893586/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 955792] Re: No public IP addresses listed in server representation
Please feel free to reopen if the issue reoccured
** Changed in: nova
Status: In Progress = Confirmed
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/955792
Title:
No public IP addresses listed in server representation
Status in OpenStack Compute (Nova):
Invalid
Bug description:
1. Create a VM
2. Wait till active
3. Attach a public ip to VM
4. SSH to VM using nova ssh
routray@ubuntu:~/Desktop/copy/st1$ nova ssh
usage: nova ssh [--private] [--login login] server
error: too few arguments
Try `nova help ssh' for more information.
routray@ubuntu:~/Desktop/copy/st1$ nova --debug ssh 106204
connect: (cs.systest.aw1.hpcloud.net, 35357)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
cs.systest.aw1.hpcloud.net:35357\r\nContent-Length: 150\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{auth:
{tenantName: satya.rout...@hp.com-default-tenant, passwordCredentials:
{username: satya.rout...@hp.com, password: ca$hc0w!4#}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Length: 3564
header: Content-Type: application/json
header: Date: Wed, 14 Mar 2012 10:29:28 GMT
header: Cache-Control: no-cache
header: Expires: -1
header: Pragma: no-cache
header: Server: Apache-Coyote/1.1
connect: (compute.systest.aw1.hpcloud.net, 443)
send: u'GET /v1.1/73438783064199/servers/106204 HTTP/1.1\r\nHost:
compute.systest.aw1.hpcloud.net\r\nx-auth-project-id:
satya.rout...@hp.com-default-tenant\r\nx-auth-token:
HPAuth_4f606bd1e4b0b829e4428dc9\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Length: 1015
header: Content-Type: application/json; charset=UTF-8
header: Date: Wed, 14 Mar 2012 10:29:32 GMT
ERROR: No public address found.
After little more debugging
I found that the public ip assigned is listed under private
snip
RESP:{'date': 'Thu, 15 Mar 2012 07:17:00 GMT', 'status': '200',
'content-length': '1015', 'content-type': 'application/json; charset=UTF-8',
'content-location':
u'https://compute.systest.aw1.hpcloud.net/v1.1/73438783064199/servers/106204#39;}
{server: {status: ACTIVE, updated: 2012-03-15T06:58:15Z, hostId:
d303b97b5c36df3811814d8a707b22c219f622f88fb8ab397028e683, user_id:
47101178638744, name: vm01, links: [{href:
https://compute.systest.aw1.hpcloud.net/v1.1/73438783064199/servers/106204;,
rel: self}, {href:
https://compute.systest.aw1.hpcloud.net/73438783064199/servers/106204;, rel:
bookmark}], addresses: {private: [{version: 4, addr: 10.12.15.192},
{version: 4, addr: 15.184.120.60}]}, tenant_id: 73438783064199,
image: {id: 3172, links: [{href:
https://compute.systest.aw1.hpcloud.net/73438783064199/images/3172;, rel:
bookmark}]}, created: 2012-03-14T10:15:12Z, uuid:
c81949b6-dd1e-4993-ae4f-4c0e5b4225d
b, accessIPv4: , accessIPv6: , key_name: satya, progress: 100,
flavor: {id: 100, links: [{href:
https://compute.systest.aw1.hpcloud.net/73438783064199/flavors/100;, rel:
bookmark}]}, config_drive: , id: 106204, metadata: {}}}
snip
Might be this is the cause of this issue
Guessing if we will have a public feild where the associated public ip
will be located this issue may go away
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/955792/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
