CLO doesn't set default value for `.spec.outputs[].lokiStack.target.namespace` when namespace is not set in RHOCP 4
Issue
-
After configuring the clusterLogForwarder to log forward to the Red Hat Managed Loki, not logs are visible in the OpenShift Console and the collectors have a dns error to resolve the Loki IP address:
2025-01-13T10:15:01.107136Z WARN sink{component_kind="sink" component_id=output_default_lokistack_infrastructure component_type=loki}: vector::internal_events::http_client: HTTP error. error=error trying to connect: dns error: failed to lookup address information: Name or service not known error_type="request_failed" stage="processing" internal_log_rate_limit=true 2025-01-13T10:15:01.107264Z WARN sink{component_kind="sink" component_id=output_default_lokistack_infrastructure component_type=loki}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: Failed to make HTTP(S) request: error trying to connect: dns error: failed to lookup address information: Name or service not known internal_log_rate_limit=true 2025-01-13T10:15:01.166864Z WARN sink{component_kind="sink" component_id=output_default_lokistack_infrastructure component_type=loki}: vector::internal_events::http_client: Internal log [HTTP error.] is being suppressed to avoid flooding.
-
It's observed a DNS error in the collector pods resolving the Red Hat Managed Loki, but it's not matching the article "Logs are not visible in the Observe > Logs dashboard within the RHOCP Web Console due to dns error in RHOCP4" as the
.spec.outputs[].lokiStack.target.name
matches the name of the LokiStack resource.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Logging (RHOL)
- 6
- Loki
- Vector
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.