Rancher 1.6 cannot stop services or have start_once

1

We’ve just moved all our containers from an old instance of Rancher to 1.6.14 and upgraded to 1.6.21.

We have unusual behaviour in that we can’t stop services. When we stop them in the UI they get immediately restarted. This is causing issues with some of our containers running under rancher-cron in that they’re continuously being re-run instead of waiting for the prod from rancher-cron.

Any ideas why?

2

Oddly I redeployed these services this morning and now Rancher is correctly honouring the start_once label.

Unfortunately I have to now report this as not able to replicate.