ERROR mistral.engine.default_executor [-] Failed to run action on create plan with invalid file format

Bug #1672853 reported by opavlenk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Uploading invalid format (jpg file) deployment plan via UI

Traceback in mistral executor.log:
2017-03-14 21:01:35.812 89784 INFO mistral.actions.std_actions [-] Running fail action.
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor [-] Failed to run action [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, action_cls='<class 'mistral.actions.action_factory.FailAction'>', attributes='{}', params='{}']
 Fail action expected exception.
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor Traceback (most recent call last):
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor File "/usr/lib/python2.7/site-packages/mistral/engine/default_executor.py", line 89, in run_action
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor result = action.run()
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor File "/usr/lib/python2.7/site-packages/mistral/actions/std_actions.py", line 95, in run
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor raise exc.ActionException('Fail action expected exception.')
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor ActionException: Fail action expected exception.
2017-03-14 21:01:35.813 89784 ERROR mistral.engine.default_executor

Api.log:
2017-03-14 21:01:34.042 89869 INFO mistral.api.controllers.v2.action_execution [-] Create action_execution [action_execution=ActionExecution [id='Unset', workflow_name='Unset', task_name='Unset', task_execution_id='Unset', state='Unset', state_info='Unset', tags='Unset', name='tripleo.plan.create_container', description='Unset', accepted='Unset', input='{'container': 'invalid-plan'}', output='Unset', created_at='Unset', updated_at='Unset', params='{'save_result': True, 'run_sync': True}']]
2017-03-14 21:01:34.368 89869 INFO mistral.api.controllers.v2.execution [-] Create execution [execution=Execution [id='Unset', workflow_name='tripleo.plan_management.v1.create_deployment_plan', workflow_id='Unset', description='Unset', params='Unset', task_execution_id='Unset', state='Unset', state_info='Unset', input='{u'container': u'invalid-plan'}', output='Unset', created_at='Unset', updated_at='Unset']]
2017-03-14 21:01:34.550 89869 INFO mistral.api.controllers.v2.environment [-] Fetch environment [name=invalid-plan]

engine.log:

2017-03-14 21:01:35.840 89715 INFO workflow_trace [-] Action 'std.fail' (23154e80-ec03-4b19-833f-fafc816a8143)(task=fail_workflow) [RUNNING -> ERROR, error = Failed to run action [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, action_cls='<class 'mistral...]
2017-03-14 21:01:35.925 89715 INFO workflow_trace [-] Task 'fail_workflow' (f14d153f-c49b-4d1d-923e-b1f589b486de) [RUNNING -> ERROR, msg=Failed to run action [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, action_cls='<class 'mistral.actions.action_factory.FailAction'>', attributes='{}', params='{}']
 Fail action expected exception.] (execution_id=5f21101c-5199-43aa-b7b5-4d3cbeb64548)
2017-03-14 21:01:36.165 89715 INFO workflow_trace [-] Workflow 'tripleo.plan_management.v1.create_deployment_plan' [RUNNING -> ERROR, msg=Failure caused by error in tasks: fail_workflow

  fail_workflow [task_ex_id=f14d153f-c49b-4d1d-923e-b1f589b486de] -> Failed to run action [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, action_cls='<class 'mistral.actions.action_factory.FailAction'>', attributes='{}', params='{}']
 Fail action expected exception.
    [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, idx=0]: Failed to run action [action_ex_id=23154e80-ec03-4b19-833f-fafc816a8143, action_cls='<class 'mistral.actions.action_factory.FailAction'>', attributes='{}', params='{}']
 Fail action expected exception.
] (execution_id=5f21101c-5199-43aa-b7b5-4d3cbeb64548)

no error on UI was shown.

swift container for the plan was created empty:
$ swift list
invalid-plan
overcloud
test
$ swift stat invalid-plan
               Account: AUTH_afdeb892f41a457f8b635569054ba087
             Container: invalid-plan
               Objects: 0
                 Bytes: 0
              Read ACL:
             Write ACL:
               Sync To:
              Sync Key:
    Meta Usage-Tripleo: plan
         Accept-Ranges: bytes
      X-Storage-Policy: Policy-0
         Last-Modified: Tue, 14 Mar 2017 19:01:35 GMT
           X-Timestamp: 1489518094.12235
            X-Trans-Id: tx24754696686d4bd4a89a8-0058c84218
          Content-Type: text/plain; charset=utf-8
X-Openstack-Request-Id: tx24754696686d4bd4a89a8-0058c84218

Tags: ui
Julie Pichon (jpichon)
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
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.