Bug 1327223 - 2.0: crush_rule API: PATCHing the 'name' with non-alphanumeric characters does not work
Summary: 2.0: crush_rule API: PATCHing the 'name' with non-alphanumeric characters doe...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Calamari
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 3.1
Assignee: Boris Ranto
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-14 13:59 UTC by Harish NV Rao
Modified: 2017-07-19 13:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-19 13:21:34 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Harish NV Rao 2016-04-14 13:59:27 UTC
Description of problem:
 PATCHing the 'name' with non-alphanumeric characters does not work for crush_rule api. It does not fail and does not change the name also. It should either fail or change the name. 

Version-Release number of selected component (if applicable):10.1.1-1.el7cp

How reproducible: always

Steps to Reproduce:
1. PATCH the crush_rule api for name with non-alphanumeric characters. e.g., replicated_ruleset_Test_#!@[ ?;
2. PATCH operation completes with:
HTTP 202 ACCEPTED
Vary: Accept
Content-Type: text/html; charset=utf-8
Allow: GET, DELETE, HEAD, OPTIONS, PATCH
{
    "request_id": "d4aa85ea-56d4-4758-90d7-13b3f128cd55"
}
3. Do GET on this crush rule.

Actual results:
The name is not changed

Expected results:
Either change the name or do not accept the command

Additional info:
Works for "-" and "_"

Comment 2 Christina Meno 2016-04-20 13:13:36 UTC
There probably could be more validation on the front end.

Harish would you please check the /api/v2/request endpoint after trying this operation? I suspect you'll see the failure there.

Comment 7 Christina Meno 2017-07-19 13:21:34 UTC
calamari won't ship in rhcs 3.0


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