The IOP-enabled Satellite server is not cleaning up previously collected data from the IOP containers. As a result, disk usage grows continuously over time, especially when the Satellite manages a large number of hosts.

Observed behavior:

• If the number of hosts registered to the Satellite server exceeds the capacity of iop-core-ingress, the system keeps accumulating container data without cleanup.

• In an environment with ~800 hosts, disk usage grew to ~9 GB within 4 weeks under /var/lib/containers/storage/....

Each generated tarball contains two sets of data:

1. Insights-client collected data

1. Inventory data

Example tarball contents:

# tar tvf /var/lib/containers/storage/overlay/fdf03351fc447f7eb66bacde1a97a74b4d6294a13b92b26469d28a77c584e21d/merged/var/tmp/a4e79c871fdcee726c2901cfd8822892.tar.gz 
drwx------ foreman/foreman   0 2025-12-09 17:24 ./
-rw-r--r-- foreman/foreman 305 2025-12-09 17:24 ./metadata.json
-rw-r--r-- foreman/foreman 43762 2025-12-09 17:24 ./e3c50d5c-1b73-4147-a80e-ed22510a3601.json

Impact

• Continuous disk space increase on Satellite servers

• Risk of full disk leading to service disruption

• Manual intervention is currently required to clean up the container storage

Expected Behavior

IOP containers should automatically clean up outdated/processed data, or a retention/cleanup mechanism should be put in place.

Steps to Reproduce

1. Enable IOP on Satellite

1. Register a large number of hosts (hundreds)

1. Allow IOP data collection to run for several weeks

1. Observe disk usage in /var/lib/containers/storage/

1. Notice old tar files are not removed