Set RHOSO Lightspeed specific system prompt

[lpiwowar]

When RHOSO Lightspeed operator deployes OLS operator it uses the default OLS system prompt which leads to more OpenShift focused responses from RHOSO Lightspeed.

This commit utilizies the querySystemPrompt parameter in OLSConfig to configure OLS with RHOSO specific system prompt.

Depends-On: openshift/lightspeed-operator#1211

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[lpiwowar]

/test all

[lpiwowar]

Right now this will have no effect because the version of OLS operator that is currently published does not contain this change [1] yet. The querySystemPrompt parameter is present in the OLSConfig CR, but does not work for the non-lcore backend. Once [1] is released as part of the next OLS operator version, the change our operator makes should take effect.

[1] github.com/openshift/lightspeed-operator/pull/1211

[umago]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lpiwowar, umago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [lpiwowar,umago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[umago]

/lgtm cancel

[umago]

I think @Akrog should also take a look at it, but it l.g.t.m :-)

[lpiwowar]

The CI is failing with:

namespace/openshift-lightspeed created
time="2026-01-20T16:17:16Z" level=info msg="Creating a File-Based Catalog of the bundle \"registry.build05.ci.openshift.org/ci-op-gz31yd25/pipeline@sha256:f8a19adf7ad16566c4c5d745c9470aa8d6d2dc817b312aabc7c07d6a5290544b\""
time="2026-01-20T16:17:16Z" level=info msg="Generated a valid File-Based Catalog"
time="2026-01-20T16:18:15Z" level=info msg="Created registry pod: 8a19adf7ad16566c4c5d745c9470aa8d6d2dc817b312aabc7c07d6a5290544b"
time="2026-01-20T16:18:15Z" level=info msg="Created CatalogSource: openstack-lightspeed-operator-catalog"
time="2026-01-20T16:18:16Z" level=info msg="OperatorGroup \"operator-sdk-og\" created"
time="2026-01-20T16:18:16Z" level=info msg="Created Subscription: openstack-lightspeed-operator-v0-0-1-sub"
time="2026-01-20T16:18:55Z" level=fatal msg="Failed to run bundle: install plan is not available for the subscription openstack-lightspeed-operator-v0-0-1-sub: Get \"https://api.oko-04.oooci.ccitredhat.com:6443/apis/operators.coreos.com/v1alpha1/namespaces/openshift-lightspeed/subscriptions/openstack-lightspeed-operator-v0-0-1-sub\": context deadline exceeded\n"
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2026-01-20T16:18:55Z"}
error: failed to execute wrapped command: exit status 1

It looks like it is not related to the PR. Let's retest and see.

[lpiwowar]

/test openstack-lightspeed-kuttl-4-18

[umago]

@Akrog, I'm good with the proposed system prompt. Do u want to take a look as well ? I believe the instructions should be similar to what you have tested before

[Akrog]

nit: Maybe we should mention that OpenShift uses CoreOS as the operating system and EDPM nodes run RHEL.

[umago]

Latest changes looks good!

[umago]

@lpiwowar do u want to squash the commits or we do it at merge time ?

[lpiwowar]

@umago I think keeping the commits is ok as they are not "ugly" IMO and explain the development of the original system prompt. I would keep them unless you think otherwise:)

[umago]

@lpiwowar ok then! Sounds good

[umago]

/lgtm