Hide Forgot
Description of problem: Creation of cluster, pool or device fails if name contains some "special" character like: space or character with diacritics (e.g. ěščřžýáíéůú). Version-Release number of selected component (if applicable): rhscon-ui-0.0.26-1.el7.noarch rhscon-ceph-0.0.9-1.el7.x86_64 rhscon-core-0.0.12-1.el7.x86_64 rhscon-agent-0.0.4-1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Prepare few servers for USM Ceph cluster accordingly to the documentation. 2. Try to create cluster with name containing some of the problematic character, e.g.: Test Cluster A ěščřžýáíé etc. 3. Create cluster with correct name. 4. Try to create storage pool/device similarly as cluster in step 2. Actual results: The cluster/pool/device creation fails on some point of the creation process. Expected results: The web UI/REST API doesn't allow submitting the request with problematic characters in some input field. Additional info: Which characters are allowed in the form fields around the skyring web UI/REST API fields? Please consider this topic also for other places - e.g. user login name.
Have you tried this from the REST browser or UI? ideally the validations are supposed to be at UI level and the REST API(core) will not do any validations.
I've tried it via web UI. I think/agree, that there might be some limitation for the names (because for example cluster name is used also for the ceph configuration file name), but I think it should be covered/validated on both layers - web UI and also in REST API.
I doubt we have the bandwidth to take this up for the current release, a good candidate to move to nect release
Yes I agree, probably we will try to incorporate the straight forward cases if we have time. setting the severity to low. In any case this need to be documented and we should provide set of valid names for cluster/pools etc.
Per bug scrub meeting, this is low priority, moving to 3.0
Looking at ceph documentation[1], cluster name should be "simple string without spaces". The full description of cluster name follows: > Cluster Name: Ceph clusters have a cluster name, which is a simple string > without spaces. The default cluster name is ceph, but you may specify a > different cluster name. Overriding the default cluster name is especially > useful when you are working with multiple clusters and you need to clearly > understand which cluster your are working with. > > For example, when you run multiple clusters in a federated architecture, the > cluster name (e.g., us-west, us-east) identifies the cluster for the current > CLI session. Note: To identify the cluster name on the command line interface, > specify the a Ceph configuration file with the cluster name (e.g., ceph.conf, > us-west.conf, us-east.conf, etc.). Also see CLI usage (ceph --cluster > {cluster-name}). So if RHSC 2.0 allows a user to create a cluster with space in it's name, it blatantly goes agains ceph expectations. which means that RHSC 2.0 would allow admin to create a ceph cluster in unsupported/untested configuration. Based on this fact, I'm asking to reevaluate. [1] http://docs.ceph.com/docs/master/install/manual-deployment/