Merge lp:~javier.collado/utah/bug1039540 into lp:utah
Status: | Rejected |
---|---|
Rejected by: | Javier Collado |
Proposed branch: | lp:~javier.collado/utah/bug1039540 |
Merge into: | lp:utah |
Diff against target: |
12 lines (+1/-1) 1 file modified
utah/run.py (+1/-1) |
To merge this branch: | bzr merge lp:~javier.collado/utah/bug1039540 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
UTAH Dev | Pending | ||
Review via email: mp+121528@code.launchpad.net |
Description of the change
This one line change should fix the permissions problems when running test cases on a machine provisioned from scratch.
According to my experience, what works fine for me is:
- Avoid running the utah client as root
- Use always `utah` user to run test cases
I think the client has been executed as root for some time, so there must be some other thing that has changed. Anyway, I believe that running the test cases as `utah` user should be the default to avoid permissions problems. In particular, what I've seen is that when the client is executed as `root` and, after that, as `utah` there are problems to remove test files that were left by the previous run.
Unmerged revisions
- 661. By Javier Collado
-
Updated utah command to be executed as regular user
If I run test cases as the utah user, can they reboot if necessary? It seems like that wasn't implemented yet a while ago, but if it is now, I can move all my stuff to the user instead of root.