| Summary: | rest: unable to migrate and reduce the replicate count on a distributed-replicate volume | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Dustin Tsang <dtsang> |
| Component: | rhsc-sdk | Assignee: | Shubhendu Tripathi <shtripat> |
| Status: | CLOSED NOTABUG | QA Contact: | Dustin Tsang <dtsang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1 | CC: | dpati, dtsang, knarra, mmahoney, mmccune, pprakash, rhs-bugs, ssampat |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-17 05:30:45 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: | |
update to comment#0. Expected result should be "Reducing replica count of volume is disallowed in glusterfs 3.4.0.49rhs" This is not a bug. Because reducing replica count is not a migration but normal DELETE action. Migration is meant for distribute type only. |
Description of problem: unable to reduce the replicate volume from replicate of 2 to 1 during a brick migration. Passing with/without the replica_count resulted in the same issue: POST /api/clusters/7934c13e-8067-48e7-9a68-0fb1407c28e3/glustervolumes/613d9e85-ea82-4e43-b04a-9d3212180000/bricks/migrate <?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]" <action>[\n]" <bricks>[\n]" <replica_count>1</replica_count>[\n]" <brick>[\n]" <name>latest-a:/bricks/201312130656284161942637805</name>[\n]" </brick>[\n]" <brick>[\n]" <name>latest-a:/bricks/201312130656284621245056192</name>[\n]" </brick>[\n]" <brick>[\n]" <name>latest-a:/bricks/20131213065628462516730110</name>[\n]" </brick>[\n]" </bricks>[\n]" </action>[\n]" or <?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]" <action>[\n]" <bricks>[\n]" <brick>[\n]" <name>latest-a:/bricks/201312130656284161942637805</name>[\n]" </brick>[\n]" <brick>[\n]" <name>latest-a:/bricks/201312130656284621245056192</name>[\n]" </brick>[\n]" <brick>[\n]" <name>latest-a:/bricks/20131213065628462516730110</name>[\n]" </brick>[\n]" </bricks>[\n]" </action>[\n]" Results in: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]" <fault>[\n]" <reason>Operation Failed</reason>[\n]" <detail>[volume remove brick start failed[\n]" error: remove brick incorrect brick count of 3 for replica 2[\n]" return code: -1]</detail>[\n]" </fault>[\n]" Version-Release number of selected component (if applicable): rhsc-cb11 How reproducible: 100% of the time Steps to Reproduce: 1. create a dist rep volume 3x2 2. migrate a one brick from each replicate pair as shown in the description Actual results: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>[\n]" <fault>[\n]" <reason>Operation Failed</reason>[\n]" <detail>[volume remove brick start failed[\n]" error: remove brick incorrect brick count of 3 for replica 2[\n]" return code: -1]</detail>[\n]" </fault>[\n]" Expected results: migration call should succeed, returning the job id in the response Additional info: