-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cannot read property name of undefined fwdRules.forEach #26
Comments
I removed the virtual server IP that matched the forwarding rule from my BIG-IP configs and tested failover again. This way, the forwarding IP should NOT match...and therefore the script should NOT fail. Sure enough, I have success. My workaround...
Why are forwarding rules causing a problem? |
This was my own fault. I forgot to have my terraform plan create TWO target instances: one containing each BIG-IP. I only had ONE target instance which caused the 'name' undefined error. Suggest that better logging be added to the code to better defined this type of error. for reference :)
|
Thanks for suggesting this improvement to our logging. We are now tracking this logging enhancement request with internal issue ID AUTOSDK-362. |
Closing. This enhancement was included with Release 1.7. |
Hitting an error when performing failover in GCP. I stood up my environment with terraform, proper labels, pre-reqs, etc. I installed CFE and the POST declaration is 200 OK. I perform a failover, but items are not moving. Routes do not move, alias IPs do not move, and forwarding rules are not moving. It appears from the restnoded logs that the forwarding rule logic is causing issues.
specific error from unit 1...
Full Logs
unit 1 during failover to become active...
unit 2 during failover to become active...
The text was updated successfully, but these errors were encountered: