could you provide your steps (jobs, blcli commands, etc.) that you use to set this property and some other property what works for comparison?
I know this is not the question you are asking but is it not easier to use repeater routing rules to define which repeater to use based on property conditions?
I'm not familiar with repeater routing rules. If there is a better way we can do this, I'm all ears. This is the only way I know of doing it currently (by setting REPEATER_NAME and then telling jobs to stage using repeater). However, if there is another trick I'm all for it.
However, it still seems that REPEATER_NAME should get set when I tell the Provisioning job to use the Server Property Instance. I don't understand why that field won't take.
Open infrastructure manager
Add a repeater (as you should already have done)
Create a new repeater routing rule based on a condition that you define, which could for example be a SERVER class property, and assign the correct repeater to that rule. All jobs will target the correct repeater beased on the conditions specified.
what scott is suggesting is to use a rule like 'TARGET.IP_ADDRESS starts with 123.123.' or something like that instead of using the 'REPEATER_NAME=blah
also - i'm not sure what you are showing - in one example the repeater name is a hostname, in the rule it's 'Dallas' ?
are there other properties in the server class you are trying to set that are of type PSC that are not setting via provisioning?
what version of blade is this ?
I'm work with Robert on this as well and the version of Blade is 8.2 We were able to set other properties like CUSTOMER and during the provisioning process that property takes the value we set. However it seems like when we attempt to set the REPEATER_NAME and set it the value after the server is provisioned is still blank. We tried several things and it keeps coming up blank.