Comment 10 for bug 1418921

Let me provide node state from last snapshot

id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|------------------|---------|------------|-------------------|---------------------------|---------------|--------|---------
10 | discover | Untitled (bc:10) | None | 10.20.0.9 | 52:54:d0:15:bc:10 | | | True | None
8 | error | Untitled (1b:e9) | 7 | 10.20.0.6 | fe:23:39:ec:9a:4d | controller | | True | 7
9 | discover | Untitled (c7:5e) | None | 10.20.0.11 | 52:54:47:7f:c7:5e | | | True | None
7 | error | Untitled (f0:fb) | 7 | 10.20.0.9 | 5e:6a:b2:5c:03:46 | ceph-osd, cinder, compute | | True | 7

And It is clear that nailgun assigned different ips for each created cobbler system, 0.8 and 0.10 - this is correct and expected behavior.
But it seems they failed to provison and get this new ips, that is why db state stuck in 0.6 and 0.9.
Unfortunately there is no logs at all apart from db and cobbler rpc info - so it is still unclear what was the reason that provisioning failed.