Closed JeffGiroux closed 4 years ago
This appears to only affect versions 15.x. I tried 14.x and 13.x and both the latter versions successfully clustered.
Here's the 15.0.1 output. Different messages from 15.1.0.2...but still...not cluster.
2020-06-04T18:48:11.923Z info: [pid: 29117] [scripts/autoscale.js] Cluster action UPDATE
2020-06-04T18:48:11.924Z debug: [pid: 29117] [lib/bigIp.js] list localhost /tm/cm/trust-domain/Root
2020-06-04T18:48:11.940Z debug: [pid: 29117] [lib/bigIp.js] {"kind":"tm:cm:trust-domain:trust-domainstate","name":"Root","fullPath":"Root","generation":789,"selfLink":"https://localhost/mgmt/tm/cm/trust-domain/Root?ver=15.0.1","caCert":"/Common/dtca.crt","caCertReference":{"link":"https://localhost/mgmt/tm/cm/cert/~Common~dtca.crt?ver=15.0.1"},"caCertBundle":"/Common/dtca-bundle.crt","caCertBundleReference":{"link":"https://localhost/mgmt/tm/cm/cert/~Common~dtca-bundle.crt?ver=15.0.1"},"caDevices":["/Common/jg-f5-autoscale150-bigip-46l6.c.f5-4136-mspteam-dev.internal"],"caDevicesReference":[{"link":"https://localhost/mgmt/tm/cm/device/~Common~jg-f5-autoscale150-bigip-46l6.c.f5-4136-mspteam-dev.internal?ver=15.0.1"}],"caKey":"/Common/dtca.key","caKeyReference":{"link":"https://localhost/mgmt/tm/cm/key/~Common~dtca.key?ver=15.0.1"},"status":"standalone","trustGroup":"/Common/device_trust_group","trustGroupReference":{"link":"https://localhost/mgmt/tm/cm/device-group/~Common~device_trust_group?ver=15.0.1"}}
2020-06-04T18:48:11.941Z info: [pid: 29117] [scripts/autoscale.js] This instance is not in cluster. Requesting join.
2020-06-04T18:48:11.942Z silly: [pid: 29117] [scripts/autoscale.js] Join request is too soon after last join request. 32509 ms
2020-06-04T18:48:11.943Z info: [pid: 29117] [scripts/autoscale.js] Checking for messages
2020-06-04T18:48:14.119Z debug: [pid: 29117] [scripts/autoscale.js] Handling 0 message(s)
2020-06-04T18:48:14.124Z info: [pid: 29117] [lib/util.js] Autoscale finished.
2020-06-04T18:48:14.120Z silly: [pid: 29117] [scripts/autoscale.js] number of messages to read:
2020-06-04T18:48:14.121Z silly: [pid: 29117] [scripts/autoscale.js] number of read messages:
These versions work fine... f5-bigip-13-1-3-2-0-0-4-payg-best-1gbps-20191105210022 f5-bigip-14-1-2-3-0-0-5-payg-best-1gbps-191218142340
These versions do not cluster... f5-bigip-15-0-1-0-0-11-payg-best-25mbps-190803012348 f5-bigip-15-1-0-2-0-0-9-payg-best-25mbps-200321032524
Thanks for reporting this issue! Could you please provide qkviews from master and problematic hosts?
I just tested latest release gdm templates 3.6.0 against BIG-IP 15.1.0.2 and autoscale works now!
Do you already have an issue opened with F5 support?
Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open an case with F5 if this is a critical issue.
Description
Autoscale template does not place BIG-IP devices in cluster. It fails onboarding of the autoscale script. The devices end up as standalone.
YAML used...
Error in logs
Template
https://github.com/F5Networks/f5-google-gdm-templates/tree/master/experimental/autoscale/waf/via-lb/existing-stack/payg
Severity Level
3