-
Bug
-
Resolution: Done-Errata
-
Normal
-
Logging 5.8.z
-
False
-
None
-
False
-
NEW
-
NEW
-
-
Bug Fix
-
Medium
-
-
-
-
Log Collection - Sprint 249, Log Collection - Sprint 250, Log Collection - Sprint 251, Log Collection - Sprint 252
Description of problem:
When a CustomResource is created in OpenShift-logging namespace using a different name from "instance", the following message appears in status-> conditions section:
message: 'validation failed: Only spec.collection is allowed when using multiple instances of ClusterLogForwarder: openshift-logging/<CR name>'
According to the official documentation that for legacy implementation:
In legacy implementations, you can only use one log forwarder in your cluster. The ClusterLogForwarder resource in this mode must be named instance, and must be created in the openshift-logging namespace. The ClusterLogForwarder resource also requires a corresponding ClusterLogging resource named instance in the openshift-logging namespace.
And for Multi Log Forwarder feature:
You cannot create a ClusterLogForwarder resource named instance in the openshift-logging namespace, because this is reserved for a log forwarder that supports the legacy workflow using the Fluentd collector. You cannot create a ClusterLogForwarder resource named collector in the openshift-logging namespace, because this is reserved for the collector.
So, with these previous sentences, we can confirm that a different name of "instance" cannot be used for creating a Custom Resource in "openshift logging"namespace".
Therefore the validation error shouldn´t be:
message: 'validation failed: Only spec.collection is allowed when using multiple instances of ClusterLogForwarder: openshift-logging/<CR name>'
It should be something like: "Only instance name can be defined for a CR when using legacy mode or when deploys a CR in "openshift-logging" .
Version-Release number of selected component (if applicable):
RHOL 5.8
Actual results:
Verification message does not correspond to the real error.
Expected results:
Verification message corresponds to the real error.
- links to
-
RHSA-2024:130615 Logging for Red Hat OpenShift - 5.9.1
- mentioned on