Seagate / cortx-ha

CORTX ha (High-Availability) is responsible for ensuring that CORTX Solution is available in case of any hardware component or software service failures. It takes care of failover/ failback control flow for affected services and stabilizes them across CORTX cluster.

https://github.com/Seagate/cortx

GNU Affero General Public License v3.0

4 stars 45 forks source link

CORTX-29399 : When pod is restarted via replicas or kubectl delete, pod_restart count is not set properly. #680

Closed gauri-bhosale closed 2 years ago

gauri-bhosale commented 2 years ago

Signed-off-by: gauri.bhosale gauri.bhosale@seagate.com

Problem Statement

When pod is restarted via replicas or kubectl delete, pod_restart count is not set properly.

Design

system_health status checked incoming genericId and stored genericId if its not same checked for status but status not only my online it may 'starting' also
Coding
[X] Coding conventions are followed and code is consistent

Testing

[X] Unit and System Tests are added
[X] Test Cases cover Happy Path, Non-Happy Path and Scalability
[X] Testing was performed with RPM
https://jts.seagate.com/secure/attachment/513156/Test_Results.txt

Review Checklist

[X] PR is self reviewed
[X] JIRA number/GitHub Issue added to PR
[X] Jira and state/status is updated and JIRA is updated with PR link
[X] Check if the description is clear and explained

Review Checklist

[X] Is perfline test run and the report with and without the changes updated in the PR? [Y/N]:

Testing result :https://jts.seagate.com/secure/attachment/513156/Test_Results.txt