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

Alert is not generated when specifying a rule and not including NFS version #47

Open
ms185570 opened this issue Sep 13, 2021 · 2 comments
Labels
backend Issues related to the backend service or the APIs. jira Has an Internal Jira Story

Comments

@ms185570
Copy link

If you create an export policy with a rule that does not have the nfsv3 or nfsv41 block then the export policy does not get created. Instead there should be an error stating that one of them are required.

@okrause
Copy link
Contributor

okrause commented Sep 21, 2021

The behaviour mirrors what the UI does. Without either "ticking" NFSv3 or NFSv4, the export rule is invalid. Without any valid export rule, no export policy is created.
What happens here is, that we pass the (invalid) export rule to the API and the API silently ignores it. The UI - in contrast - throws an error telling the user what is wrong. See picture.
While this "works as designed", one could argue that the API or the TF provider could be more user friendly and return an error ...

image

@lonico lonico added the backend Issues related to the backend service or the APIs. label Jan 10, 2022
@carchi8py
Copy link
Collaborator

carchi8py commented Mar 29, 2022

An internal story 4851 has been made for this issue.

@carchi8py carchi8py added the jira Has an Internal Jira Story label Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issues related to the backend service or the APIs. jira Has an Internal Jira Story
Projects
None yet
Development

No branches or pull requests

4 participants