We are having a strange issue here. If we manually launch a catalog entry, everything starts up just fine. However, if we use an api call to launch the same catalog entry, rancher fails to start the instance.
We have compared the rancherCompose string and they are identical (as expected) and the answers to the questions are the same.
The catalog config has this:
.catalog:
name: "Dashboard"
[snip]
mongo-data:
scale: 1
dashboard:
scale: 1
health_check:
port: 3000
interval: 2000
initializing_timeout: 100000
unhealthy_threshold: 3
strategy: none
response_timeout: 2000
healthy_threshold: 2
mongo:
scale: 1
After starting up, the manual service has this as the rancherCompose.yml config:
mongo-data:
scale: 1
dashboard:
scale: 1
health_check:
port: 3000
interval: 2000
initializing_timeout: 100000
unhealthy_threshold: 3
strategy: none
response_timeout: 2000
healthy_threshold: 2
mongo:
scale: 1
but the api-created instance has only this
mongo-data:
scale: 1
dashboard:
scale: 1
mongo:
scale: 1
so the health_check section is missing
Does anyone have a clue why this is happening ? There is only 1 version of the application in the template repo
Thanks!