Rudder

Hi Denis, this is interesting.

The check is actually done node by node, and only check that on any given node, all the directive are derived from the same version of technique.

For example, you could have:
- node1 => [directive1_0 from tech1-v1 ; directive1_1 from tech1-v1]
- node2 => [directive2_0 from tech1-v2 ]

This is the only (HUGE - we are aware of it) limitation on technique version.

I'm going to try to reproduce. If you have a way to reproduce, that would be very helpful.

In all case, we have to make that message clearer, and add log to help analyse the problem.

Say you have 4 directives, dir1, dir2 dir3 and dir4:

dir1 and dir2 => group: servers
dir3 and dir4 => group: desktops

Then you migrate only dir1 and dir2 and you'll get the error. Basicly you need to migrate all directives of the same type or the error occurs.

I just tested with Rudder (3.0.1) and it possible to have a directive (checkGenericFileContent in my case) with:

- version 6 applied to group 1 (with node 1 into it),
- version 7 applied to group 2 (with node 2 into it).

So perhaps you have some overlap in the groups...

Could you check that, it would be very helpful: I don't want to overlook a bug because I wasn't able to reproduce it.

But in all case, the error message should say explicitly what is the problem ("node 1 has the following rules applying diffent version of technique XXX: [rule1, rule2, ...]; node 2 etc).