Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53579

Asynchronous cleanup not removing renamed workspace directories on slaves

    XMLWordPrintable

Details

    • Improvement
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • ws-cleanup-plugin
    • None
    • Jenkins ver. 2.121.3
      ws-cleanup 0.34

    Description

      We noticed the workspaces on our slaves getting renamed to the form of ${WORKSPACE}ws-cleanup${TIMESTAMP}. (ie, job1 would become job1_ws-cleanup_1411197183394). The expected behavior is that these were temporary to support asynchronous processing and would be deleted. However, these directories never get removed from the slave. Over time, the slave hard drives filled up resulting in build failures.

      Attachments

        Issue Links

          Activity

            jbochenski Jakub Bochenski added a comment - - edited

            > I would expect Jenkins to establish a permission mapping between its euid and container's root.

            Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it

            EDIT: my argument is same as https://issues.jenkins-ci.org/browse/JENKINS-53579?focusedCommentId=374472&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-374472

            jbochenski Jakub Bochenski added a comment - - edited > I would expect Jenkins to establish a permission mapping between its euid and container's root. Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it EDIT: my argument is same as https://issues.jenkins-ci.org/browse/JENKINS-53579?focusedCommentId=374472&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-374472

            For some reason, here the problems appears on jobs that are using Docker images running root user inside. I would expect Jenkins to establish a permission mapping between its euid and container's root. What is even stranger is that not all files created in the relevant steps are surviving.

            gdartiguelongue Gilles Dartiguelongue added a comment - For some reason, here the problems appears on jobs that are using Docker images running root user inside. I would expect Jenkins to establish a permission mapping between its euid and container's root. What is even stranger is that not all files created in the relevant steps are surviving.
            mookayla Michaela Ervin added a comment - - edited

            Understandable!

             

            I added the following to the end of my build script to test changing the perms.

             

            workspace = getcwd()
            LOGGER.info('Workspace directory is: {}'.format(workspace)) 
            system('cd "{}" && sudo chown -R jenkins:jenkins *'.format(workspace))
            

            It seems to have worked except a file still existed that I didn't realize was getting created.  Running again to see if it works.

            mookayla Michaela Ervin added a comment - - edited Understandable!   I added the following to the end of my build script to test changing the perms.   workspace = getcwd() LOGGER.info( 'Workspace directory is: {}' .format(workspace)) system( 'cd "{}" && sudo chown -R jenkins:jenkins *' .format(workspace)) It seems to have worked except a file still existed that I didn't realize was getting created.  Running again to see if it works.
            markewaite Mark Waite added a comment -

            I hope for security purposes that the Jenkins agent process cannot become the root user as a general pattern. I don't think the plugin has any way to ask the operating system to promote the cleanup operation to root permission. Even if it did, I don't think it would be wise to make such a request, since agents that can easily become the root user can then also be used to harm the operating system that is hosting the agent

            markewaite Mark Waite added a comment - I hope for security purposes that the Jenkins agent process cannot become the root user as a general pattern. I don't think the plugin has any way to ask the operating system to promote the cleanup operation to root permission. Even if it did, I don't think it would be wise to make such a request, since agents that can easily become the root user can then also be used to harm the operating system that is hosting the agent
            mookayla Michaela Ervin added a comment - - edited

            Why are the ${WORKSPACE}ws-cleanup${TIMESTAMP} directories owned by someone else?  AFAIK jenkins creates them so it should delete them.

             

            Edit: I see, our scripts run some commands with sudo and thus stuff is owned by root.

            Maybe I just need to run `chown -R jenkins:jenkins` on the directory at the end of my script.

             

            What about an option to "try" to run the cleanup as root?

            mookayla Michaela Ervin added a comment - - edited Why are the ${WORKSPACE} ws-cleanup ${TIMESTAMP} directories owned by someone else?  AFAIK jenkins creates them so it should delete them.   Edit: I see, our scripts run some commands with sudo and thus stuff is owned by root. Maybe I just need to run `chown -R jenkins:jenkins` on the directory at the end of my script.   What about an option to "try" to run the cleanup as root?

            People

              olivergondza Oliver Gondža
              jbochenski Jakub Bochenski
              Votes:
              15 Vote for this issue
              Watchers:
              26 Start watching this issue

              Dates

                Created:
                Updated: