Bug 1755227

Summary: Remove-brick operation displays warning message related to cluster.force-migration
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sayalee <saraut>
Component: cliAssignee: Sanju <srakonde>
Status: CLOSED ERRATA QA Contact: Sayalee <saraut>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amukherj, nchilaka, rhs-bugs, rkothiya, storage-qa-internal, vdas
Target Milestone: ---   
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-15 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:23:00 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:
Bug Depends On:    
Bug Blocks: 1696809    

Description Sayalee 2019-09-25 06:23:36 UTC 
Description of problem:
While doing remove-brick operation, a warning message is displayed :

It is recommended that remove-brick be run with cluster.force-migration option disabled to prevent possible data corruption. Doing so will ensure that files that receive writes during migration will not be migrated and will need to be manually copied after the remove-brick commit operation. Please check the value of the option and update accordingly. 
Do you want to continue with your current cluster.force-migration settings? (y/n) 

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

How reproducible:
Always

Steps to Reproduce:
1. Create a volume.
2. Try to do remove-brick operation on the volume:

#gluster v remove-brick vol1 10.70.46.246:/bricks/brick10/vol1-b1 
10.70.47.188:/bricks/brick10/vol1-b1 10.70.46.63:/bricks/brick10/vol1-b1 start

It is recommended that remove-brick be run with cluster.force-migration option disabled to prevent possible data corruption. Doing so will ensure that files that receive writes during migration will not be migrated and will need to be manually copied after the remove-brick commit operation. Please check the value of the option and update accordingly. 
Do you want to continue with your current cluster.force-migration settings? (y/n) 


Actual results:
The warning message regarding the "cluster.force-migration" is displayed even though the functionality of force-migration is not supported this release.

Expected results:
The warning should not be displayed as "cluster.force-migration" is not supported.

Additional info:

Volume Name: vol1
Type: Distribute
Volume ID: 6a3ebd81-4a87-45f1-8166-fea61ba338bd
Status: Started
Snapshot Count: 0
Number of Bricks: 12
Transport-type: tcp
Bricks:
Brick1: 10.70.47.88:/bricks/brick1/vol1-b1
Brick2: 10.70.47.190:/bricks/brick1/vol1-b1
Brick3: 10.70.47.5:/bricks/brick1/vol1-b1
Brick4: 10.70.46.246:/bricks/brick1/vol1-b1
Brick5: 10.70.47.188:/bricks/brick1/vol1-b1
Brick6: 10.70.46.63:/bricks/brick1/vol1-b1
Brick7: 10.70.46.246:/bricks/brick10/vol1-b1
Brick8: 10.70.47.188:/bricks/brick10/vol1-b1
Brick9: 10.70.46.63:/bricks/brick10/vol1-b1
Brick10: 10.70.47.88:/bricks/brick10/vol1-b1
Brick11: 10.70.47.190:/bricks/brick10/vol1-b1
Brick12: 10.70.47.5:/bricks/brick10/vol1-b1
Options Reconfigured:
transport.address-family: inet
storage.fips-mode-rchecksum: on
nfs.disable: on
Comment 10 errata-xmlrpc 2019-10-30 12:23:00 UTC 
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/RHEA-2019:3249