Skip to content
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

Operator UI allows creation of Tenant without required Encryption fields #1610

Closed
cesnietor opened this issue May 22, 2023 · 6 comments · Fixed by #1730
Closed

Operator UI allows creation of Tenant without required Encryption fields #1610

cesnietor opened this issue May 22, 2023 · 6 comments · Fixed by #1730
Labels
bug Something isn't working community

Comments

@cesnietor
Copy link
Contributor

If I write something on the Encryption fields, the Create button is disabled until all fields are set but if I started setting up some fields and I change between encryption methods, the Create button gets enabled and allows us to create a Tenant. Which then causes an error while trying to initialize it. I think we probably need to refresh the button state every time we change encryption methods.

Screen.Recording.2023-05-22.at.10.24.14.AM.mov

Since it allows the creation of the tenant, it fails while creating the KES pod
Screenshot 2023-05-22 at 10 20 31 AM

Expected Behavior

Created button should be disabled if Encryption is Enabled and not all fields are being set.
Created button state should be refreshed if changing encryption method and fields should also be refreshed to empty values.

Current Behavior

Encryption fields hold value even after changing encryption method

Possible Solution

Refresh button state on change of encryption method

Steps to Reproduce (for bugs)

  1. On UI, Click on Create Tenant
  2. Fillup initial required fields (name, namespace, etc)
  3. Go to Encryption tab and enable it
  4. Select Vault and write something on Endpoint
  5. Change to AWS method
  6. Go back to Vault Method (here the Create button is enabled but not all required fields have been set)

Context

Regression

Your Environment

  • Version used (minio-operator): v5.0.4
  • Environment name and version (e.g. kubernetes v1.17.2):
  • Server type and version:
  • Operating System and version (uname -a):
  • Link to your deployment file:
@jiuker
Copy link
Contributor

jiuker commented Jul 5, 2023

Something cannot work, see go-openapi/validate#152

@cesnietor
Copy link
Contributor Author

@jiuker I believe this is also a UI issue, the UI portion of it doesn't seem to be addressed by the PR is that correct? cc @bexsoft

@jiuker
Copy link
Contributor

jiuker commented Aug 22, 2023

@jiuker I believe this is also a UI issue, the UI portion of it doesn't seem to be addressed by the PR is that correct? cc @bexsoft

Yes. But the backend is where the data is finally validated. I am not good at frontend by the way. Right now it's not submittable, the backend will return an error but it won't show the error either, if you're good at front-end, you can help with that.

@cesnietor
Copy link
Contributor Author

thanks, I'll reopen the issue then. Thanks @jiuker for adding a validation.

@cesnietor cesnietor reopened this Aug 22, 2023
@jiuker
Copy link
Contributor

jiuker commented Aug 23, 2023

thanks, I'll reopen the issue then. Thanks @jiuker for adding a validation.

Actually it was already there, it just didn't take effect, I went and submitted a pr to valid to fix the problem

@jiuker jiuker assigned cesnietor and unassigned jiuker Sep 4, 2023
@cesnietor cesnietor removed their assignment Sep 5, 2023
@cesnietor
Copy link
Contributor Author

closing this since operator ui has been deprecated, see https://github.com/minio/operator/blob/master/docs/notes/v6.0.0.md#whats-new for more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working community
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants