Skip to content

CSTACKEX-301: automation for cs volume resize - #109

Open
sathvikaragi wants to merge 4 commits into
mainfrom
automation/CSTACKEX-301
Open

sathvikaragi wants to merge 4 commits into
mainfrom
automation/CSTACKEX-301

Conversation

@sathvikaragi

@sathvikaragi sathvikaragi commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

Description

automation test cases for volume resize.

Test cases covered:

-Stop the VM and grow the attached volume.
-Verify the resized size through:
CloudStack database
NFS3: host-side qemu-img info
iSCSI: ONTAP LUN space.size
-Verify shrinking is rejected and existing sizes remain unchanged.
-Restart the VM and validate the resized disk capacity.
-Detach volume and grow the volume again.

This PR...

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?

Screenshot 2026-10-12 at 11 54 34 AM

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

@github-actions

Copy link
Copy Markdown

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 24.75%
Branch coverage 18.87%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent - this code sleeps well at night 😴
🟡 B 60-79% Good - almost there, don't stop now 😉
🟠 C 40-59% Acceptable - your code is wearing a seatbelt, but no airbags 😬
🔴 D 20-39% Marginal - boldly shipping where no test has gone before 🖖
⛔ F < 20% Failing - tests? what tests? 🔥

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

Comment thread test/integration/plugins/ontap/iscsi/instance/test_vm_volume_attach.py Outdated
Comment thread test/integration/plugins/ontap/iscsi/instance/test_vm_volume_attach.py Outdated
@github-actions

Copy link
Copy Markdown

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 24.74%
Branch coverage 18.87%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent - this code sleeps well at night 😴
🟡 B 60-79% Good - almost there, don't stop now 😉
🟠 C 40-59% Acceptable - your code is wearing a seatbelt, but no airbags 😬
🔴 D 20-39% Marginal - boldly shipping where no test has gone before 🖖
⛔ F < 20% Failing - tests? what tests? 🔥

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

Comment thread test/integration/plugins/ontap/nfs3/instance/test_vm_volume_attach.py Outdated
Comment thread test/integration/plugins/ontap/ontap_test_base.py
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch.

@sathvikaragi
sathvikaragi force-pushed the automation/CSTACKEX-301 branch from 86b41e6 to cc697d4 Compare October 12, 2026 05:43
Move KVM host SSH helpers out of the shared test base, match the iSCSI shrink assertion to the driver message, and check the ONTAP backing file when a running-VM resize is rejected.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 24.84%
Branch coverage 19.00%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent - this code sleeps well at night 😴
🟡 B 60-79% Good - almost there, don't stop now 😉
🟠 C 40-59% Acceptable - your code is wearing a seatbelt, but no airbags 😬
🔴 D 20-39% Marginal - boldly shipping where no test has gone before 🖖
⛔ F < 20% Failing - tests? what tests? 🔥

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

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.

3 participants