Back to bug 1009180
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dan Smith | 2013-09-17 22:22:36 UTC | Status | NEW | POST |
| Assignee | rhos-maint | ndipanov | ||
| Dan Smith | 2013-09-17 22:26:17 UTC | Target Release | --- | 4.0 |
| Target Milestone | --- | rc | ||
| Perry Myers | 2013-09-18 10:59:19 UTC | Priority | unspecified | medium |
| CC | pmyers | |||
| Xavier Queralt | 2013-10-03 14:58:41 UTC | Status | POST | MODIFIED |
| CC | xqueralt | |||
| Fixed In Version | openstack-nova-2013.2-0.23.rc1.el6 | |||
| errata-xmlrpc | 2013-10-28 19:14:44 UTC | Status | MODIFIED | ON_QA |
| Ami Jeain | 2013-12-02 14:57:13 UTC | Status | ON_QA | VERIFIED |
| Don Domingo | 2013-12-10 02:42:08 UTC | CC | dansmith, ddomingo | |
| Flags | needinfo?(dansmith) | |||
| Dan Smith | 2013-12-10 14:56:44 UTC | Doc Text | Cause: Nova would change the hostname it reports to the controller at runtime if the hostname on the underlying system was changed. Consequence: The controller would create a new record for the host and the old record would become stale. Fix: Nova will no longer report a hostname change at runtime. Result: A node's hostname will not change during runtime and a restart of the compute service will be required before such a change is communicated to the controller. | |
| Flags | needinfo?(dansmith) | |||
| Don Domingo | 2013-12-11 04:48:36 UTC | Doc Text | Cause: Nova would change the hostname it reports to the controller at runtime if the hostname on the underlying system was changed. Consequence: The controller would create a new record for the host and the old record would become stale. Fix: Nova will no longer report a hostname change at runtime. Result: A node's hostname will not change during runtime and a restart of the compute service will be required before such a change is communicated to the controller. | Previously, updating a node's hostname while nova-compute was running on it changed the hostname that nova-compute reported to the controller as well. Whenever this occurred, the controller created a new record for the host, leaving the old record to go stale. With this release, nova-compute will no longer report changes to the node's hostname during runtime. Rather, nova-compute will simply log the hostname change; the node will not use the new hostname until nova-compute is restarted. |
| Don Domingo | 2013-12-11 23:47:09 UTC | Doc Text | Previously, updating a node's hostname while nova-compute was running on it changed the hostname that nova-compute reported to the controller as well. Whenever this occurred, the controller created a new record for the host, leaving the old record to go stale. With this release, nova-compute will no longer report changes to the node's hostname during runtime. Rather, nova-compute will simply log the hostname change; the node will not use the new hostname until nova-compute is restarted. | Previously, updating a node's hostname while openstack-nova-compute was running on it changed the hostname that nova-compute reported to the controller as well. Whenever this occurred, the controller created a new record for the host, leaving the old record to go stale. With this release, openstack-nova-compute will no longer report changes to the node's hostname during runtime. Rather, nova-compute will simply log the hostname change; the node will not use the new hostname until openstack-nova-compute is restarted. |
| errata-xmlrpc | 2013-12-19 17:29:16 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-20 00:24:26 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-19 19:24:26 UTC | |||
| John Skeoch | 2016-04-22 05:02:42 UTC | CC | eglynn | |
| Perry Myers | 2016-04-26 18:40:35 UTC | CC | pmyers | |
| Russell Bryant | 2019-09-09 14:26:50 UTC | CC | rbryant |
Back to bug 1009180