CFE uses hostname rather than device name when identifying traffic group about f5-cloud-failover-extension

[alaari-f5]

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

[shyawnkarim]

@C0missar is there a specific requirement that the hostnames do not match?

[C0missar]

No, just the opposite - I want them to match. But when I change the hostname from the default assigned when the CFT is executed, such as 'ip-10-195-201-249.ebus.swaws' to 'awsf5proda.sherwin.com', the device name does not change, and it cannot be changed without breaking device trust first and then rebuilding it. The problem then is that the CFE uses the host name to identify the HA members, but the traffic group is defined in terms of the device name, so HA can never work unless the two names match. This is a bug in CFE. You shouldn't have to fail over the entire device, just a single device group; besides, I don't KNOW the name of the device to build the declaration without more calls to find it. There should also be some indication of CFE failure. Upon triggering, CFE will happily report that it has failed over, when no change has occurred to either the device state, the state file, or the EIP associations. As a general rule, I think the host name and device name SHOULD match; otherwise, it's confusing operationally, if nothing else. As a separate issue, there should be a way to specify the host name in the CFT so that there is no need to manually change the device name. The amount of code that it takes to change the host name becomes ridiculous if the device name must be changed as well - break trust, change host name A, change device name A, change host name B, change device name B, rebuild trust. Thanks, Stan From: Shyawn Karim <[email protected]> Sent: Thursday, April 23, 2020 3:22 PM To: F5Networks/f5-cloud-failover-extension <[email protected]> Cc: Stanly E Ward <[email protected]>; Mention <[email protected]> Subject: [EXTERNAL] Re: [F5Networks/f5-cloud-failover-extension] CFE uses hostname rather than device name when identifying traffic group (#4) This email originated outside the Company @C0missar<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_C0missar&d=DwMCaQ&c=-YrhKbO6aFrSLScoj0Mm-IuOYlqIJC7nrlQzxTUu-mA&r=Ogz3AKalfkTeer1Wvy-1NDisU8am1gusHceS0yROSZs&m=c80H4kIIIzBaXUhqQcox_ygtq8m_moyAHoWIZSm9lRI&s=GIMcoMIA7PLmjC563ffRYxmEjP0ouYECobHRev9ymrU&e=> is there a specific requirement that the hostnames do not match? - You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_F5Networks_f5-2Dcloud-2Dfailover-2Dextension_issues_4-23issuecomment-2D618608928&d=DwMCaQ&c=-YrhKbO6aFrSLScoj0Mm-IuOYlqIJC7nrlQzxTUu-mA&r=Ogz3AKalfkTeer1Wvy-1NDisU8am1gusHceS0yROSZs&m=c80H4kIIIzBaXUhqQcox_ygtq8m_moyAHoWIZSm9lRI&s=-Q483vjOXtTU2EZenTT2R_3VmdqHEXkUmbeNR-bcOp4&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKD3XS5TIHM5B3S2VIIZFRDROCIMRANCNFSM4MKIIO3A&d=DwMCaQ&c=-YrhKbO6aFrSLScoj0Mm-IuOYlqIJC7nrlQzxTUu-mA&r=Ogz3AKalfkTeer1Wvy-1NDisU8am1gusHceS0yROSZs&m=c80H4kIIIzBaXUhqQcox_ygtq8m_moyAHoWIZSm9lRI&s=PrsOR6R-tNFXUM8dqhPLdkqj07hle3l6Ey7UQrbwBMU&e=>. SW-COMPANY USE-OTHER

[shyawnkarim]

@C0missar, thanks for this additional clarity. I've added these notes to our ticket, internal ID AUTOSDK-262.

[shyawnkarim]

@C0missar, AUTOSDK-262 has been scheduled for our next sprint, which starts tomorrow.

[shyawnkarim]

Closing.

@C0missar work on this issue has been completed and will be included in the next release on May 28, 2020.

Please feel free to reopen this issue if you still run into problems with this.