Requests to update f5cloudfailover state file fail if there is more than one container in CFE storage account

[mikeshimkus]

Do you already have an issue opened with F5 support?

Yes

Description

Requests to update f5cloudfailover state file fail if there is more than one container in CFE storage account.

Workaround: Use a dedicated storage account for the CFE state file.

We are tracking the fix for this in internal issue #487.

Environment information

For bugs, enter the following information:

• Cloud Failover Extension Version: 2.0.x
• BIG-IP version: 17.1.1
• Cloud provider: Azure

Severity Level

Severity: 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.

[mikeshimkus]

Addressed in v2.1.0.