Verify Azure API works before enabling ANF backend #466
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes [issue NetApp#465](NetApp#465) **Describe the solution you'd like** As of v20.04, the Azure NetApp Files backend will report itself as being `online` even if its `backend.json` contains invalid credentials. The backend should report itself as being `offline` or `failed` in this scenario. **Describe alternatives you've considered** The current workaround is to initialize the backend with `tridentctl create backend` and then attempt to provision a volume through a `PersistentVolumeClaim` or wait for capacity pool discovery to take place.
netapp-ci
pushed a commit
that referenced
this pull request
Jan 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue #465
Describe the solution you'd like
As of v20.04, the Azure NetApp Files backend will report itself as being
onlineeven if itsbackend.jsoncontains invalid credentials. The backend should report itself as beingofflineorfailedin this scenario.Describe alternatives you've considered
The current workaround is to initialize the backend with
tridentctl create backendand then attempt to provision a volume through aPersistentVolumeClaimor wait for capacity pool discovery to take place.