Bug 1329244

Summary: 2.0: crush_rule API: Creating a new rule with min_size > max_size succeeds
Product: Red Hat Ceph Storage Reporter: Harish NV Rao <hnallurv>
Component: CalamariAssignee: Boris Ranto <branto>
Calamari sub component: Back-end QA Contact: Vidushi Mishra <vimishra>
Status: CLOSED WONTFIX Docs Contact:
Severity: high    
Priority: unspecified CC: ceph-eng-bugs, gmeno, uboppana
Version: 2.0   
Target Milestone: rc   
Target Release: 2.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 17:26:22 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:

Description Harish NV Rao 2016-04-21 13:24:56 UTC
Description of problem:

  Creating a new rule with min_size > max_size succeeds

Version-Release number of selected component (if applicable): 


How reproducible: always


Steps to Reproduce:
1. Create a new rule via crush_rule API by specifying min_size > max_size

    {
        "id": 3, 
        "name": "replicated_ruleset_kdsjf", 
        "ruleset": 0, 
        "type": "replicated", 
        "min_size": 100, 
        "max_size": 10, 
        "steps": [
           :
           :
  
Actual results:
new crush rule is created successfully

Expected results:
new crush rule should not be created and should display error message indicating min_size > max_size.

Additional info: