Open robertbartel opened 1 year ago
Looks like https://github.com/minio/mc/releases/tag/RELEASE.2023-03-20T17-17-53Z is the breaking release of mc
.
Verified that RELEASE.2023-03-20T17-17-53Z
is the first version with the issue.
Based on how we check the version of the mc
command in scripts/minio_init.sh
, you can not use go install github.com/minio/mc@RELEASE.2023-02-28T00-12-59Z
to get the last working version. You will need to either download a binary for that tag or clone the repo and run make build
. Verified that this is does work, at least for me.
As discussed in #242, we are using an old MinIO version, due to a deprecated feature related to backing storage and how it relates to the way DMOD is designed. It turns out that newer versions of the MinIO client applications have a minor breaking change when used with the old service version.
The break relates to how access policies are set. In short, the version used in DMOD requires the
admin policy set
command and does not support theadmin policy attach
command. The reverse is the case for new versions of the client.On a superficial level, this breaks the
minio_init.sh
helper script. Updates are pending which will at least help exit cleanly in problem situations, but not to work around them.More importantly, it isn't possible to initialize the DMOD MinIO services - and thus, a DMOD deployment - using the currently configured version, without an older version of the MinIO client application.