Comment 7 for bug 1491725

Folks, we catch same issue :
I don't know how-to reproduce it, but its related to cobbler system and fuel nodes:
 id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|------------------|---------|---------------|-------------------|-------|-------------------|--------|---------
18 | discover | Untitled (42:94) | 5 | 192.168.5.110 | ec:f4:bb:cd:42:94 | | cinder, compute | True | 5
19 | discover | Untitled (43:00) | 5 | 192.168.5.112 | ec:f4:bb:cd:43:00 | | cinder, compute | True | 5
16 | discover | Untitled (45:54) | 5 | 192.168.5.113 | ec:f4:bb:cd:45:54 | | controller, mongo | True | 5
17 | discover | Untitled (41:20) | 5 | 192.168.5.111 | ec:f4:bb:cd:41:20 | | controller, mongo | True | 5
12 | discover | Untitled (45:4c) | 5 | 192.168.5.114 | ec:f4:bb:cd:45:4c | | controller, mongo | True | 5
[root@fueldc209hw bootstrap]# cobbler system list
 default
 node-11
 node-12
 node-13
 node-14
 node-15
 node-16
 node-17
 node-18
 node-19
##
But nodes count was always static - 5
I guess, its related to some action, which "delete nodes" , but after node re-discovered - it catch +1 to their id.
Work-around :
cobbler system remove --name ${old_node-id}
cobbler sync