Skip to content

[enterprise-4.12] OBSDOCS-1753 Add known issue with upgrade oom error #91512

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
Apr 2, 2025
+11 −0
Merged

[enterprise-4.12] OBSDOCS-1753 Add known issue with upgrade oom error #91512

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
11 changes: 11 additions & 0 deletions ...luster_observability_operator/cluster-observability-operator-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,17 @@ The following table provides information about which features are available depe
| 1.1 | 4.18+ | ✔ | ✔ | ✔ | ✔ | ✔
|===

[id="cluster-observability-operator-1-1-known-issues_{context}"]
== Known issues

These are the known issues in {coo-full} 1.1.0:

* `observability-operator` and `perses-operator` pods enter a `CrashLoopBackOff` state due to `OutOfMemory` errors, after upgrading from {coo-full} 1.0.
+
A workaround is provided in the knowledge base article link:https://access.redhat.com/solutions/7113898[ClusterObservability and perses operator pod in CrashLoopBackOff due to OOMKilled in RHOCP4].
+
This issue is being tracked in link:https://issues.redhat.com/browse/COO-784[*COO-784*].


[id="cluster-observability-operator-1-1-bug-fixes_{context}"]
=== Bug fixes
Expand Down