-
Bug
-
Resolution: Unresolved
-
Undefined
-
1.1.0
-
None
-
None
-
True
-
-
False
-
-
-
None
perses pod can not be started on arm64.
oc logs perses-0
time="2025-03-17T08:12:17Z" level=warning msg="encryption_key is not provided and therefore it will use a default one. For production instance you should provide the key."
time="2025-03-17T08:12:17Z" level=fatal msg="unable to initialize the service manager: open schemas/panels: no such file or directory"
Image:
quay.io/redhat-user-workloads/cluster-observabilit-tenant/cluster-observability-operator/perses-0-50-rhel9@sha256:693518152abaef50c8bfe105189b95682cb0ada05cc3c79e4e8d5b5150a6e5f4
Version:
Labels: architecture=aarch64
build-date=2025-03-15T00:03:11
oc logs perses-0
time="2025-03-17T08:12:17Z" level=warning msg="encryption_key is not provided and therefore it will use a default one. For production instance you should provide the key."
time="2025-03-17T08:12:17Z" level=fatal msg="unable to initialize the service manager: open schemas/panels: no such file or directory"
- is incorporated by
-
COO-713 Perses dashboards are not listed in the console
-
- On QA
-
- links to