-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minio tenant deployment stuck in "Provisioning initial users" #2165
Comments
Same happens to me |
I was able to reproduce this partially, although after some seconds the users were provisioned correctly:
I used the following YAML to create the tenant: apiVersion: v1
kind: Namespace
metadata:
name: minio-tenant-st
---
apiVersion: minio.min.io/v2
kind: Tenant
metadata:
name: minio-tenant-st
namespace: minio-tenant-st
spec:
requestAutoCert: false
users:
- name: minio-tenant-st-user-0
configuration:
name: minio-tenant-st-env-configuration
pools:
- volumesPerServer: 2
name: pool-0
servers: 2
volumeClaimTemplate:
metadata:
name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: '2147483648'
---
apiVersion: v1
kind: Secret
metadata:
name: minio-tenant-st-env-configuration
namespace: minio-tenant-st
type: Opaque
stringData:
config.env: |-
export MINIO_ROOT_USER="minio"
export MINIO_ROOT_PASSWORD="minio123"
---
apiVersion: v1
kind: Secret
metadata:
name: minio-tenant-st-user-0
namespace: minio-tenant-st
type: Opaque
stringData:
CONSOLE_ACCESS_KEY: user
CONSOLE_SECRET_KEY: minio123 The operator logging shows:
It looks like it takes a little while before the |
@janhuehne could you please share the entire operator logs ? that would help us more. |
I am getting this in the pool logs Unable to use the drive https://saae-pool-0-1.saae-hl.minio-saae.svc.cluster.local:9000/export0: drive not found |
It has nothing to do with provisioning the users. It can't provision the users, because the Minio cluster won't come up properly. Please run It seems like pod |
|
|
|
Thanks for your help |
I think the message You can check the PVC information by running |
I made it work. Some errata in the creation of the PVs |
Check the operator logs for any To test it try to create a tenant without the TLS option from the console under the Security parameters, if it worked you will might need to use a custom cert. |
Closing this issue since this seems a configuration issue. |
After the deployment of a new tenant, the deployment process is stuck in the stage "Provisioning initial users" and the health is "red".
Expected Behavior
The tenant should be up and running
Current Behavior
health status is "red" and the process is stuck in "Provisioning initial users"
Steps to Reproduce (for bugs)
Your Environment
minio-operator
): 5.0.15 provided by MinIO Incuname -a
): Linux 6.7.4-200.fc39.x86_64 Add Minio operator #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024 x86_64 GNU/LinuxTenant configuration
MinIO tenant pod log
minio-tenant-st-pool-0-0:
minio-tenant-st-pool-0-1:
Operator error
I0613 22:03:22.769414 1 event.go:364] Event(v1.ObjectReference{Kind:"Tenant", Namespace:"minio-tenant-st", Name:"minio-tenant-st", UID:"2a48b9ca-735a-4476-bf33-0e8870bbc9ba", APIVersion:"minio.min.io/v2", ResourceVersion:"6119438", FieldPath:""}): type: 'Warning' reason: 'UsersCreatedFailed' Users creation failed: context deadline exceeded
Node overview:
MinIO tenant status
kubectl minio tenant status minio-tenant-st
The text was updated successfully, but these errors were encountered: