[Yahoo-eng-team] [Bug 1617362] [NEW] Nova 'ComputeManager._destroy_evacuated_instances' method doesn't send notifications
Public bug reported: The community manager has a way to notify about instance usage - notify_about_instance_usage. Currently the _destroy_evacuated_instances does not have any notifications when all the evacuated instances are destroyed. A notification should be sent when this method completes and any instance is actually destroyed. https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L627 ** 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/1617362 Title: Nova 'ComputeManager._destroy_evacuated_instances' method doesn't send notifications Status in OpenStack Compute (nova): New Bug description: The community manager has a way to notify about instance usage - notify_about_instance_usage. Currently the _destroy_evacuated_instances does not have any notifications when all the evacuated instances are destroyed. A notification should be sent when this method completes and any instance is actually destroyed. https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L627 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1617362/+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 1604475] [NEW] TypeError: live_migrate_instance() got an unexpected keyword argument 'async'
Public bug reported: During live migration, this unexpected API error occur. The live migration failed. Error in the nova-api.log: 2016-07-19 02:52:59.734 3825 INFO nova.osapi_compute.wsgi.server [req-7ecad794-1fea-4815-a9d9-5fe2ab829c53 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 a3b6f61367f64e23aad54feb8255f4c1 - - -] 9.109.223.198,127.0.0.1 "GET /v2.1/a3b6f61367f64e23aad54feb8255f4c1/storage-viable-hosts?instance_uuid=5b7cb076-53ca-47b6-891a-95ff00d6dd70 HTTP/1.1" status: 200 len: 443 time: 0.1453900 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions [req-c2bf4983-fc1f-415e-9011-4f626972db87 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 a3b6f61367f64e23aad54feb8255f4c1 - - -] Unexpected exception in API method 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in wrapper 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/migrate_server.py", line 100, in _migrate_live 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions disk_over_commit, host, force) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 165, in inner 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return function(self, context, instance, *args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 172, in _wrapped 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return fn(self, context, instance, *args, **kwargs) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 146, in inner 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions return f(self, context, instance, *args, **kw) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 3322, in live_migrate 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions request_spec=request_spec, async=async) 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions TypeError: live_migrate_instance() got an unexpected keyword argument 'async' 2016-07-19 02:53:03.764 3827 ERROR nova.api.openstack.extensions 2016-07-19 02:53:03.766 3827 INFO nova.api.openstack.wsgi [req-c2bf4983-fc1f-415e-9011-4f626972db87 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 a3b6f61367f64e23aad54feb8255f4c1 - - -] HTTP exception thrown: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. The issue appears to be caused by this changeset: https://review.openstack.org/#/c/36/ While the 'async' argument was added to the conductor's ComputeTaskAPI.live_migrate_instance, the 'async' argument was not added to the conductor's LocalComputeTaskAPI.live_migrate_instance. My current Nova config file has this set: [conductor] use_local = True ** 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/1604475 Title: TypeError: live_migrate_instance() got an unexpected keyword argument 'async' Status in OpenStack Compute (nova): New Bug description: During live migration, this unexpected API error occur. The live migration failed. Error in the nova-api.log: 2016-07-19 02:52:59.734 3825 INFO nova.osapi_compute.wsgi.server [req-7ecad794-1fea-4815-a9d9-5fe2ab829c53 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 a3b6f61367f64e23aad54feb8255f4c1 - - -] 9.109.223.198,127.0.0.1 "GET
[Yahoo-eng-team] [Bug 1583235] [NEW] changes in an instance's description are not dynamically reflected
Public bug reported:
Issue:
A change in an instance's "description" attribute is not dynamically reflected.
Steps to Reproduce:
1.Updates the editable attribute description of the instance using API
PUT /v2.1/{tenant_id}/servers/{server_id}
Expected Result:
Instance Description field changes should be dynamically reflected.
A notification should be sent on the instance to indicate a change in the
instance's description.
Actual Result:
Instance Description field changes are not dynamically reflected.
No notification is sent.
** 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/1583235
Title:
changes in an instance's description are not dynamically reflected
Status in OpenStack Compute (nova):
New
Bug description:
Issue:
A change in an instance's "description" attribute is not dynamically
reflected.
Steps to Reproduce:
1.Updates the editable attribute description of the instance using API
PUT /v2.1/{tenant_id}/servers/{server_id}
Expected Result:
Instance Description field changes should be dynamically reflected.
A notification should be sent on the instance to indicate a change in the
instance's description.
Actual Result:
Instance Description field changes are not dynamically reflected.
No notification is sent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1583235/+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 1567024] Re: updated VM name leaves libvirt domain behind after deletion
** Changed in: nova
Status: Opinion => 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/1567024
Title:
updated VM name leaves libvirt domain behind after deletion
Status in OpenStack Compute (nova):
New
Bug description:
After successfully updating the name of an instance (from a libvirt/KVM
host), I proceeded to delete the instance.
The instance was successfully deleted. However, upon using "virsh list
--all", it can be seen that the domain has not been undefined.
Steps to Reproduce:
1. Setup instance with a libvirt/KVM host and SVC storage
2. Spawn a VM called "test-vm"
API --> POST https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers
3. Update the VM with a new name "new-name-vm"
API --> PUT
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
body: {{'name': 'new-name-vm'}}
4. Delete the VM
API --> DELETE
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
Expected Results:
The VM to be deleted and the libvirt domain to be destroyed and undefined.
"virsh list --all" should return:
virsh list --all
IdName State
Actual Results:
The VM is deleted but the domain was not undefined and still appears on the
KVM using "virsh list --all".
"virsh list --all" returned:
virsh list --all
IdNameState
---
22test-vm-5334ead7-0016 running
Version of libvirt: libvirtd (libvirt) 1.2.16
Version of Nova: 13.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1567024/+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 1567024] [NEW] updated VM name leaves libvirt domain behind after deletion
Public bug reported:
After successfully updating the name of an instance (from a libvirt/KVM host),
I proceeded to delete the instance.
The instance was successfully deleted. However, upon using "virsh list --all",
it can be seen that the domain has not been undefined.
Steps to Reproduce:
1. Setup instance with a libvirt/KVM host and SVC storage
2. Spawn a VM called "test-vm"
API --> POST https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers
3. Update the VM with a new name "new-name-vm"
API --> PUT
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
body: {{'name': 'new-name-vm'}}
4. Delete the VM
API --> DELETE
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
Expected Results:
The VM to be deleted and the libvirt domain to be destroyed and undefined.
"virsh list --all" should return:
virsh list --all
IdName State
Actual Results:
The VM is deleted but the domain was not undefined and still appears on the KVM
using "virsh list --all".
"virsh list --all" returned:
virsh list --all
IdNameState
---
22test-vm-5334ead7-0016 running
Version of libvirt: libvirtd (libvirt) 1.2.16
Version of Nova: 13.0.0
** 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/1567024
Title:
updated VM name leaves libvirt domain behind after deletion
Status in OpenStack Compute (nova):
New
Bug description:
After successfully updating the name of an instance (from a libvirt/KVM
host), I proceeded to delete the instance.
The instance was successfully deleted. However, upon using "virsh list
--all", it can be seen that the domain has not been undefined.
Steps to Reproduce:
1. Setup instance with a libvirt/KVM host and SVC storage
2. Spawn a VM called "test-vm"
API --> POST https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers
3. Update the VM with a new name "new-name-vm"
API --> PUT
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
body: {{'name': 'new-name-vm'}}
4. Delete the VM
API --> DELETE
https://:8774/v2.1/da0be0d560f541d7acccb66104ebe094/servers/5334ead7-4bd7-4f81-8b41-d833ebf52a9b
Expected Results:
The VM to be deleted and the libvirt domain to be destroyed and undefined.
"virsh list --all" should return:
virsh list --all
IdName State
Actual Results:
The VM is deleted but the domain was not undefined and still appears on the
KVM using "virsh list --all".
"virsh list --all" returned:
virsh list --all
IdNameState
---
22test-vm-5334ead7-0016 running
Version of libvirt: libvirtd (libvirt) 1.2.16
Version of Nova: 13.0.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1567024/+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 1565859] [NEW] Can't detach volume from an instance
Public bug reported: Steps to Reproduce: 1. Setup instance with a libvirt/KVM host and SVC storage 2. Spawn a VM 3. Attach a volume to the VM 4. Wait for volume attachment to complete successfully 5. Detach the volume Expected Result: 1. The volume is detached from the VM 2. The volume's status becomes "Available" 3. The volume can be deleted. Actual result: 1. Volume remains attached to the VM (waited over 10 minutes) 2. The volume's state stays "In-Use" Logs: 016-03-24 16:34:13.852 143842 INFO nova.compute.resource_tracker [-] Final resource view: name=C387f19U21-KVM phys_ram=260533MB used_ram=4608MB phys_disk=545GB used_disk=40GB total_vcpus=160 used_vcpus=2 pci_stats=[] 2016-03-24 16:34:14.081 143842 INFO nova.compute.resource_tracker [-] Compute_service record updated for C387f19U21_KVM:C387f19U21-KVM 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall [-] Dynamic interval looping call 'oslo_service.loopingcall._func' failed 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall Traceback (most recent call last): 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py", line 136, in _run_loop 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall result = func(*self.args, **self.kw) 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py", line 377, in _func 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall return self._sleep_time 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall self.force_reraise() 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall six.reraise(self.type_, self.value, self.tb) 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py", line 356, in _func 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall result = f(*args, **kwargs) 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/guest.py", line 342, in _do_wait_and_retry_detach 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall reason=reason) 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall DeviceDetachFailed: Device detach failed for vdb: Unable to detach from guest transient domain.) 2016-03-24 16:34:44.919 143842 ERROR oslo.service.loopingcall 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [req-fab1608e-cffe-40f9-82d0-a4c7a9cebf10 3ebcf1a38bc7b4977b7f8da32faad97bdef843372a670bb2817f8a066f042b9b e10bc17f58d8499a8fab1b05687123e5 - - -] [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] Failed to detach volume 4221ccad-0f98-4f78-ad06-92ea4941afc1 from /dev/vdb 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] Traceback (most recent call last): 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 4767, in _driver_detach_volume 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] encryption=encryption) 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1469, in detach_volume 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] wait_for_detach() 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] File "/usr/lib/python2.7/site-packages/oslo_service/loopingcall.py", line 385, in func 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] return evt.wait() 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] File "/usr/lib/python2.7/site-packages/eventlet/event.py", line 121, in wait 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] return hubs.get_hub().switch() 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] File "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch 2016-03-24 16:34:44.921 143842 ERROR nova.compute.manager [instance: 88724ae0-38d6-4b06-9236-7d5f4d6d6cd6] return self.greenlet.switch() 2016-03-24 16:34:44.921 143842 ERROR
[Yahoo-eng-team] [Bug 1547197] [NEW] "Additional properties are not allowed" message not getting translated
Public bug reported:
During a Nova v2.1 request, the message "Additional properties are not
allowed" is not being translated. Other parts of the API request are
being translated, but the error message seems to be hard-coded in
English.
Example:
URL:
https://9.47.82.183/powervc/openstack/compute/v2.1/dbcb06068c6e4a3fb59326a0bce653f0/os-hosts/ip9_114_181_60
Body:
{
"registration": {
"host_display_name": "MyKVMHost_updated1",
"access_ip": "912.123.233.44",
"user_id": "root",
"password": "Passw0rd"
}
}
Response:
400
{"badRequest": {"message": "Additional properties are not allowed
(u'registration' was unexpected)", "code": 400}}
** Affects: nova
Importance: Undecided
Assignee: Lauren Taylor (lmtaylor)
Status: New
** Changed in: nova
Assignee: (unassigned) => Lauren Taylor (lmtaylor)
--
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/1547197
Title:
"Additional properties are not allowed" message not getting translated
Status in OpenStack Compute (nova):
New
Bug description:
During a Nova v2.1 request, the message "Additional properties are not
allowed" is not being translated. Other parts of the API request are
being translated, but the error message seems to be hard-coded in
English.
Example:
URL:
https://9.47.82.183/powervc/openstack/compute/v2.1/dbcb06068c6e4a3fb59326a0bce653f0/os-hosts/ip9_114_181_60
Body:
{
"registration": {
"host_display_name": "MyKVMHost_updated1",
"access_ip": "912.123.233.44",
"user_id": "root",
"password": "Passw0rd"
}
}
Response:
400
{"badRequest": {"message": "Additional properties are not allowed
(u'registration' was unexpected)", "code": 400}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1547197/+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 1531256] Re: remove get_lock policy action and method
** Changed in: nova Status: In Progress => Fix Released ** Changed in: nova Status: Fix Released => 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/1531256 Title: remove get_lock policy action and method Status in OpenStack Compute (nova): Invalid Bug description: The get_lock method in compute/api.py is no longer in use or being called in Nova. Need to remove the get_lock method and the get_lock policy action from the default policy.json To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1531256/+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 1531256] [NEW] remove get_lock policy action and method
Public bug reported: The get_lock method in compute/api.py is no longer in use or being called in Nova. Need to remove the get_lock method and the get_lock policy action from the default policy.json ** Affects: nova Importance: Undecided Assignee: Lauren Taylor (lmtaylor) Status: New ** Changed in: nova Assignee: (unassigned) => Lauren Taylor (lmtaylor) -- 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/1531256 Title: remove get_lock policy action and method Status in OpenStack Compute (nova): New Bug description: The get_lock method in compute/api.py is no longer in use or being called in Nova. Need to remove the get_lock method and the get_lock policy action from the default policy.json To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1531256/+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 1504666] Re: RemoteError not properly caught during live migraion
There is no error. Made a mistake in debugging. Canceling this bug.
** Changed in: nova
Status: Incomplete => 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/1504666
Title:
RemoteError not properly caught during live migraion
Status in OpenStack Compute (nova):
Invalid
Bug description:
API fails during live migration with a 500 internal server error.
https://127.0.0.1:8774/v2/8c87f173ba7c47cbb4f57eebe85479c1/servers/d53b954a-7323-4d88-a5fc-14c0672a704e/action
{
"os-migrateLive": {
"host": "8231E2D_109EFCT",
"block_migration": false,
"disk_over_commit": false
}
}
The correct error should be 400 BadRequest as the error raise should
be RemoteError, not a MigrationError
Nova-api logs:
MigrationError(u'Migration error: Remote error:error message)
[u'Traceback (most recent call last):\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 142, in _dispatch_and_reply\nexecutor_callback))\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 186, in _dispatch\nexecutor_callback)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 129, in _do_dispatch\nresult = func(ctxt, **new_args)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 89, in
wrapped\npayload)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 72, in
wrapped\nreturn f(self, context, *args, **kw)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 352, in
decorated_function\nLOG.warning(msg, e, instance=instance)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 325, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 89, in
wrapped\npayload)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 72, in
wrapped\nreturn f(self, context, *args, **kw)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 402, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 380, in
decorated_function\nkwargs[\'instance\'], e, sys.exc_info())\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 368, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5023,
in check_can_live_migrate_destination\nblock_migration,
disk_over_commit)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
raise exception.MigrationError(reason=six.text_type(ex))\n'
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1504666/+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 1504666] [NEW] RemoteError not properly caught during live migraion
Public bug reported:
API fails during live migration with a 500 internal server error.
https://127.0.0.1:8774/v2/8c87f173ba7c47cbb4f57eebe85479c1/servers/d53b954a-7323-4d88-a5fc-14c0672a704e/action
{
"os-migrateLive": {
"host": "8231E2D_109EFCT",
"block_migration": false,
"disk_over_commit": false
}
}
The correct error should be 400 BadRequest as the error raise should be
RemoteError, not a MigrationError
Nova-api logs:
MigrationError(u'Migration error: Remote error:error message)
[u'Traceback (most recent call last):\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line
142, in _dispatch_and_reply\nexecutor_callback))\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line
186, in _dispatch\nexecutor_callback)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line
129, in _do_dispatch\nresult = func(ctxt, **new_args)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 89, in
wrapped\npayload)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 72, in
wrapped\nreturn f(self, context, *args, **kw)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 352, in
decorated_function\nLOG.warning(msg, e, instance=instance)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 325, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 89, in
wrapped\npayload)\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/exception.py", line 72, in
wrapped\nreturn f(self, context, *args, **kw)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 402, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 380, in
decorated_function\nkwargs[\'instance\'], e, sys.exc_info())\n', u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 368, in
decorated_function\nreturn function(self, context, *args, **kwargs)\n', u'
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5023, in
check_can_live_migrate_destination\nblock_migration, disk_over_commit)\n',
u'
File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in
__exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'
raise exception.MigrationError(reason=six.text_type(ex))\n'
** Affects: nova
Importance: Undecided
Assignee: Lauren Taylor (lmtaylor)
Status: New
** Changed in: nova
Assignee: (unassigned) => Lauren Taylor (lmtaylor)
--
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/1504666
Title:
RemoteError not properly caught during live migraion
Status in OpenStack Compute (nova):
New
Bug description:
API fails during live migration with a 500 internal server error.
https://127.0.0.1:8774/v2/8c87f173ba7c47cbb4f57eebe85479c1/servers/d53b954a-7323-4d88-a5fc-14c0672a704e/action
{
"os-migrateLive": {
"host": "8231E2D_109EFCT",
"block_migration": false,
"disk_over_commit": false
}
}
The correct error should be 400 BadRequest as the error raise should
be RemoteError, not a MigrationError
Nova-api logs:
MigrationError(u'Migration error: Remote error:error message)
[u'Traceback (most recent call last):\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 142, in _dispatch_and_reply\nexecutor_callback))\n', u'
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py",
line 186, in _dispatch\nexecutor_callback)\n
[Yahoo-eng-team] [Bug 1300972] Re: os-simple-tenant-usage is returning with the response code 400
This is now a logging issue. The REST os-simple-tenant-usage returns a
response code 400 which is correct. However, a trace shouldn't be in
the log when not all the requirements are being passed.
** Summary changed:
- os-simple-tenant-usage is returning with the response code 400
+ os-simple-tenant-usage: printing trace in logs if not passing all requirements
** 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/1300972
Title:
os-simple-tenant-usage: printing trace in logs if not passing all
requirements
Status in OpenStack Compute (Nova):
New
Bug description:
REST os-simple-tenant-usage is returning with a response code 400
from api.log:
2014-03-20 11:27:58.044 49351 INFO nova.osapi_compute.wsgi.server
[req-b653843a-de1c-4267-af33-7f7a9c5fa99d 0 b38c2504810f437883a5b57a8b13fe7f]
9.41.223.193,127.0.0.1 GET
/v2/b38c2504810f437883a5b57a8b13fe7f/os-simpletenant-usage HTTP/1.1 status:
404 len: 302 time: 0.6078889
2014-03-20 11:28:04.221 49351 ERROR nova.api.openstack.wsgi
[req-09d455d6-c963-4729-b1b6-082bd04cfe8b 0 b38c2504810f437883a5b57a8b13fe7f]
NV-46FDF46 Exception handling resource: strptime() argument 1 must be string,
not None
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi Traceback (most
recent call last):
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 991, in
_process_stack
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi action_result
= self.dispatch(meth, request, action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 1078, in
dispatch
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi return
method(req=request, **action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 252, in index
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi
(period_start, period_stop, detailed) = self._get_datetime_range(req)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 234, in _get_datetime_range
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi period_start
= self._parse_datetime(env.get('start', [None])[0])
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 220, in _parse_datetime
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi value =
timeutils.parse_strtime(dtstr, %Y-%m-%d %H:%M:%S.%f)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/openstack/common/timeutils.py, line 65,
in parse_strtime
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi return
datetime.datetime.strptime(timestr, fmt)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi TypeError:
strptime() argument 1 must be string, not None
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi
2014-03-20 11:28:04.226 49351 INFO nova.osapi_compute.wsgi.server
[req-09d455d6-c963-4729-b1b6-082bd04cfe8b 0 b38c2504810f437883a5b57a8b13fe7f]
9.41.223.193,127.0.0.1 GET
/v2/b38c2504810f437883a5b57a8b13fe7f/os-simple-tenant-usage HTTP/1.1 status:
400 len: 362 time: 0.0551372
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1300972/+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 1300972] [NEW] os-simple-tenant-usage is returning with the response code 400
Public bug reported:
REST os-simple-tenant-usage is returning with a response code 400
from api.log:
2014-03-20 11:27:58.044 49351 INFO nova.osapi_compute.wsgi.server
[req-b653843a-de1c-4267-af33-7f7a9c5fa99d 0 b38c2504810f437883a5b57a8b13fe7f]
9.41.223.193,127.0.0.1 GET
/v2/b38c2504810f437883a5b57a8b13fe7f/os-simpletenant-usage HTTP/1.1 status:
404 len: 302 time: 0.6078889
2014-03-20 11:28:04.221 49351 ERROR nova.api.openstack.wsgi
[req-09d455d6-c963-4729-b1b6-082bd04cfe8b 0 b38c2504810f437883a5b57a8b13fe7f]
NV-46FDF46 Exception handling resource: strptime() argument 1 must be string,
not None
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi Traceback (most
recent call last):
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 991, in
_process_stack
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi action_result =
self.dispatch(meth, request, action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 1078, in
dispatch
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi return
method(req=request, **action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 252, in index
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi (period_start,
period_stop, detailed) = self._get_datetime_range(req)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 234, in _get_datetime_range
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi period_start =
self._parse_datetime(env.get('start', [None])[0])
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 220, in _parse_datetime
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi value =
timeutils.parse_strtime(dtstr, %Y-%m-%d %H:%M:%S.%f)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/openstack/common/timeutils.py, line 65,
in parse_strtime
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi return
datetime.datetime.strptime(timestr, fmt)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi TypeError:
strptime() argument 1 must be string, not None
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi
2014-03-20 11:28:04.226 49351 INFO nova.osapi_compute.wsgi.server
[req-09d455d6-c963-4729-b1b6-082bd04cfe8b 0 b38c2504810f437883a5b57a8b13fe7f]
9.41.223.193,127.0.0.1 GET
/v2/b38c2504810f437883a5b57a8b13fe7f/os-simple-tenant-usage HTTP/1.1 status:
400 len: 362 time: 0.0551372
** 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/1300972
Title:
os-simple-tenant-usage is returning with the response code 400
Status in OpenStack Compute (Nova):
New
Bug description:
REST os-simple-tenant-usage is returning with a response code 400
from api.log:
2014-03-20 11:27:58.044 49351 INFO nova.osapi_compute.wsgi.server
[req-b653843a-de1c-4267-af33-7f7a9c5fa99d 0 b38c2504810f437883a5b57a8b13fe7f]
9.41.223.193,127.0.0.1 GET
/v2/b38c2504810f437883a5b57a8b13fe7f/os-simpletenant-usage HTTP/1.1 status:
404 len: 302 time: 0.6078889
2014-03-20 11:28:04.221 49351 ERROR nova.api.openstack.wsgi
[req-09d455d6-c963-4729-b1b6-082bd04cfe8b 0 b38c2504810f437883a5b57a8b13fe7f]
NV-46FDF46 Exception handling resource: strptime() argument 1 must be string,
not None
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi Traceback (most
recent call last):
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 991, in
_process_stack
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi action_result
= self.dispatch(meth, request, action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py, line 1078, in
dispatch
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi return
method(req=request, **action_args)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
/usr/lib/python2.6/site-packages/nova/api/openstack/compute/contrib/simple_tenant_usage.py,
line 252, in index
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi
(period_start, period_stop, detailed) = self._get_datetime_range(req)
2014-03-20 11:28:04.221 49351 TRACE nova.api.openstack.wsgi File
[Yahoo-eng-team] [Bug 1300975] [NEW] API set_flavor_extra_spec_with_all_invalid gives response 500 instead of 404
Public bug reported:
POST v2/{tenant_id}/flavors/{flavor_id}/os-extra_specs gives response
500 instead of 404.
With Post_Body : {extra_specs: ksr}, the actual result is
{computeFault: {message: The server has either erred or is incapable of
performing the requested operation., code: 500}}
when the expected result should be a 404.
Extra specs is suppose to be a list of keys. If I input with
{extra_specs: {ksr: ksr}}, I would get 404. However, there should
be a check to make sure the extra_specs value was a set and raised a 4xx
HTTP error when it wasn't, rather than hitting an unexpected condition
and raising 5xx
** 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/1300975
Title:
API set_flavor_extra_spec_with_all_invalid gives response 500 instead
of 404
Status in OpenStack Compute (Nova):
New
Bug description:
POST v2/{tenant_id}/flavors/{flavor_id}/os-extra_specs gives
response 500 instead of 404.
With Post_Body : {extra_specs: ksr}, the actual result is
{computeFault: {message: The server has either erred or is incapable of
performing the requested operation., code: 500}}
when the expected result should be a 404.
Extra specs is suppose to be a list of keys. If I input with
{extra_specs: {ksr: ksr}}, I would get 404. However, there
should be a check to make sure the extra_specs value was a set and
raised a 4xx HTTP error when it wasn't, rather than hitting an
unexpected condition and raising 5xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1300975/+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
