Closed chen23 closed 3 years ago
Is this issue affected at all by your recent Service Discovery Worker merge request?
This is less of an issue (takes less time to initialize service discovery). I would consider this close(able), but still technically an issue, but not worth fixing IMHO.
Environment
Summary
When using service discovery the task to create service discovery is made before the AS3 declaration has completed. This can cause errors in service discovery where the partition has not been created yet.
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration:
Observe the following error response:
Tue, 18 Aug 2020 23:50:22 GMT - fine: [f5-service-discovery: Task.js] Error: Command failed: tmsh -a create ltm node /AS3Demo/consul-192.168.128.3-private address 192.168.128.3 metadata replace-all-with { appsvcs-discovery { } } 01070734:3: Configuration error: Can't associate Node (/AS3Demo/consul-192.168.128.3-private) folder does not exist
Tue, 18 Aug 2020 23:50:22 GMT - fine: [f5-service-discovery: restWorkerTask.js] service discovery task succeeded Tue, 18 Aug 2020 23:50:22 GMT - fine: [appsvcs] {"message":"generating tmsh commands and pre-script iControlRest calls","level":"debug"} Tue, 18 Aug 2020 23:50:22 GMT - fine: [appsvcs] {"message":"getting whitelist","level":"debug"} Tue, 18 Aug 2020 23:50:22 GMT - fine: [appsvcs] {"message":"setting whitelist","level":"debug"} Tue, 18 Aug 2020 23:50:22 GMT - fine: [appsvcs] {"message":"executing pre-script iControl calls","level":"debug"} Tue, 18 Aug 2020 23:50:22 GMT - fine: [appsvcs] {"message":"Executing pre-script time: 0 milliseconds","level":"debug"}