Operator Managed Cluster fails to run

[loverustfs]

Ref

rustfs/rustfs#987

Describe the bug
We are trying to bootstrap a cluster using the operator. The image for it was built using the files in this repository https://github.com/rustfs/operator

We are opening the issue in this repository, because from our point of view its not a issue with the operator.

When trying to Deploy a cluster on 4 nodes, the pods get created with all settings from the tenant, but fail to start due to this error in all nodes:

Initializing data directories:
Initializing log directory: /logs
Starting: /usr/bin/rustfs
   API: http://10.42.5.167:9000  http://127.0.0.1:9000
Console WebUI available at: http://10.42.5.167:9001/rustfs/console/index.html
Console WebUI (localhost): http://127.0.0.1:9001/rustfs/console/index.html
Error: Custom { kind: Other, error: Io(Custom { kind: Other, error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" } }) }

To Reproduce

1. Deploy the rustfs operator
2. Deploy a tenant configuration:

apiVersion: rustfs.com/v1alpha1
kind: Tenant
metadata:
  name: rustfs-prod
  namespace: rustfs-prod
spec:
  credsSecret:
    name: rustfs-admin-credentials
  env:
  - name: RUST_LOG
    value: debug
  image: rustfs/rustfs:1.0.0-alpha.71
  mountPath: /data
  podManagementPolicy: Parallel
  pools:
  - name: primary
    persistence:
      annotations:
        description: RustFS distributed storage volumes
      labels:
        app: rustfs
        environment: production
        team: storage
      path: /data
      volumeClaimTemplate:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 10Gi
        storageClassName: longhorn-static
      volumesPerServer: 1
    servers: 4

Expected behavior
A cluster with 4 nodes is deployed and in a running state

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
We are running the following components:

• RKE2 1.32.3 k8s Cluster on vsphere managed by rancher
• longhorn as cluster storage

[shahab96]

I am unable to reproduce this bug on my test environment. I have used the following manifest.

---
apiVersion: v1
kind: Namespace
metadata:
  name: test-rustfs
  labels:
    name: test-rustfs
---
apiVersion: v1
kind: Secret
metadata:
  name: rustfs-admin-credentials
  namespace: test-rustfs
type: Opaque
stringData:
  accesskey: "shahabaccesskey"
  secretkey: "shahabaccesskey"
---
apiVersion: rustfs.com/v1alpha1
kind: Tenant
metadata:
  name: rustfs-prod
  namespace: test-rustfs
spec:
  credsSecret:
    name: rustfs-admin-credentials
  env:
  - name: RUST_LOG
    value: debug
  image: rustfs/rustfs:1.0.0-alpha.71
  mountPath: /data
  podManagementPolicy: Parallel
  pools:
  - name: primary
    persistence:
      annotations:
        description: RustFS distributed storage volumes
      labels:
        app: rustfs
        environment: production
        team: storage
      path: /data
      volumeClaimTemplate:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 10Gi
        storageClassName: standard
      volumesPerServer: 1
    servers: 4

[shahab96]

It seems that this issue is fixed by #58