[CPDEV-93296]PAAS_check_failed_after_procedure_Kubernetes_upgrade

[nikhil1697]

Description

After Kubernetes Upgrade procedure check_paas indicates inconsistencies in the IP address management (IPAM) system used by Calico in Kubernetes cluster. Specifically, it identifies the following problems:

1. IPs with missing handles: These are IP addresses that are allocated but do not have corresponding handles in the IPAM system.
2. Handles with no matching IPs: These are handles in the IPAM system that do not have corresponding IP addresses allocated to them.

Solution

Added a function(release_calico_leaked_ips) in the upgrade procedure. This function should parse the output of the calicoctl ipam check --show-problem-ips command, identify the problematic IPs and handles, and release them automatically.
*

Test Cases

TestCase 1

Steps:

1. Run kubemarine upgrade
2. Run kubemarine check_paas

Results:

Before	After
ipam check indicates some problems, for more info you can use calicoctl ipam check --show-problem-ips	pass_check for Calico will be successful

Unit tests

Indicate new or changed unit tests and what they do, if any.

[vlar0816]

task release_calico_leaked_ips fails with the following message

2024-07-04 08:28:29,803 INFO *** TASK release_calico_leaked_ips ***
2024-07-04 08:28:29,803 DEBUG Getting leaked ips...
2024-07-04 08:28:30,032 DEBUG Found 0 leaked ips
rm: cannot remove '/tmp/7cdc7a2183a94e69834f91e37f425ae9.json': No such file or directory
2024-07-04 08:28:30,068 CRITICAL FAILURE!
2024-07-04 08:28:30,068 CRITICAL TASK FAILED release_calico_leaked_ips
2024-07-04 08:28:30,068 CRITICAL KME0002: Remote group exception