Concourse v5.5.4 Release Notes

Release Date: 2019-10-24 // over 4 years ago
  • ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ‘ท Concourse now garbage-collects worker containers and volumes that are not tracked in the database. In some niche cases, it is possible for containers and/or volumes to be created on the worker, but the database (via the web) assumes their creation had failed. If this occurs, these untracked containers can pile up on the worker and use resources. #3600 ensures that they get cleaned appropriately.

    ๐Ÿฑ ๐Ÿ”— fix

    • โž• Add 5 minute timeout for baggageclaim destroy calls. #4516

    ๐Ÿฑ ๐Ÿ”— fix

    • โž• Add 5 minute timeout for worker's garden client http calls. This is primarily to address cases such as destroy which may hang indefinitely causing GC to stop occurring. #4467

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ‘ท Transition failed state containers to destroying resulting in them being GC'ed. This ensures that if web's call to garden to create a container times out, the container is subsequently deleted from garden prior to being deleted from the db. This keeps the web's and worker's state consistent. #4562