Cisco Bug: CSCvs98887 - CCP Tenant Cluster need to clean out old non-CCP images to prevent disk filling
Jun 15, 2020
- Cisco Container Platform
Known Affected Releases
4.0.1 4.2.1 5.0.0 5.1.0 6.0.0
Symptom: Scenario: A Tenant cluster is deployed, and is running lots of containers of varying different versions. Lots of different docker images and layers are pulled and run which consume disk space on each node. Disk space on each node is finite, currently ~30 GB. Conditions: Over time a growing number of container images will be pulled, the local disk will eventually fill up and Docker will purge images that are not currently used, including CCP system images. Docker does not know the difference between a CCP image and a Customer image. When the CCP images are purged, and a CCP container/pod is restarted and moves from one worker node to another, the CCP Pod will fail to run and there will be an outage to the user.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases