[Yahoo-eng-team] [Bug 1850694] Re: shelve doesn't handle UnexpectedTaskStateError
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/rocky
Status: New => In Progress
** Changed in: nova/rocky
Importance: Undecided => Low
** Changed in: nova/rocky
Assignee: (unassigned) => Artom Lifshitz (notartom)
** Changed in: nova/queens
Assignee: (unassigned) => Artom Lifshitz (notartom)
** Changed in: nova/stein
Assignee: (unassigned) => Artom Lifshitz (notartom)
** Changed in: nova/train
Status: New => In Progress
** Changed in: nova/train
Importance: Undecided => Low
** Changed in: nova/train
Assignee: (unassigned) => Artom Lifshitz (notartom)
** Changed in: nova/stein
Importance: Undecided => Low
** Changed in: nova/queens
Importance: Undecided => Low
** Tags added: shelve
--
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/1850694
Title:
shelve doesn't handle UnexpectedTaskStateError
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) queens series:
In Progress
Status in OpenStack Compute (nova) rocky series:
In Progress
Status in OpenStack Compute (nova) stein series:
In Progress
Status in OpenStack Compute (nova) train series:
In Progress
Bug description:
Description
===
Shelving a server expects its task state to be None. If it's not None
(for example, if attempting to shelve a server that's already being
shelved), we get a UnexpectedTaskStateError from the database layer
and return a 500 to the user. A 409 would be more appropriate.
Steps to reproduce
==
1. Send multiple shelve requests in quick succession.
Expected result
===
The initial request should be accepted, the rest should return 409.
Actual result
=
Error 500 for all requests except the first.
Environment
===
This was reported on OSP13 (Queens) originally [1].
Logs & Configs
==
2019-05-28 03:18:48.530 26 INFO nova.osapi_compute.wsgi.server
[req-1437e513-3e32-4243-8f5d-1a7e17c111df 3ff59a48497842e7a716a03a17e5bf8b
493b17f3b02b4f9ea6e71b1ae4c5ac5d - e4c6faf4dfb04f2da40c0595f1a424c7
e4c6faf4dfb04f2da40c0595f1a424c7] 10.101.4.137,10.101.4.1 "POST
/v2.1/493b17f3b02b4f9ea6e71b1ae4c5ac5d/servers/f905b880-9caa-465e-93c5-fffe9192c825/action
HTTP/1.1" status: 500 len: 622 time: 0.1237578
2019-05-28 03:18:48.529 26 INFO nova.api.openstack.wsgi
[req-1437e513-3e32-4243-8f5d-1a7e17c111df 3ff59a48497842e7a716a03a17e5bf8b
493b17f3b02b4f9ea6e71b1ae4c5ac5d - e4c6faf4dfb04f2da40c0595f1a424c7
e4c6faf4dfb04f2da40c0595f1a424c7] HTTP exception thrown: Unexpected API Error.
Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API
log if possible.
2019-05-28 03:18:48.529 26 DEBUG nova.api.openstack.wsgi
[req-1437e513-3e32-4243-8f5d-1a7e17c111df 3ff59a48497842e7a716a03a17e5bf8b
493b17f3b02b4f9ea6e71b1ae4c5ac5d - e4c6faf4dfb04f2da40c0595f1a424c7
e4c6faf4dfb04f2da40c0595f1a424c7] Returning 500 to user: Unexpected API Error.
Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API
log if possible.
__call__
/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1064
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi
[req-1437e513-3e32-4243-8f5d-1a7e17c111df 3ff59a48497842e7a716a03a17e5bf8b
493b17f3b02b4f9ea6e71b1ae4c5ac5d - e4c6faf4dfb04f2da40c0595f1a424c7
e4c6faf4dfb04f2da40c0595f1a424c7] Unexpected exception in API method:
UnexpectedTaskStateError: Conflict updating instance
f905b880-9caa-465e-93c5-fffe9192c825. Expected: {'task_state': [None]}. Actual:
{'task_state': u'shelving'}
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi Traceback (most
recent call last):
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi File
"/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 788, in
wrapped
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi return f(*args,
**kwargs)
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi File
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/shelve.py", line
43, in _shelve
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi
self.compute_api.shelve(context, instance)
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi File
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 204, in inner
2019-05-28 03:18:48.523 26 ERROR nova.api.openstack.wsgi return
function(self, context, instance, *args, **kwargs)
2019-05-28 03:18:48.5
[Yahoo-eng-team] [Bug 1847957] Re: Stage init-local fails saying NameError: global name 'name' is not defined
Since this piece of code is replaced in v19.2 and I don't have complete logs or the system to provide for further debug. Moving it to invalid state. ** Changed in: cloud-init Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1847957 Title: Stage init-local fails saying NameError: global name 'name' is not defined Status in cloud-init: Invalid Bug description: 2019-10-11 04:38:09,499 - util.py[DEBUG]: failed stage init-local Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 653, in status_wrapper ret = functor(name, args) File "/usr/lib/python2.7/site-packages/cloudinit/cmd/main.py", line 362, in main_init init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL)) File "/usr/lib/python2.7/site-packages/cloudinit/stages.py", line 671, in apply_network_config return self.distro.apply_network_config(netcfg, bring_up=bring_up) File "/usr/lib/python2.7/site-packages/cloudinit/distros/__init__.py", line 178, in apply_network_config dev_names = self._write_network_config(netconfig) File "/usr/lib/python2.7/site-packages/cloudinit/distros/opensuse.py", line 177, in _write_network_config net_apply_res = self._supported_write_network_config(netconfig) File "/usr/lib/python2.7/site-packages/cloudinit/distros/__init__.py", line 93, in _supported_write_network_config renderer.render_network_config(network_config) File "/usr/lib/python2.7/site-packages/cloudinit/net/renderer.py", line 56, in render_network_config templates=templates, target=target) File "/usr/lib/python2.7/site-packages/cloudinit/net/sysconfig.py", line 707, in render_network_state path = net.sys_dev_path(iface[name]) NameError: global name 'name' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1847957/+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
