Set quota on target directory based on source actual size, not by its current consumed size

[santhoshatdell]

Description

• Set quota on target directory based on source actual size, not by its current consumed size.
• Updated version from 2.6.0 to 2.6.1

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#753

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes (79.9%)
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• Backward compatibility is not broken

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Tested 10 PVs creation with no quotas and 20 PVs (5+5+10) with quotas enabled. When quotas is enabled, same quota gets set on both source and target directories.
• Tested RG sync and failover actions. Verified data writes to source before failover and writes to target after failover.
  Captured log snippets.txt

Another round of test logs for QuotaScan workaround fix.
Test log - SyncIQ - QuotaScan.txt

[prablr79]

@santhoshatdell can we get the checklist fully checked for this PR ?

[santhoshatdell]

@santhoshatdell can we get the checklist fully checked for this PR ?

Hi Prasanna,
I only work on replication related changes in this repo. When I do, I update replication related unit tests and try to keep up code coverage %. I cannot get the coverage to above 90%. We also have our e2e tests which we run to verify our fixes.