search

F5Networks / f5-google-gdm-templates

Google Deployment Templates for quickly deploying BIG-IP services in Google Cloud Platform
28 stars 45 forks source link

Cluster failed error message in cloudLibsError.log #66

Closed leondelyon3 closed 3 years ago

leondelyon3 commented 3 years ago

Do you already have an issue opened with F5 support?

NO

Description

bipgip instances are always seen as standalone. Cluster Active/Standby can't be established, see error in cloudLibsError Attached files describing all the setup in failover-api.docx, also cloud logs files attached for each bigip instances.

Template

v3.12 https://github.com/F5Networks/f5-google-gdm-templates/tree/main/supported/failover/same-net/via-api/3nic/existing-stack/payg

Severity Level

Severity: 2

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. failover-api.zip
shyawnkarim commented 3 years ago

Since this is a sev2 can you file a support case? I'll start looking into this.

leondelyon3 commented 3 years ago

it's for an internal poc. But I will open a support case. I've found also another issue, even for via-lb deployment: It is not possible to generate qkview file with the –progress-bar option because of the following error: Trapped a global exception! Schema item diags_ihealth_request.qkview_progress (tag 31600) not found

shyawnkarim commented 3 years ago

Can you send me your parameters file? My BIG-IPs cluster when I deploy with this template.

shyawnkarim commented 3 years ago

@leondelyon3 can you open a new issue for the kqview problem?

leondelyon3 commented 3 years ago

the file failover-api.zip should contains it. In mean time I've re-sent it to your email, just in case.

leondelyon3 commented 3 years ago

By changing mgmtGuiPort from 8443 to default value 443 in the yaml file, has solved the issue. More details on: https://tron.f5net.com/sr/1-7483037107/#1-3FWTSR7.

So this is definitively a bug.

shyawnkarim commented 3 years ago

I was able to duplicate this behavior. We are now tracking this bug internally with ID ESECLDTPLT-2714.

shyawnkarim commented 3 years ago

Closing.

This bug was fixed with Release 3.13.0.