Doesnt appear the IP to transfer

[Arcedes]

Do you already have an issue opened with F5 support?

Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open an case with F5 if this is a critical issue.

Description

We have an error with the cfe where computers A (active) & B (Passive) show this configuration when running this command
curl -su admin: -X POST -d '{“action”: “dry-run”}' http://localhost:8100/mgmt/shared/cloud-failover/trigger | jq .

{
"addresses": {
"publicAddresses": {},
"operations": {
"toStandby": [
{
"networkInterface": "eni-04f8fa2ec5458c7b6",
"addresses": []
}
],
"toActive": [
{
"networkInterface": "eni-0d6d2956ca05fbeb8",
"addresses": []
}
]
},
"loadBalancerAddresses": {}
},
"routes": {
"operations": []
}
}

According to external tests, when running the same command in the same environment of the cloud provider and virtual machines with the same version of the machines, we should get the following answers.
{
"addresses": {
"publicAddresses": {
"52.52.22.39": {
"current": {
"PrivateIpAddress": "10.10.10.130",
"AssociationId": "eipassoc-05426f3a4048f8f73"
},
"target": {
"PrivateIpAddress": "10.10.11.150",
"NetworkInterfaceId": "eni-02e08ff72bb7a37f1"
},
"AllocationId": "eipalloc-014c47f1f0865b2f9"
}
},
"operations": {
"toStandby": [],
"toActive": []
},
"loadBalancerAddresses": {}
},
"routes": {
"operations": []
}
}

However, in the first case, the IP that will be transferred to the secondary Big IP does not appear.

Environment information

For bugs, enter the following information:

• Cloud Failover Extension Version: 2.1.3
• BIG-IP version: 16.1.4.1
• Cloud provider: AWS

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: <Fill in level: 1 through 5> 3

Severity level definitions:

1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
2. Severity 2 (High) : Defect is causing major obstruction of system operations.
3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.