-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
-
-
None
Version of components:
OCP version
4.16.0-0.nightly-2024-11-05-003735
Operator bundle: quay.io/rhobs/observability-operator-bundle:0.4.3-241105092032
Description of issue:
When Tracing UI plugin instance is created. The distributed-tracing-* pod shows the following errors and the Tracing UI is not available in the OCP web console.
% oc logs distributed-tracing-745f655d84-2jk6b time="2024-11-05T13:08:37Z" level=info msg="enabled features: []\n" module=main time="2024-11-05T13:08:37Z" level=error msg="cannot read base manifest file" error="open web/dist/plugin-manifest.json: no such file or directory" module=manifest time="2024-11-05T13:08:37Z" level=info msg="listening on https://:9443" module=server I1105 13:08:37.620932 1 tlsconfig.go:240] "Starting DynamicServingCertificateController" 10.128.0.109 - - [05/Nov/2024:13:08:54 +0000] "GET /plugin-manifest.json HTTP/1.1" 500 62 10.128.0.109 - - [05/Nov/2024:13:08:54 +0000] "GET /plugin-manifest.json HTTP/1.1" 500 62 10.128.0.109 - - [05/Nov/2024:13:09:10 +0000] "GET /plugin-manifest.json HTTP/1.1" 500 62 10.128.0.109 - - [05/Nov/2024:13:09:25 +0000] "GET /plugin-manifest.json HTTP/1.1" 500 62
Steps to reproduce the issue:
*Instal the latest operator bundle.
quay.io/rhobs/observability-operator-bundle:0.4.3-241105092032
*Set the -openshift.enabled flag in the CSV.
*Create the Tracing UI plugin instance and check the UI plugin pod logs.
- links to
