You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you already have an issue opened with F5 support?
Yes
Description
When sending a declaration via POST to the /declare endpoint, CFE makes the initial requests to get/set the storage account name, device.init has not yet been called and therefore the proxy settings are unavailable. These requests will bypass the proxy server.
We tracking the fix with internal issue EC-485.
Environment information
For bugs, enter the following information:
Cloud Failover Extension Version: 2.0.x
BIG-IP version: 17.1.1
Cloud provider: AWS/Azure/GCP
Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 3
Severity level definitions:
Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
Severity 2 (High) : Defect is causing major obstruction of system operations.
Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.
The text was updated successfully, but these errors were encountered:
mikeshimkus
changed the title
Initial requests to get CFE storage account info do not use proxy server
Initial declare requests to get CFE storage account info do not use proxy server
Mar 25, 2024
Do you already have an issue opened with F5 support?
Yes
Description
When sending a declaration via POST to the /declare endpoint, CFE makes the initial requests to get/set the storage account name, device.init has not yet been called and therefore the proxy settings are unavailable. These requests will bypass the proxy server.
We tracking the fix with internal issue EC-485.
Environment information
For bugs, enter the following information:
Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 3
Severity level definitions:
The text was updated successfully, but these errors were encountered: