2017-02-16 17:15:54,498 - atomic_reactor.util - ERROR - {"errorDetail":{"message":"devmapper: Thin Pool has 17890 free data blocks which is less than minimum required 17946 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior"},"error":"devmapper: Thin Pool has 17890 free data blocks which is less than minimum required 17946 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior"}
buildvm-02.stg.phx2.fedoraproject.org
https://kojipkgs.stg.fedoraproject.org//work/tasks/153/90300153/openshift-incremental.log
Assigning to @maxamillion
Metadata Update from @kevin: - Issue assigned to maxamillion
The immediate issue is resolved, I'm still trying to sort out how this happened. There's a job that's supposed to be cleaning the storage up from old builds and it just isn't at the moment. Will update when I find something.
I no longer hit this issue. Feel free to close (not sure if you want to keep this for tracking). Maybe relevant logs:
2017-02-22 10:17:19,859 - atomic_reactor.core - INFO - removing image 'd8ef41343556dde5b6a3f5bcf7496a55dba667bf4dfe742dcc8264a4ca218484' from filesystem 2017-02-22 10:17:19,859 - atomic_reactor.core - DEBUG - image_id = 'd8ef41343556dde5b6a3f5bcf7496a55dba667bf4dfe742dcc8264a4ca218484' 2017-02-22 10:17:20,162 - atomic_reactor.core - INFO - removing image 'registry.stg.fedoraproject.org/fedora:25' from filesystem 2017-02-22 10:17:20,162 - atomic_reactor.core - DEBUG - image_id = 'registry.stg.fedoraproject.org/fedora:25' 2017-02-22 10:17:20,173 - atomic_reactor.core - INFO - removing image 'fedora:25' from filesystem 2017-02-22 10:17:20,173 - atomic_reactor.core - DEBUG - image_id = 'fedora:25' 2017-02-22 10:17:20,181 - atomic_reactor.core - INFO - removing image 'candidate-registry.stg.fedoraproject.org/f25/toolchain:1' from filesystem 2017-02-22 10:17:20,181 - atomic_reactor.core - DEBUG - image_id = 'candidate-registry.stg.fedoraproject.org/f25/toolchain:1' 2017-02-22 10:17:20,183 - atomic_reactor.plugins.remove_built_image - WARNING - failed to remove image candidate-registry.stg.fedoraproject.org/f25/toolchain:1 (404: Not Found), ignoring 2017-02-22 10:17:20,184 - atomic_reactor.core - INFO - removing image 'candidate-registry.stg.fedoraproject.org/f25/toolchain:latest' from filesystem 2017-02-22 10:17:20,184 - atomic_reactor.core - DEBUG - image_id = 'candidate-registry.stg.fedoraproject.org/f25/toolchain:latest' 2017-02-22 10:17:20,185 - atomic_reactor.plugins.remove_built_image - WARNING - failed to remove image candidate-registry.stg.fedoraproject.org/f25/toolchain:latest (404: Not Found), ignoring 2017-02-22 10:17:20,185 - atomic_reactor.core - INFO - removing image 'candidate-registry.stg.fedoraproject.org/f25/toolchain:1-1.f25docker' from filesystem 2017-02-22 10:17:20,185 - atomic_reactor.core - DEBUG - image_id = 'candidate-registry.stg.fedoraproject.org/f25/toolchain:1-1.f25docker' 2017-02-22 10:17:20,187 - atomic_reactor.plugins.remove_built_image - WARNING - failed to remove image candidate-registry.stg.fedoraproject.org/f25/toolchain:1-1.f25docker (404: Not Found), ignoring 2017-02-22 10:17:20,187 - atomic_reactor.core - INFO - removing image 'sha256:0774f3d9a37e5e2b2205f0c72dc8b21950736613a68d36ecfd19e9f6bad5a18a' from filesystem 2017-02-22 10:17:20,187 - atomic_reactor.core - DEBUG - image_id = 'sha256:0774f3d9a37e5e2b2205f0c72dc8b21950736613a68d36ecfd19e9f6bad5a18a' 2017-02-22 10:17:20,674 - atomic_reactor.core - INFO - removing image 'candidate-registry.stg.fedoraproject.org/f25/toolchain:rawhide-docker-candidate-20170222101152' from filesystem 2017-02-22 10:17:20,674 - atomic_reactor.core - DEBUG - image_id = 'candidate-registry.stg.fedoraproject.org/f25/toolchain:rawhide-docker-candidate-20170222101152' 2017-02-22 10:17:20,677 - atomic_reactor.plugins.remove_built_image - WARNING - failed to remove image candidate-registry.stg.fedoraproject.org/f25/toolchain:rawhide-docker-candidate-20170222101152 (404: Not Found), ignoring
I'm assuming that first removal gets rid off of all layers and hence even removes all other alias names.
This has been resolved, changes in ansible repo. Closing.
Metadata Update from @puiterwijk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.