You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not clear from the charm docs that the secret-key needs to be at least 8 char long
It is also not very verbose from Juju POV what is actually happening on the charm
Ideally I would expect to have some config value validation on the charm to set it maybe on blocked state but avoid having the actual service down
Reproduce
juju config minio secret-key=minio
Logs
I cannot access MinIO website
$ juju status | grep minio
minio res:oci-image@1755999 waiting 1 minio ckf-1.7/stable 186 10.152.183.165 no
mlflow-minio res:oci-image@1755999 active 1 minio ckf-1.7/edge 186 10.152.183.108 no
minio/0* error idle 10.1.149.251 9000/TCP,9001/TCP crash loop backoff: back-off 2m40s restarting failed container=minio pod=minio-0_kubeflow(1980c8fe-8cb3-4099-b9eb-2c6...
mlflow-minio/0* active idle 10.1.150.41 9000/TCP,9001/TCP
$ microk8s.kubectl logs -n kubeflow minio-0
Defaulted container "minio" out of: minio, juju-pod-init (init)
ERROR Unable to validate credentials inherited from the shell environment: Invalid credentials
> Please provide correct credentials
HINT:
Access key length should be at least 3, and secret key length at least 8 characters
The text was updated successfully, but these errors were encountered:
It is not clear from the charm docs that the secret-key needs to be at least 8 char long
It is also not very verbose from Juju POV what is actually happening on the charm
Ideally I would expect to have some config value validation on the charm to set it maybe on blocked state but avoid having the actual service down
Reproduce
Logs
I cannot access MinIO website
$ microk8s.kubectl get pods -n kubeflow | grep minio minio-operator-0 1/1 Running 0 40d mlflow-minio-operator-0 1/1 Running 0 67m mlflow-minio-0 1/1 Running 0 66m minio-0 0/1 CrashLoopBackOff 5 (105s ago) 6m24s
The text was updated successfully, but these errors were encountered: