Open dskachan opened 5 years ago
@dskachan Hey, has this been solved yet?
I think the basic handling is missing here for serviceset on CLI.
I confirm this problem in the actual master with the commit 4f959572f2ad210493602552fce961a8db806be3
I did not find any way to add/delete a service to a service set using serviceset option after icingacli director command, for example icingacli director serviceset test-set set service load
I used service as an option, like @dskachan did, and I confirm his observation. The director will add the service to a serviceset, but he will delete the service template and convert it to apply rule. If this is not the wanted way to add service/s to a serviceset the director should stop this manipulation and another way should be available.
Here is what happen:
icingacli director service set load --service_set test-set
ref/NC/735167
Expected Behavior
Service is added to a service set
Current Behavior
icingacli returns
Service 'apt_t' has been modified
, and afterwards in icinga2 director WUI, a service with nameapt_t
isn't displayed correctly. I see instead:Possible Solution
I do not know whether it is designed to make it possible to assign a service to a service set over CLI, but if no, I would not expect that cli will change anything in the database and write an error message. If it could be done in some way, I'm kindly asking to provide a way how to do so.
Steps to Reproduce (for bugs)
first create a serviceset:
create a serviece template:
assign the service to the serviceset
That is the place where the bug comes. I understand that this is most likely abuse of the function. But as it gives me the correct result and makes the service unusable - something went wrong. I haven't found a list of keys might be used, so, I just took this one form director database.
Your Environment
icinga2 --version
): r2.10.2-1