Wrong namespace in example task manifests

[lmroz]

Each example task manifest refers to /intel/dummy in collector's config section. That results in following error (this one is for psutil) when trying to run these tasks:

Policy defined for metric, ([psutil load load1]) version (0), but no config defined in manifest
Policy defined for metric, ([psutil load load15]) version (0), but no config defined in manifest
Policy defined for metric, ([psutil load load5]) version (0), but no config defined in manifest
Policy defined for metric, ([psutil net all bytes_recv]) version (0), but no config defined in manifest
Policy defined for metric, ([psutil net all bytes_sent]) version (0), but no config defined in manifest

[geauxvirtual]

Can you specify which example you are trying to run?

[geauxvirtual]

Marking this as a bug. There is no Policy defined for these metrics per the plugin, so it should not matter what's in the config section of the example task, even though the example task shouldn't specify a config for a metric that is not being collected.

[geauxvirtual]

https://github.com/intelsdi-x/pulse/blob/master/control/plugin/cpolicy/tree.go#L135-L137

Looks like the issue is here. We recently fixed a bug where we were not validating a config against a policy defined by a plugin if no config was present (#380). However, looking at the code above, we do not set Policy to nil if the metric is not found in the ConfigPolicy for the plugin, we just create an empty ConfigPolicyNode and store it in the metric's policy. Checking if policy is nil will not work in this case.