When I try to clone an existing service in a Stack which have two sheduling rules like this for example :
The host must have a host label of env = test
The host must have a host label of datacenter = aws
the sheduling tab of my clone looks like this :
It only clones the first condition and concat the next rules in the value.
Can you reproduce this? FYI I’am running the 1.1.3 rancher version.
You need individual rules for each host label that you want to schedule against.
It’s that I have on my original container. I have :
1- The host must have a host label of env = test
2- The host must have a host label of datacenter = aws
I have one rule for my host label env and my host label datacenter.
The screen capture I have pasted is after cloning my original container with my 2 rules. The result is messy. The cloning operation did not copy my two rules properly.
This is the way the rules are actually stored since labels are a map and can’t have duplicate keys. The UI used to split the label values on comma to make them appear separate but that was breaking something else. So it should still do that, but only for scheduler labels.
Ok, if I understand what you are syaing, this problem is only a UI problem. So when I upgrade a container and if I validate this upgrade without cleaning the scheduling labels mess, it will work as expected?