-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.6
-
False
-
-
False
When customers have large environments, sometimes the gateway container delay to start and the systemd task fails, requiring restarts to have it up and running.
TASK [ansible.containerized_installer.automationgateway : Manage automation gateway containers via systemd] ******************************************** ok: [gatewaya.lab.local] => (item=automation-gateway.service) FAILED - RETRYING: [gatewayb.lab.local]: Manage automation gateway containers via systemd (3 retries left). FAILED - RETRYING: [gatewaya.lab.local]: Manage automation gateway containers via systemd (3 retries left). ok: [gatewaya.lab.local] => (item=automation-gateway-proxy.service) ok: [gatewayb.lab.local] => (item=automation-gateway.service) FAILED - RETRYING: [gatewayb.lab.local]: Manage automation gateway containers via systemd (3 retries left). ok: [gatewayb.lab.local] => (item=automation-gateway-proxy.service)