Closed janisz closed 7 years ago
This happens when you deployed service and then update it with different number of ports but you stopped deployment or you deployment has not finished yet.
Below are the steps to reproduce it:
Can service be processed anyway, despite the inconsistency between app definition and running task? Totally 'ignoring' such cases may not be the best idea.
I concur. If port counts differs between task and app we can check version and if it differs to we can skip registration of whole task. This approach could work but does not prevent situation when port definitions totally changed but port counts stays the same.
Changes Unknown when pulling 25f46ce585c7bfe322a27eb39091d2185ad600a5 on bugfix/#164/check_ports_bounds into on master.