Guest agent fails if it can't resolve it's own hostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Expired
|
Medium
|
Unassigned |
Bug Description
When using heat to build instances heat will create an instance in nova with some large random hostname.
After taskmanager creates the instance then it creates a record in designate, this hostname is different that the hostname assigned to the instance.
Trove guest agent will fail with:
2014-03-28 03:16:11.079 2590 INFO trove.guestagen
2014-03-28 03:16:11.080 2590 DEBUG trove.openstack
2014-03-28 03:16:11.111 2590 ERROR trove.guestagen
2014-03-28 03:16:11.112 2590 ERROR trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
2014-03-28 03:16:11.112 2590 TRACE trove.openstack
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in trove: | |
assignee: | Sushil Kumar (sushil-kumar2) → nobody |
status: | In Progress → Incomplete |
Hi Sam
2 things,
1. Is this problem still on.
2. it would be helpfull, if you can please provide an example name which gets registered on dns in your case