Page MenuHomePhabricator
Create Task
Maniphest T63144

jenkis-deploy user on labs should have its home in /mnt
Closed, ResolvedPublic
Actions

Description

The Jenkins slaves on labs projects (deployment-prep and integration projects) use the user jenkins-deploy to setup the instance as a Jenkins slave. The LDAP entry points the home of that user to /home/jenkins-deploy which is a GlusterFS partition for the integration project.

The slave jobs are run under /mnt/jenkins-workspace since we don't want the jobs workspaces to be on a shareable disks to avoid obvious race conditions.

To avoid relying on GlusterFS, we should get jenkins-deploy home to point to /mnt/jenkins-deploy . That needs some puppet change to create the home directory then the LDAP entry can be altered.

Version: wmf-deployment
Severity: normal

Details

Reference
bz61144

Event Timeline

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:56 AM
• bzimport added a project: Continuous-Integration-Infrastructure.
• bzimport set Reference to bz61144.
hashar created this task.Feb 10 2014, 3:21 PM
gerritbot added a comment.Feb 10 2014, 3:29 PM

Change 112458 had a related patch set uploaded by Hashar:
contint: move jenkins-deploy user home to /dev/vdb

https://gerrit.wikimedia.org/r/112458

gerritbot added a comment.Feb 10 2014, 3:58 PM

Change 112458 merged by ArielGlenn:
contint: move jenkins-deploy user home to /dev/vdb

https://gerrit.wikimedia.org/r/112458

hashar added a comment.Feb 10 2014, 4:44 PM

All instances now have a /mnt/home/jenkins-deploy homedir which belong to jenkins-deploy.

The next step is to have the jenkins-deploy user home dir to be updated in LDAP to point to /mnt/home/jenkins-deploy

Currently:

  1. ldaplist -l passwd jenkins-deploy|grep homeDirectory

homeDirectory: /home/jenkins-deploy

Then reconnect all Jenkins slaves and make sure jobs can still be triggered.

hashar added a comment.Feb 10 2014, 4:56 PM

Apergos reviewed the puppet changes and Andrew updated the homeDirectory.

I have rebooted most slave instance (beside deployment-parsoid2 and deployment-bastion).

integration-slave01 Jenkins slave has reconnected and the npm command now use /mnt/home/jenkins-deploy for its cache thus solving the issue I had.

Still have to double check the other jobs/slaves.

hashar added a comment.Feb 10 2014, 5:02 PM

I have disconnected and reconnected all slaves. Bye bye GlusterFS.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits