Bug #11172
Tails pythonlib is sometimes deployed with wrong permissions on jenkins.lizard
100%
Description
We’ve noticed that our jenkins jobs were sometimes not automatically updated recently.
It happened one time because the jenkins-jobs clone repository on jenkins.lizard had wrong permissions and some files in the .git directory were onwed by root rather than the jenkins user. Why it ended this way wasn’t clear, and it could as well have been a sysadmin mistake.
The second time, the cronjob responsible for the automatic upgrades was erroring out because the Tails pythonlib installation was deployed with restrictive permissions (owned by root but with 0{6,7}00), so the script wasn’t able to import it. Why it happened is not also not clear. It did after commits pythonlib:38b3c97 and puppet-tails:0425138
We’ll need to watch out on subsequent changes in the Tails pythonlib if and how this problem arises.
Subtasks
History
#1 Updated by intrigeri 2016-02-26 19:38:20
It might be that I did something stupid manually (bad boy!) in this area ~a week ago.
I can check my shell history if you want.
#2 Updated by bertagaz 2016-04-22 09:21:30
- Status changed from Confirmed to In Progress
- Assignee changed from bertagaz to intrigeri
- % Done changed from 0 to 80
- QA Check set to Ready for QA
intrigeri wrote:
> It might be that I did something stupid manually (bad boy!) in this area ~a week ago.
> I can check my shell history if you want.
Might be that, since then changes have happened in the git repo, and the pythonlib seems to have been deployed just fine. The permissions are correct from what I see. So I think we messed it up manually ourselves somehow. Feel free to close this ticket (or reject it) if you agree with my conclusions.
#3 Updated by intrigeri 2016-04-25 03:46:33
- Status changed from In Progress to Rejected
- Assignee deleted (
intrigeri) - % Done changed from 80 to 100
- QA Check changed from Ready for QA to Pass
OK, rejecting. Let’s see if it happens again.