API reports error and does not work when recipe description changed

[henrywang]

Description of problem

API reports error and will not work when the recipe description changed..

Component (web, API, etc)

API

Steps to Reproduce

1. Navigate to the Recipe page.
2. Click Details tab.
3. Click "Edit" button on the Description row.
4. Type the changed description.
5. Click "Save" button.

Actual results

The API reports error info as below:
POST /api/v0/recipes/new application/json: => Matched: POST /api/v0/recipes/new application/json Apr 24 10:25:40.033 INFO /recipes/new/ (JSON), recipe.name: abc Apr 24 10:25:40.033 DEBG Branch master's id is 6bcbc71aa9453d557000f029f4c488091aea4216 thread '<unnamed>' panicked at 'called Result::unwrap()on anErr value: Error { code: -1, klass: 2, message: "failed to rename lockfile to \'/home/xiaofwan/tmp/recipes/git/objects/fa/f372512676500a601c0815b2d8a40beea4c67b\': Permission denied" }', /checkout/src/libcore/result.rs:859 note: Run with 'RUST_BACKTRACE=1' for a backtrace.

HTTP POST JSON content (description was "abc recipe" before changed):

And after run with RUST_BACKTRACE=1, got backtrace which can be found from https://paste.fedoraproject.org/paste/aYUGyZnswUPkO5Xhg1BxYl5M1UNdIGYhyRLivL9gydE=

Expected results

The changed description should be saved and not any error on both API and Web sides.

[bcl]

I am unable to reproduce this, either with a new bdcs test changing the description, or with the UI. The error would seem to indicate a file permission problem in your recipe repo, can you check it to see if they look reasonable?
It's possible that there could be SELinux problems if you are running from a container and it didn't relabel them properly.

I can't see any way for a description change to cause this kind of failure since it isn't handled any differently than the other fields of the recipe struct.