Region activation for MinIO OSE failed due to an inability to fetch the Storage Tenant ID.
search cancel

Region activation for MinIO OSE failed due to an inability to fetch the Storage Tenant ID.

book

Article ID: 421213

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • The system could not activate the MinIO OSE Region because it was unable to retrieve the required Storage Tenant ID.



    Note: Here, MinIO is deployed as Solution add-on and NOT as OSE VM. 

Environment

VCD 10.6.X
OSE 3.1

 

Cause

MinIO Operator version 4.3.7 is not compatible with OSE 3.1. It should be 5.X

Resolution

Below steps to executed to check MinIO Operator version:

  • Logon to MinIO Server. 
  • cd /minio/minio-operator and run the commands below: 
  • kubectl get pod 0n minio-operator
  • Above command shows MinIO Operator Pod name.
  • Copy the complete name and run below command: 

    kubectl describe pod -n minio-operator minio-operator-<id>-<id> | grep -A5 image

    xxxx@servername :~ /minio/minio-operator# kubectl describe po -n minio-operator minio-operator-<id>-<id> | grep -A5 Image
    Image : XXXXX.XXXX.XXX/library/operator:v4.3.7

  • Or,  run the command: helm list -A

    XXX@mServername :~ /minio/minio-operator# helm list -A
    NAME                        Namespace          revision             Chart                  APP VERSION       
    minio-operator           minio-operator          1                minio-operator-4.3.7      v4.3.7 

  • MinIO Operator version 4.3.7 is lower than compatible version of MiniO Operator which is 5.X. It should be 5.X as per below document. 
  • Reference: Before you begin
  • Issue resolves post deploying MinIO Operator of version 5.X