When deployed in a large bundle with multiple charms related to it (like the Charmed Kubeflow bundle), istio-pilot may skip the method that sends gateway-info to remote units and/or the handler for the default gateway, which causes the following:
1) If the handle_default_gateway is not called, the default-gateway never gets created.
2) If the handle_gateway_info_relation is not called, related remove units will never get the gateway info, which prevents them to complete their start up.
Note that even though this is wrong behaviour, istio-pilot will not fail.
Workarounds
For 1): juju run --unit istio-pilot/0 -- "export JUJU_DISPATCH_PATH=hooks/config-changed; ./dispatch"
For 2) This behaviour should be corrected by this change
Behaviour
When deployed in a large bundle with multiple charms related to it (like the Charmed Kubeflow bundle), istio-pilot may skip the method that sends
gateway-info
to remote units and/or the handler for the default gateway, which causes the following:1) If the
handle_default_gateway
is not called, thedefault-gateway
never gets created. 2) If thehandle_gateway_info_relation
is not called, related remove units will never get the gateway info, which prevents them to complete their start up.Note that even though this is wrong behaviour, istio-pilot will not fail.
Workarounds
For 1):
juju run --unit istio-pilot/0 -- "export JUJU_DISPATCH_PATH=hooks/config-changed; ./dispatch"
For 2) This behaviour should be corrected by this change