Adding volume info validations

[AmarnatReddy]

Description

Adding volume info validations

Scenarios for Volume Info Validation with Data Write:

1. Verify Volume Info Details Without Any Data
2. Create Subvolumes and Validate Usage Details
3. Mount Subvolumes, Write Data, and Validate Usage
4. Create Subvolume Group and Subvolumes, Validate Usage Details
5. Delete Subvolumes and Validate Usage During Deletion

Logs:
With erasure: http://magna002.ceph.redhat.com/cephci-jenkins/cephci-run-G5H6NB/
without erasure : http://magna002.ceph.redhat.com/cephci-jenkins/cephci-run-TWL5CW/

Please include Automation development guidelines. Source of Test case - New Feature/Regression Test/Close loop of customer BZs

click to expand checklist

• Create a test case in Polarion reviewed and approved.
• Create a design/automation approach doc. Optional for tests with similar tests already automated.
• Review the automation design
• Implement the test script and perform test runs
• Submit PR for code review and approve
• Update Polarion Test with Automation script details and update automation fields
• If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

[neha-gangadhar]

@AmarnatReddy Are we updating any existing polarion testcase? or adding a new one for all volume management scenarios?

[AmarnatReddy]

@AmarnatReddy Are we updating any existing polarion testcase? or adding a new one for all volume management scenarios?

We need a new test to cover volume info command.

[Manimaran-MM]

@AmarnatReddy Are we updating any existing polarion testcase? or adding a new one for all volume management scenarios?

We need a new test to cover volume info command.

@AmarnatReddy We have an existing TC which covers volume info without data write. If possible can we extend the same TC?
https://polarion.engineering.redhat.com/polarion/#/project/CEPH/workitem?id=CEPH-83604097

[hkadam134]

Amar,

Can't this be included in our common file for all cephfs volume-related operations instead of creating a new file ?

• test:
  name: CephFS Volume Operations
  module: cephfs_vol_management.cephfs_vol_mgmt_test_volume.py
  polarion-id: CEPH-83604097
  desc: Test for validating all CephFS Volume Operations
  abort-on-fail: false

[AmarnatReddy]

Amar,

Can't this be included in our common file for all cephfs volume-related operations instead of creating a new file ?

• test:
  name: CephFS Volume Operations
  module: cephfs_vol_management.cephfs_vol_mgmt_test_volume.py
  polarion-id: CEPH-83604097
  desc: Test for validating all CephFS Volume Operations
  abort-on-fail: false

Hi Hemanth,
I reviewed the cephfs_vol_mgmt_test_volume.py file, and I noticed that it primarily focuses on verifying commands and their outputs. However, in my case requires additional steps, such as mounting the volume, writing data, and validating the usage.
So only created a separate test case

[neha-gangadhar]

Is this only valid for squid? Can we add them to reef and quincy too?

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AmarnatReddy, Manimaran-MM

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment