Description of problem:

Issue originally reported in https://issues.redhat.com/browse/ACM-11757 and marked as resolved in ACM 2.12 but we are still encountering it.

Managed Cluster goes into a degraded state on failed metrics push even when gaps in metrics data are not present. The metrics collector on the managed-cluster is succeeding sometimes and failing other times due to 409 Conflict errors and when it fails it appears to be setting the managed cluster status to Degraded which then flips on a successful push. Looking for a way to reduce the sensitivity of this flipping or resolve the metrics conflict errors. 

Version-Release number of selected component (if applicable):

2.12.0

How reproducible:

Occurs frequently on customer environment

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: