-
Notifications
You must be signed in to change notification settings - Fork 295
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
Unable to register MinIO deployment via UI/Console #3458
Comments
I can reproduce. Let me check... |
It looks like there was an intermittent problem on the Subnet side, because it now works fine (without making any changes). I do get an error, because I'm not a customer, but I guess that would be correct. @Smoerrebroed Can you check again? |
Hmmh, weird. So either it is an intermittent problem, or it is somehow linked to the fact that I've been running my two-node cluster with MINIO_CI_CD=true to allow for folders on the root drive to be used. Could that have an impact on the connectivity to SUBNET? |
I don't think so. I didn't use <?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>BadRequest</Code>
<Message>An error occurred when parsing the HTTP request POST at ';/api/auth/login'</Message>
<Resource>/api/auth/login</Resource>
<RequestId></RequestId>
<HostId></HostId>
</Error> It looks like MinIO tried to connect to Subnet and got an invalid response. Either it connected to an incorrect endpoint (should be https://subnet.min.io/api/auth/login) or the API didn't respond properly for a while during the time of the failed requests. |
@Smoerrebroed we did see a couple of errors happening on the 24th, https://status.apps.min.dev. Please retry and if fails we can reopen and investigate. |
NOTE
Please subscribe to our paid subscription plans for 24x7 support from our Engineering team.
Trying to register a deployment of MinIO upstream in SUBNET using SUBNET credentials does not work.
Expected Behavior
Registering a MinIO (upstream) deployment from the UI using credentials for SUBNET should (a) activate the deployment and (b) register the deployment on SUBNET.
Current Behavior
Trying to register a deployment, the attached error message is shown, regardless of which email address and/or password is being used.
Possible Solution
It used to work before, so I'm going to go out on a limb and say that we can make this work again. :-)
Steps to Reproduce (for bugs)
Context
Stumbled on this by accident. Registering via mc cli seems to work.
Regression
Yes ?Your Environment
Running on a 2 node docker setup with current Ubuntu images
The text was updated successfully, but these errors were encountered: