CFE uses hostname rather than device name when identifying traffic group

[C0missar]

If the host name of the device does not match the device name in the device group, CFE is unable to identify itself and determine which traffic groups are associated. The result is that both devices think they are in standby, both report themselves as being in standby in response to a call to /mgmt/shared/cloud-failover/inspect, and no EIP re-association ever occurs.

The host name is written to the S3 f5cloudfailoverstate.json file, and the failover script searches for this name in the device group.

The CFE should only use the device name for identification of the traffic groups.

[shyawnkarim]

Thanks for reporting this bug. I've created internal ID AUTOSDK-262 to get this fixed.

[C0missar]

Any guess on when we'll see a fix? I'm trying to determine how much effort to put in to a workaround. There is one other CFT issue that would be very helpful to see addressed in the official released CFT, and that is issue #74. I'm not sufficiently familiar with CFTs to know how to code these ready tests, and it seems to me that everyone would want the same things: * Licensed * Config loaded * REST interface up * Config UI running There are other things that some people might want to check, but it seems to me that at a minimum, if any of these are not true, then we don't have a useful instance yet. Thanks, Stan Ward IT Application Security Architect The Sherwin-Williams Company Cell: 937.344.8342 Stan.Ward@Sherwin.com<mailto:michael.s.tetreault@sherwin.com> http://www.sherwin-williams.com<http://www.sherwin-williams.com/> From: Shyawn Karim <notifications@github.com> Sent: Thursday, April 9, 2020 2:27 PM To: f5devcentral/f5-cloud-failover-extension <f5-cloud-failover-extension@noreply.github.com> Cc: Stanly E Ward <Stan.Ward@sherwin.com>; Author <author@noreply.github.com> Subject: [EXTERNAL] Re: [f5devcentral/f5-cloud-failover-extension] CFE uses hostname rather than device name when identifying traffic group (#23) This email originated outside the Company Thanks for reporting this bug. I've created internal ID AUTOSDK-262 to get this fixed. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_f5devcentral_f5-2Dcloud-2Dfailover-2Dextension_issues_23-23issuecomment-2D611682849&d=DwMCaQ&c=-YrhKbO6aFrSLScoj0Mm-IuOYlqIJC7nrlQzxTUu-mA&r=Ogz3AKalfkTeer1Wvy-1NDisU8am1gusHceS0yROSZs&m=9DP1__e0JRGrwNV6I6SxbCGHg4PvVLcYZzJ-0BqKU1g&s=TJ4A1Zwcd0WuBGA3nS6U1_y4CgmNgUnOBsnwoXq4kFk&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKD3XSYAOSFW2O2IK73XK7TRLYHO3ANCNFSM4LTYWJ4A&d=DwMCaQ&c=-YrhKbO6aFrSLScoj0Mm-IuOYlqIJC7nrlQzxTUu-mA&r=Ogz3AKalfkTeer1Wvy-1NDisU8am1gusHceS0yROSZs&m=9DP1__e0JRGrwNV6I6SxbCGHg4PvVLcYZzJ-0BqKU1g&s=mQ8X_GK-22_zJv-kKNQa0lDWc971KZDEgsNJodIOhas&e=>. SW-COMPANY USE-OTHER

[shyawnkarim]

I can give you an update once this bug has been prioritized for a sprint.

[alaari-f5]

Closing this issue

As of release CFE 1.2 we moved this CFE repo under F5Networks. Your issue was recreated there. To follow-up on this issue visit:

F5Networks/f5-cloud-failover-extension#4