periodic fs050 upgrades: Unable to delete the specified workbook(s)

Bug #1786533 reported by Rafael Folco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Jose Luis Franco

Bug Description

http://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-infra/tripleo-ci/master/legacy-periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset050-upgrades-master/6142fb5/logs/undercloud/home/zuul/undercloud_upgrade.log.txt.gz

2018-08-10 07:28:42 | "+ openstack workbook delete tripleo.scale.v1",
2018-08-10 07:28:42 | "Unable to delete the specified workbook(s).",

<more info to be added after some investigation>

Changed in tripleo:
assignee: nobody → Jose Luis Franco (jfrancoa)
wes hayutin (weshayutin)
tags: added: promotion-blocker
Revision history for this message
Jose Luis Franco (jfrancoa) wrote :
Download full text (5.7 KiB)

The following error is found in the mistral logs related to the get_deployment_failures task:

2018-08-14 01:35:39.076 7 INFO mistral.engine.engine_server [req-54094e03-e859-43b3-b6da-cd865d613290 f80f44084ac74f3f92a738b308880500 252292bd925748d9974d6f444d5a5f03 - default default] Received RPC request 'start_workflow'[workflow_identifier=tripleo.deployment.v1.get_deployment_failures, workflow_input={plan: overcloud}, description=, params={}]
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server [req-54094e03-e859-43b3-b6da-cd865d613290 f80f44084ac74f3f92a738b308880500 252292bd925748d9974d6f444d5a5f03 - default default] Exception during message handling: DBEntityNotFoundError: Workflow not found [workflow_identifier=tripleo.deployment.v1.get_deployment_failures, namespace=]
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 265, in dispatch
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/mistral/engine/engine_server.py", line 110, in start_workflow
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server **params
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/mistral/db/utils.py", line 88, in decorate
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server return retry.call(_with_auth_context, auth_ctx, func, *args, **kw)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", line 330, in call
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server start_time=start_time)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", line 279, in iter
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server return fut.result()
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/concurrent/futures/_base.py", line 422, in result
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server return self.__get_result()
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", line 333, in call
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server result = fn(*args, **kwargs)
2018-08-14 01:35:39.090 7 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/mistral/db/...

Read more...

Revision history for this message
Rafael Folco (rafaelfolco) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.