Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial declare requests to get CFE storage account info do not use proxy server #138

Closed
mikeshimkus opened this issue Mar 25, 2024 · 1 comment

Comments

@mikeshimkus
Copy link
Contributor

mikeshimkus commented 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:

  • 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:

  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 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
@mikeshimkus
Copy link
Contributor Author

Addressed in v2.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant