[rudder-users] unexpected "unexpected" result

[tim taler]

Hi Nicolas

EXCELLENT! thanks for your answer, your suggested workaround works
perfectly for this task.
Thanks also for identifying the underlying issue and filing a ticket for it.

So far I'm quite impressed with rudder, it surely helps keeping the
policies readable and in coherent style.

Congratulation to this tool (wished I had found it earlier ;-) and
thanks to you guys for offering
the free open-source version!
I hope to be able to start testing the subscription version in a
couple of weeks for a customer who signaled his interest.
Especially the "Audit and Compliance" elements shall be interesting.

thanks again and
best regards

On Tue, Nov 5, 2019 at 11:36 AM Nicolas Charles
<nicolas.charles at rudder.io> wrote:
>
> Hi Tim,
>
> Thank you for the detailed error report, I've been able to reproduce, and this is a bug in the evaluation of reports send by the agent.
>
> When we use iterator in generic method, the Rudder server has no way to know evaluation which element will be in the iterator (except for the easy use case), so we have an option to automatically accept multiple reports from generic method when we have a variable in a component (parameter "Unbounded reports by elements when a variable is used" in the Setting page)
>
> However, when it's only the condition which uses an iterator, as it is in your use case, we don't store this information, and don't aggregate the result of multiple reports from a given generic method - hence the "unexpected" reporting.
>
> Note that the "-" in the comment is expected, it is only the reporting that shows what was the condition used; when used as a class it is correctly canonified.
>
>
> As a workaround, you can define a variable string "grafana.service_name" with value "grafana", and in the service_restart generic method use ${grafana.service_name}; this will allows the reports aggregation.
>
> I've opened issue https://issues.rudder.io/issues/16105 to correct this within Rudder,
>
>
> Thank you very much for your message, and sorry you had a bad experience
>
> Nicolas CHARLES
>
> On 04/11/2019 20:22, tim taler wrote:
>
> Hi all
> I'm new to rudder, and ran into an unexpected problem.
>
> As an example I like to install grafana and some plugins.
> For the plugins I created a list-variable over which a command promise
> can iterate with grafana-cli to install the plugins.
>
> After a plugin installation grafana needs to be restarted though, so
> I tried to use the "repaired" class from the command promise to
> trigger a service restart.
>
> the compliance report but stays on:
> "[Unexpected] Service restart grafana-server if
> any.(command_execution__usr_sbin_grafana_cli_plugins_grafana-piechart-panel_repaired)
> was not applicable"
>
> As you might notice the plugins from the list contain "-" which AFAIK
> are illegal for a class name - is there any easy way to canonicalize
> them?
>
> TIA
>
> _______________________________________________
> rudder-users mailing list
> FAQ: https://faq.rudder.io/
> Bug Tracker: https://issues.rudder.io/
> rudder-users at lists.rudder-project.org
> https://www.rudder-project.org/mailman/listinfo/rudder-users