Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-22333

tssw jenkins agent jenkins-el7-1 running out of disk space

    Details

      Description

      The jenkins-el7-1 has dropped below the free disk space limit several times in the last few weeks. It seems plausible there is an issue with workspace cleanup and that this agent may need a larger volume.

        Attachments

          Activity

          Hide
          ttsai Te-Wei Tsai added a comment -

          Joshua Hoblitt The Jenkinsfile of ts_mt_hexRot_middleware is designed for the Jenkins instance of T&S team to work around the permission issue (uid: 1004). Therefore, it will fail on the Jenkins instance by DM team. Actually, I thought the auto-population of "LSST Telescope & Site" on DM's Jenkins instance may not be a good idea. Thanks!

          Show
          ttsai Te-Wei Tsai added a comment - Joshua Hoblitt The Jenkinsfile of ts_mt_hexRot_middleware is designed for the Jenkins instance of T&S team to work around the permission issue (uid: 1004). Therefore, it will fail on the Jenkins instance by DM team. Actually, I thought the auto-population of "LSST Telescope & Site" on DM's Jenkins instance may not be a good idea. Thanks!
          Hide
          tribeiro Tiago Ribeiro added a comment -

          I removed all the triggers from that build. It should not run anymore. 

          Show
          tribeiro Tiago Ribeiro added a comment - I removed all the triggers from that build. It should not run anymore. 
          Hide
          jhoblitt Joshua Hoblitt added a comment -

          Te-Wei Tsai Are you saying that the job https://ts-ci.lsst.codes/blue/organizations/jenkins/lsst-ts%2Fts_mt_hexRot_middleware/branches/ should not exist? It looks like there are Jenkinsfiles at the tips of branches.

          Show
          jhoblitt Joshua Hoblitt added a comment - Te-Wei Tsai Are you saying that the job https://ts-ci.lsst.codes/blue/organizations/jenkins/lsst-ts%2Fts_mt_hexRot_middleware/branches/ should not exist? It looks like there are Jenkinsfiles at the tips of branches.
          Hide
          ttsai Te-Wei Tsai added a comment -

          To be clear, the TSSW jenkins instance hold by DM team uses the root authority for the docker image. The TSSW jenkins instance hold by T&S team uses the jenkinsuser (uid: 1004, not the root) for the docker image. This is why you will see the error here.

          Show
          ttsai Te-Wei Tsai added a comment - To be clear, the TSSW jenkins instance hold by DM team uses the root authority for the docker image. The TSSW jenkins instance hold by T&S team uses the jenkinsuser (uid: 1004, not the root) for the docker image. This is why you will see the error here.
          Hide
          ttsai Te-Wei Tsai added a comment - - edited

          Joshua Hoblitt I am the owner of ts_mt_hexRot_middleware repo. That repo was automatically on TSSW instance by the auto-population of "LSST Telescope & Site". Please help to remove that one.

          Thanks!

          BTW, the test of ts_mt_hexRot_middleware repo is on the Jenkins instance by T&S team now.

          Show
          ttsai Te-Wei Tsai added a comment - - edited Joshua Hoblitt I am the owner of ts_mt_hexRot_middleware repo. That repo was automatically on TSSW instance by the auto-population of "LSST Telescope & Site". Please help to remove that one. Thanks! BTW, the test of ts_mt_hexRot_middleware repo is on the Jenkins instance by T&S team now.

            People

            • Assignee:
              Unassigned
              Reporter:
              jhoblitt Joshua Hoblitt
              Watchers:
              Andy Clements, Joshua Hoblitt, Te-Wei Tsai, Tiago Ribeiro
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel