-
Notifications
You must be signed in to change notification settings - Fork 1
GCP: Failover is broken when dst is 'ANY' in a VS #25
Comments
Can you change the logging level to silly via the instructions on this page and then post your output again? |
Please find the output below after changing log level to silly. Tue, 07 Apr 2020 17:54:48 GMT - fine: [f5-cloud-failover] HTTP Request - POST /trigger |
Thanks for reaching out to us with with your issue. This is a bug and I've filed a bug ticket, internal ID AUTOSDK-275, to get this fixed. |
Closing this issue As of release CFE 1.2 we moved this CFE repo under F5Networks. Your issue was recreated there. To follow-up on this issue visit: |
We have multiple VS in our configuration with few VS having destination as 'ANY'(0.0.0.0/0).
VS with dst 'ANY' is used for source NAT.
When we trigger a failover, it is failing because of VS with dst as 'ANY'. We would have expect it to skip this VS for failover.
Error log:
Mon, 06 Apr 2020 04:17:41 GMT - info: [f5-cloud-failover] Performing failover - execute
Mon, 06 Apr 2020 04:17:41 GMT - info: [f5-cloud-failover] Performing Failover - discovery
Mon, 06 Apr 2020 04:17:42 GMT - severe: [f5-cloud-failover] failover.execute() error: ipaddr: the address has neither IPv6 nor IPv4 format Error: ipaddr: the address has neither IPv6 nor IPv4 format
at Object.ipaddr.parse (/var/config/rest/iapps/f5-cloud-failover/node_modules/ipaddr.js/lib/ipaddr.js:632:13)
at ipsFilter.forEach (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:516:51)
at Array.forEach ()
at ips.forEach (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:512:23)
at Array.forEach ()
at Cloud._matchIps (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:505:13)
at vm.networkInterfaces.forEach (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:640:51)
at Array.forEach ()
at theirVms.forEach (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:636:34)
at Array.forEach ()
at Cloud._discoverNicOperations (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:634:18)
at Cloud._discoverAddressOperations (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:590:18)
at _getVmsByTags.then (/var/config/rest/iapps/f5-cloud-failover/nodejs/providers/gcp/cloud.js:173:33)
at tryCatcher (/usr/share/rest/node/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:693:18)
at Promise._fulfill (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:638:18)
at Promise._settlePromise (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:582:21)
at Promise._settlePromise0 (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/usr/share/rest/node/node_modules/bluebird/js/release/promise.js:693:18)
The text was updated successfully, but these errors were encountered: