Compliance operator api-checks-pod does not start

Solution Verified - Updated -

Issue

  • The compliance operator api-checks-pod does not start. The api-checks-pod logs shows the following error:
FATAL:Error fetching resources: streaming URIs failed: failed to list MachineConfigs: The provided continue parameter is too old to display a consistent list result. You can start a new list without the continue parameter, or use the continue token in this response to retrieve the remainder of the results. Continuing with the provided token results in an inconsistent list - objects that were created, modified, or deleted between the time the first chunk was returned and now may show up in the list.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
  • Compliance Operator

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content