Clean up noisy 'failed-to-transition' log during volume GC #1780
Description
Bug Report
Nov 03 20:09:38 somewhere.io docker[3779]: {"timestamp":"1509739778.442883492","source":"atc","message":"atc.volume-collector.run.orphaned-volumes.mark-created-as-destroying.failed-to-transition","log_level":2,"data":{"error":"volume cannot be destroyed as children are present","session":"26.14766.1.3","volume":"480df3bf-97f8-4b3b-6b15-464eea436eb5","worker":"primaryworker"}}
The work dir is btrfs based.
The following can also be handy:
- Concourse version: 3.6.0
- Deployment type (BOSH/Docker/binary): binary
- Infrastructure/IaaS:
- Browser (if applicable):
- Did this used to work? yes