BugFixes For CSTACKEX-176, CSTACKEX-172, CSTACKEX-199 and CSTACKEX-181#65
Open
suryag1201 wants to merge 4 commits into
Open
BugFixes For CSTACKEX-176, CSTACKEX-172, CSTACKEX-199 and CSTACKEX-181#65suryag1201 wants to merge 4 commits into
suryag1201 wants to merge 4 commits into
Conversation
suryag1201
requested review from
piyush5netapp,
rajiv-jain-netapp and
sandeeplocharla
as code owners
sandeeplocharla
approved these changes
Jun 19, 2026
suryag1201
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR...
CSTACKEX-176: Storage Pool Backend by ONTAP FlexVolume is not Thin Provisioned
CSTACKEX-172: VM create failure due to aggrs not available and UI says "Unable to orchestrate the start of VM instance"
CSTACKEX-199: Error message when cluster password is wrong while creating primary storage pool is not user intuitive
CSTACKEX-181: Multiple host with same hostname will not follow per host igroup design
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
1- Create a storage pool with invalid ontap cred - throw the error
2- Create a storage pool with valid ontap cred - success
3- Verify Ontap Volume - thin provisioned
4- VM instance VM1 creation - suceess and igroup created with cs_svmName_hostUUID
5- VM instance VM2 creation - reused the same igroup
6- VM instance VM1 and VM2 delete - igroup also got deleted
How did you try to break this feature and the system with this change?