Skip to content

Site Replication With Group Disabled

Jump to bottom
Cesar Celis Hernandez edited this page Aug 11, 2022 · 10 revisions

Objective: Make sure you can replicate a site with a disabled group

Steps:

  1. Create Site A
MINIO_ROOT_USER=minio MINIO_ROOT_PASSWORD=minio123 minio server /Volumes/data{1...4} --address :9000 --console-address :9001
  1. Create Site B
MINIO_ROOT_USER=minio MINIO_ROOT_PASSWORD=minio123 minio server /Volumes/data{5...8} --address :9002 --console-address :9003
  1. Create Alias for Site A
mc alias set sitea http://localhost:9000 minio minio123
  1. Create Alias for Site B
mc alias set siteb http://localhost:9002 minio minio123
  1. Create disabled user:
mc admin user add sitea disableduser secretkey
  1. Create group on Site A
mc admin group add sitea disabledgroup disableduser
  1. Disable the group:
mc admin group disable sitea disabledgroup
  1. Replicate the site
mc admin replicate add sitea siteb
  1. Verify the group was equally replicated, same status, so below should not happen anymore after fix is in latest MinIO Version:
$ mc admin group info siteb disabledgroup
Group: disabledgroup
Status: enabled <--------------------------------------- Why on Site B is enabled? It should be disabled if this was replicated from Site A.
Policy: 
Members: disableduser
$ mc admin group info sitea disabledgroup
Group: disabledgroup
Status: disabled <--------------------------------------- Look in here is disabled, so disabled is expected on Site B as well.
Policy: 
Members: disableduser
$ mc admin replicate status sitea
Bucket replication status:
No Buckets present

Policy replication status:
●  5/5 Policies in sync

User replication status:
●  1/1 Users in sync

Group replication status:
●  0/1 Groups in sync

Group           | SITEA           | SITEB          
disabledgroup   | ✗  in-sync      | ✗  in-sync

NOTE: This was already fixed in https://github.com/minio/minio/pull/15507 but current version does not include this fix yet. Please wait for MinIO Version to contain the fix because in the meantime you will observe the issue above, where group replication is having different status.

Clone this wiki locally