StackStorm / StackStorm/st2

Saving a workflow via st2flow to a pack with no write permissions throws a 500

Open
#3,220 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug component:st2web enhancement status:under discussion
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

IOError: [Errno 13] Permission denied: u'/opt/stackstorm/packs/examples/actions/workflows/mistral-basic.yaml'
2017-02-15 14:04:39,657 81402288 INFO hooks [-] 6ef334bf-88f7-4ee0-9e3e-fbc5c3d7ec6f - PUT /v1/actions/58a45ec155fc8c0fbbf1e7eb result={
    "faultstring": "Internal Server Error"
} (result='{\n    "faultstring": "Internal Server Error"\n}',request_id='6ef334bf-88f7-4ee0-9e3e-fbc5c3d7ec6f',status_code='500 Internal Server Error',remote_addr='127.0.0.1',path='/v1/actions/58a45ec155fc8c0fbbf1e7eb',method='PUT')

Steps to repro

  1. Install examples pack and register actions from it via st2ctl reload --register-all

  2. Click EDIT and open a mistral workflow in FLOW

  3. Click SAVE button

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by saving the example mistral workflow through st2flow with the pack directory unwritable, then inspect the PUT /v1/actions/{id} handling for the reported permission error. Done should include a defined, non-500 response for this permission-denied case and coverage for the reproduction, but the issue does not name a test file or implementation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.