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
Operator Console UI API endpoint /api/v1/subnet/apikey/register retuns empty message and the register "fails" without show any error message on the UI, UI redirects to login page, no registration happens on SUBNET.
Other users reports show that UI shows an Error 503, and apparently the cluster actually gets registered on SUBNET, just the UI fails to complete the procedure. This was observed on Operator version 5.0.10
Possible Solution
Needs to handle a nil pointer exception
Your Environment
minio-operator 5.0.10 false negative register with 505 error banner
minio-operator 5.0.11 no registration at all in SUBNET.
Environment name and version (e.g. kubernetes v1.17.2): kubernetes, kind kindest/node:v1.27.3
The text was updated successfully, but these errors were encountered:
Register Operator on subnet properly and do not show error or silently catch the error.
Steps to Reproduce (for bugs)
This is a bug when registering from MinIO Operator UI with SUBNET, snapshot of screen for reference.
When a valid active API Key is provided a PANIC error
runtime error: invalid memory address or nil pointer dereference
shows in the console pod log:Operator Console UI API endpoint
/api/v1/subnet/apikey/register
retuns empty message and the register "fails" without show any error message on the UI, UI redirects to login page, no registration happens on SUBNET.Other users reports show that UI shows an Error 503, and apparently the cluster actually gets registered on SUBNET, just the UI fails to complete the procedure. This was observed on Operator version 5.0.10
Possible Solution
Needs to handle a nil pointer exception
Your Environment
minio-operator
5.0.10 false negative register with 505 error bannerminio-operator
5.0.11 no registration at all in SUBNET.kindest/node:v1.27.3
The text was updated successfully, but these errors were encountered: