OLSConfig CR requires manual update of MCP server configuration before upgrading OpenShift Lightspeed Operator to 1.0.10

Solution Verified - Updated -

Issue

The MCP server configuration schema in the OLSConfig CR changed between OpenShift Lightspeed Operator 1.0.9 and 1.0.10. Users with MCP servers configured must manually update their OLSConfig CR before upgrading, otherwise the upgrade will fail.

My OLS operator upgrade fails with the CSV status below:

reason: RequirementsNotMet
message: Service account does not exist

When reviewing my installplan status (oc get installplan -n openshift-lightspeed -o jsonpath='{.items[*].status}' | jq), I can see the error below:

error validating existing CRs against new CRD's schema for "olsconfigs.ols.openshift.io": 
updated validation is too restrictive: [].spec.mcpServers[0].url: Required value

Environment

  • Red Hat OpenShift Container Platform 4.17+
  • OpenShift Lightspeed Operator 1.0.9 with MCP servers configured

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