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

Data loss when running on newly pulled version of the evergreen image

    XMLWordPrintable

    Details

    • Sprint:
      Evergreen - Milestone 1
    • Similar Issues:

      Description

      Issue

      Reproducer:

      • run Evergreen using the current docs, mounting /evergreen/jenkins/home for data
      • stop the container
      • run a new one
      • builds are lost, registration is redone

      Expected behavior

      • Builds should not be lost
      • The instance should be registering anew like it's a first startup

      Tentative cause

      This comes from mounting /evergreen/jenkins/home instead of /evergreen. Builds are under /evergreen/jenkins/var, keys (including uuid.json) are under /evergreen/keys.

      Thanks to Jesse Glick for seeing this first.

        Attachments

          Issue Links

            Activity

            Hide
            batmat Baptiste Mathus added a comment -

            OK, better.

            Running from: /evergreen/jenkins/home/jenkins.war
            [INFO][2018-08-29 08:01:38] Logging initialized @1381ms to org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log initialized)
            [INFO][2018-08-29 08:01:39] Beginning extraction from war file (from winstone.Logger logInternal)
            2018-08-29 08:01:39,108 INFO success: evergreen-client entered RUNNING state, process has stayed up for > than 2 seconds (startsecs)
            [WARNING][2018-08-29 08:01:39] Empty contextPath (from org.eclipse.jetty.server.handler.ContextHandler setContextPath)
            [INFO][2018-08-29 08:01:39] jetty-9.4.z-SNAPSHOT; built: 2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm 1.8.0_171-b11 (from org.eclipse.jetty.server.Server doStart)
            info: Starting the evergreen-client..
            info: Configuring the client to use the endpoint https://evergreen.jenkins.io/
            info: Configuring the client for socket.io off https://evergreen.jenkins.io/
            info: Registering listener for event: `update created`
            info: Registering listener for event: `status ping`
            info: Checking registration status..
            info: We have keys and a UUID already
            
            Show
            batmat Baptiste Mathus added a comment - OK, better. Running from: /evergreen/jenkins/home/jenkins.war [INFO][2018-08-29 08:01:38] Logging initialized @1381ms to org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log initialized) [INFO][2018-08-29 08:01:39] Beginning extraction from war file (from winstone.Logger logInternal) 2018-08-29 08:01:39,108 INFO success: evergreen-client entered RUNNING state, process has stayed up for > than 2 seconds (startsecs) [WARNING][2018-08-29 08:01:39] Empty contextPath (from org.eclipse.jetty.server.handler.ContextHandler setContextPath) [INFO][2018-08-29 08:01:39] jetty-9.4.z-SNAPSHOT; built: 2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm 1.8.0_171-b11 (from org.eclipse.jetty.server.Server doStart) info: Starting the evergreen-client.. info: Configuring the client to use the endpoint https://evergreen.jenkins.io/ info: Configuring the client for socket.io off https://evergreen.jenkins.io/ info: Registering listener for event: `update created` info: Registering listener for event: `status ping` info: Checking registration status.. info: We have keys and a UUID already

              People

              • Assignee:
                batmat Baptiste Mathus
                Reporter:
                batmat Baptiste Mathus
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: