In the list of involved nodes, drop "no secondary"
In the list of involved nodes, drop "no secondary"

When grouping moves into jobs, a new job set is started, if the new
move involves a node also touched by a previous move. When computing
the list of involved nodes, the new primary and secondary nodes of the
instance are included; if an instance, however, has only one node, the
"no secondary" index -1 should be left out to avoid spurious conflicts
between unrelated moves of single-homed instances.

Signed-off-by: Klaus Aehlig <4ce51de36d9068cd7db2eec1151e0f3f95419008@google.com>
Reviewed-by: Hrvoje Ribicic <be5828fca31f89218048bec4189e30a581aa65da@google.com>

yiannist/ganeti,mbakke/ganeti,apyrgio/ganeti,bitemyapp/ganeti,andir/ganeti,bitemyapp/ganeti,apyrgio/ganeti,onponomarev/ganeti,leshchevds/ganeti,leshchevds/ganeti,ganeti/ganeti,yiannist/ganeti,grnet/snf-ganeti,andir/ganeti,dimara/ganeti,yiannist/ganeti,mbakke/ganeti,ganeti-github-testing/ganeti-test-1,ganeti-github-testing/ganeti-test-1,ganeti/ganeti,ganeti/ganeti,dimara/ganeti,andir/ganeti,mbakke/ganeti,onponomarev/ganeti,grnet/snf-ganeti,leshchevds/ganeti