Skip to content

Reuse the shared ONTAP snapshot delete during VM snapshot rollback so cleanup follows the normal delete path. - #127

Merged
sandeeplocharla merged 1 commit into
mainfrom
bugfix/CSTACKEX-357
Oct 15, 2026
Merged

sandeeplocharla merged 1 commit into
mainfrom
bugfix/CSTACKEX-357

Conversation

@sandeeplocharla

Copy link
Copy Markdown
Collaborator

Description

This PR is to address a comment received on apache#13897 .
rollbackFlexVolSnapshot now uses deleteFlexVolSnapshotForCloudStackVolume instead of issuing its own snapshot delete.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@piyush5netapp piyush5netapp left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just test the snapshot once for cross confirmation.

@sandeeplocharla
sandeeplocharla merged commit 81bf88e into main Oct 15, 2026
11 of 12 checks passed
sandeeplocharla added a commit that referenced this pull request Oct 15, 2026
… cleanup follows the normal delete path. (#127)

### Description

This PR is to address a comment received on
apache#13897 .
`rollbackFlexVolSnapshot` now uses
`deleteFlexVolSnapshotForCloudStackVolume` instead of issuing its own
snapshot delete.


<!-- When "Fixes: #<id>" is specified, the issue/PR will automatically
be closed when this PR gets merged -->
<!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
<!-- Fixes: # -->

<!---
*******************************************************************************
-->
<!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE
DOCUMENTATION. -->
<!--- PLEASE PUT AN 'X' in only **ONE** box -->
<!---
*******************************************************************************
-->

### Types of changes

- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Enhancement (improves an existing feature and functionality)
- [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
- [ ] Build/CI
- [ ] Test (unit or integration test code)

### Feature/Enhancement Scale or Bug Severity

#### Feature/Enhancement Scale

- [ ] Major
- [ ] Minor

#### Bug Severity

- [ ] BLOCKER
- [ ] Critical
- [ ] Major
- [X] Minor
- [ ] Trivial

### Screenshots (if appropriate):

### How Has This Been Tested?

<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran
to -->

#### How did you try to break this feature and the system with this
change?

<!-- see how your change affects other areas of the code, etc. -->

<!-- Please read the
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md)
document -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants