Following servers have mismatching configuration [http://alt-minio-tier0-node03/.:9000->http://alt-minio-tier0-node07/.:9000 has incorrect configuration: context deadline exceeded http://alt-minio-tier0-node03/.:9000->http://alt-minio-tier0-node02/.:9000 has incorrect configuration: conte...
After a ton of debugging it turns out that if you are connecting using http but the MinIO server has TLS activated then you will see the above error. Just be sure the connection scheme is set to the right configuration, in this case, config["vfs.s3.scheme"] = "https". ...
type BucketRemoteArnInvalid GenericError func (e BucketRemoteArnInvalid) Error() string { return "Remote ARN has invalid format: " + e.Bucket } // BucketRemoteRemoveDisallowed when replication configuration exists type BucketRemoteRemoveDisallowed GenericError func (e BucketRemoteRemoveDisallowed) ...
ENTITY_TOO_LARGE("EntityTooLarge", "Upload exceeds the maximum allowed object size"), EXPIRED_TOKEN("ExpiredToken", "The provided token has expired"), ILLEGAL_VERSIONING_CONFIGURATION_EXCEPTION("IllegalVersioningConfigurationException", "The versioning configuration specified in the request is invalid."...
Despite attempting to add/data/disk1to the server configuration URL and experimenting with other methods, success has yet to be achieved. All the MinIO instances with/data/disk1in their nodes are functional and accessible upon logging in. However, the server fails to initiate. ...
While minio has a client and an SDK library as well, we’ll only focus on the server side component for now. Our goals install a fully S3 compatible service start automatically on system startup transport should be protected by a valid SSL certificate (for free) ...
As to what I think is happening: I think I'm having a networking/name resolution issue. I think when the cluster starts up, name resolution is incorrect and doesn't settle down until after the pods have all started. Unfortunately, I suspect that Minio has already performed name resolution ...
That user has a policy assigned that is described as follows: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::my-bucket" ] } ] } Not being an expert, but I interpret the above as the ability to take...
lite.svc.cluster.local:9000 has incorrect configuration: Expected number of endpoints 8, seen 16 https://myminio-pool-0-0.myminio-hl.tenant-lite.svc.cluster.local:9000->https://myminio-pool-0-2.myminio-hl.tenant-lite.svc.cluster.local:9000 has incorrect configuration: Expected number of ...
Probably this has to do with the range header being passed where it shouldn't because the CRT client is confused by the xl.meta file or some minio specific file metadata? Update: This only happens when checksumValidation on the SDK is disabled Steps to Reproduce (for bugs) S3AsyncClient s3...