Skip to content

OLS-2239: Run vale checks on tshooting assembly #101206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 29, 2025
Merged

OLS-2239: Run vale checks on tshooting assembly #101206

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions modules/ols-502-bad-gateway-errors.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
// This module is used in the following assemblies:
// troubleshoot/ols-troubleshooting-openshift-lightspeed.adoc

:_mod-docs-content-type: CONCEPT
:_mod-docs-content-type: REFERENCE
[id="ols-502-bad-gateway-errors_{context}"]
= 502 Bad Gateway Errors in the interface

If you try to start using {ols-long} before the internal components have stabilized, 502 Bad Gateway errors can occur. While all the pods might be running, there can be other console and internal {ocp-product-title} system components that are not ready.
[role="_abstract"]
Avoid 502 Bad Gateway errors by waiting for all internal {ols-long} and {ocp-product-title} system components to stabilize after deployment.

Wait a few minutes and try using {ols-long} again.
3 changes: 2 additions & 1 deletion modules/ols-operator-missing-from-operatorhub-list.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
// This module is used in the following assemblies:
// troubleshoot/ols-troubleshooting-openshift-lightspeed.adoc

:_mod-docs-content-type: CONCEPT
:_mod-docs-content-type: REFERENCE
[id="ols-operator-missing-from-operatorhub-list_{context}"]
= Operator Missing from the Operator Hub list

[role="_abstract"]
If you are not running your {ocp-product-title} cluster on an x86 architecture, for example OpenShift Local on M1 Mac, you will not see the {ols-long} Operator in Operator Hub due to the way the Operator Hub filters architectures.

{ols-long} is only supported on x86 architecture.
3 changes: 2 additions & 1 deletion modules/ols-thinking-model-generates-delineator-prompt.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
// This module is used in the following assemblies:
// troubleshoot/ols-troubleshooting-openshift-lightspeed.adoc

:_mod-docs-content-type: CONCEPT
:_mod-docs-content-type: REFERENCE
[id="ols-thinking-model-generates-delineator-prompt_{context}"]
= Thinking model generates delineator prompt

[role="_abstract"]
In some cases, thinking or reasoning models produce output that has delineators, such as `THOUGHT` or `reasoning`, to separate the thinking process from the model output that the {ols-long} Service uses to answer your question.

The {ols-long} Service does not configure the delineator behavior or produce the delineators in the output. The delineator feature is a model configuration setting. Typically, you can disable the feature using one of the following methods:
Expand Down
4 changes: 3 additions & 1 deletion troubleshoot/ols-troubleshooting-openshift-lightspeed.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
:_content-type: ASSEMBLY
[id="ols-troubleshooting-openshift-lightspeed"]
= Troubleshooting OpenShift Lightspeed

include::_attributes/common-attributes.adoc[]
:context: ols-troubleshooting-openshift-lightspeed

toc::[]

The following topics provide information to help troubleshoot {ols-long}.
[role="_abstract"]
Find solutions and workarounds for common issues encountered when using and configuring the {ols-long} Operator and Service.

include::modules/ols-502-bad-gateway-errors.adoc[leveloffset=+1]
include::modules/ols-operator-missing-from-operatorhub-list.adoc[leveloffset=+1]
Expand Down