CORTX-34384: No Mend Policy Set

[pankajgborole]

Signed-off-by: pankajgborole pankaj.g.borole@seagate.com

Problem Statement

• Problem statement

Design

• For Bug, Describe the fix here.
• For Feature, Post the link for design

Coding

Checklist for Author

• [ ] Coding conventions are followed and code is consistent

Testing

Checklist for Author

• [ ] Unit and System Tests are added
• [ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [ ] Testing was performed with RPM
• [ ] Jenkins pipelines used for testing

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

• [ ] Interface change (if any) are documented
• [ ] Side effects on other features (deployment/upgrade)
• [ ] Dependencies on other component(s)

Review Checklist

Checklist for Author

• [ ] Jira ID/ COMMUNITY is prefixed in PR title Prefix Syntax - CORTX-<5 digit JIRA ID>: <PR Title> - for Seagate Employees COMMUNITY: <PR Title> - for open source contributors
• [ ] PR is self reviewed
• [ ] Jira and state/status is updated and JIRA is updated with PR link
• [ ] Check if the description is clear and explained

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide

[stale[bot]]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[shailesh-vaidya]

@pankajgborole Can we close this pull request.

[pankajgborole]

@pankajgborole Can we close this pull request.

@shailesh-vaidya yes we can close it, as the policy enforcement completed at product level

[shailesh-vaidya]

Marking pull request as closed