Bug 1835268 - When clusterlogging object is created with unexpected name there is no warning
Summary: When clusterlogging object is created with unexpected name there is no warning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Brett Jones
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-13 13:57 UTC by ewolinet
Modified: 2020-07-13 17:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:38:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 523 0 None closed Bug 1835268: validate metadata name in crd 2020-11-19 09:48:07 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:38:38 UTC

Description ewolinet 2020-05-13 13:57:03 UTC
Description of problem:
When a user creates the clusterlogging object with a name other than "instance" there is no indication to the user that this is required -- nothing happens with the operator.

How reproducible:
Always

Steps to Reproduce:
1. Create a clusterlogging object with a name other than "instance"
2. Observe nothing happening


Actual results:
Nothing happens

Expected results:
The user is informed it is not a valid name or that nothing will happen.

Comment 4 Anping Li 2020-05-18 13:49:33 UTC
oc create -f logging/clusterlogging/example.yaml 
The ClusterLogging "qe" is invalid: metadata.name: Unsupported value: "qe": supported values: "instance"

Comment 5 errata-xmlrpc 2020-07-13 17:38:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409


Note You need to log in before you can comment on or make changes to this bug.