Comment 3 for bug 1053597

here is is with device_Id.

| dhcp80a81c5c-6cb9-5124-b268-7d352d654d3c-68fbbf41-ff2f-4bf3-a850-369518cb6d3b | network:dhcp | {"subnet_id": "c37d9f81-eede-4ac6-9397-d10c240a3d11", "ip_address": "60.0.0.2"} |
| dhcpfba529fc-becd-5f63-b6f3-2f92fed6a2b7-68fbbf41-ff2f-4bf3-a850-369518cb6d3b | network:dhcp | {"subnet_id": "c37d9f81-eede-4ac6-9397-d10c240a3d11", "ip_address": "60.0.0.4"} |

Looking at the code, I see that device_id is generated based on DNS name. I changed the DNS name of the host after running the dhcp agent, so I guess that explains it. I'll close this bug. I was really just making sure there was not a serious bug here, and the change of DNS name seems to explain it.