Verified on 4.10.0-0.nightly-2021-10-23-225921. Verification steps: 1. Disable Cluster Version Operator. 2. Degrade Cluster Monitoring Operator: Edit "config.yaml" key value in "cluster-monitoring-config" config map of "openshift-monitoring" namespace. Put any non-valid yaml there. 3. Wait until Cluster Monitoring Operator will be degraded: oc get co 4. Restart Insights Operator 5. Wait until a new archive will be created. 6. Download the archive. config/pod/openshift-monitoring/logs contains logs for all containers of "openshift-monitoring" namespace.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056