Bug 1414691
| Summary: | Name validation is not consistent in cli with from web console | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yanping Zhang <yanpzhan> | |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.5.0 | CC: | aos-bugs, jforrest, jokerman, mmccomas, spadgett, tdawson | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
When creating some resources in the web console, the validation of the name field was more strict than the command-line interface. Validation has been relaxed for the following forms in the web console to match the command line:
* Add Autoscaler
* Add Storage
* Create Config Map
* Create Route
* Create Secret
Periods are now allowed in the names, and the max length has been increased to 253 characters.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1414956 (view as bug list) | Environment: | ||
| Last Closed: | 2017-04-12 19:09:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
Routes shouldn't be allowing the '.', cloned a bug to Routing component to resolve that issue https://bugzilla.redhat.com/show_bug.cgi?id=1414956 The remaining issues are with the console being too strict in its validation. We're updating name validation (pattern and maxlength) on the following forms: * Add Autoscaler * Add Storage * Create Config Map * Create Route * Create Secret Suggest regression testing these forms. https://github.com/openshift/origin-web-console/pull/1155 Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/96fcca36402973bc933a5a78da29673cb16a957b Bug 1414691 - Fix name validation for several resources This has been merged into ocp and is in OCP v3.5.0.10 or newer. Tested on OCP v3.5.0.14 : Create "Autoscaler","Storage","Config Map","Route" and "Secret" from web console, when name is invalid, there is error info showing: "Name must consist of lower-case letters, numbers, periods, and hyphens. It must start and end with a letter or a number. " And name containing ".","-" such as "name.test-one" is valid, and could be created successfully both from cli and web. The bug has been fixed, so move it to Verified. 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-2017:0884 |
Description of problem: When create pvc from storage page on web console, if input pvc name containing "." such as "pvc.test", it will prompt error info:"Claim names may only contain lower-case letters, numbers, and dashes. They may not start or end with a dash. Max length of 253.", but pvc with name "pvc.test" can be created successfully in cli. Version-Release number of selected component (if applicable): openshift v3.5.0.6+87f6173 oc v3.5.0.6+87f6173 How reproducible: Always Steps to Reproduce: 1.Create pvc with name containing "." such as "pvc.test" from storage page on web console. 2.Create pvc with name containing "." in cli. $ cat pvc-one.json { "apiVersion": "v1", "kind": "PersistentVolumeClaim", "metadata": { "name": "pvc.test" }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "2Gi" } } } } $ oc create -f pvc-one.json persistentvolumeclaim "pvc.test" created $ oc get pvc NAME STATUS VOLUME CAPACITY ACCESSMODES AGE pvc.test Pending 6s 3. Actual results: 1.Could not create pvc.test on web console. 2.Could create pvc.test in cli successfully. Expected results: 1,2.Should have consistent validation about pvc name from web console and cli. Additional info: Creating other resources have same issue, too. eg: route.