Back to bug 1308702
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Zane Bitter | 2016-02-15 19:33:36 UTC | CC | zbitter | |
| Zane Bitter | 2016-02-15 20:20:06 UTC | Doc Text | Cause: The RPC response timeout for communication between the heat-api and heat-engine processes is supposed to be increased from the default value in a director undercloud. However, due to https://bugzilla.redhat.com/show_bug.cgi?id=1305947 this configuration change is missing on underclouds originally installed with director 7.2. Consequence: Heat stack operations on the undercloud may fail with a MessagingTimeout error. Workaround (if any): In the file /etc/heat/heat.conf on the undercloud, change the line: #rpc_response_timeout=60 to rpc_response_timeout=600 (i.e. remove the initial # to uncomment it, and change the value from 60 to 600.) Then restart the heat services: systemctl restart openstack-heat-api.service systemctl restart openstack-heat-api-cfn.service systemctl restart openstack-heat-engine.service Result: Heat will be running using the correct timeouts. | |
| Doc Type | Bug Fix | Known Issue | ||
| Zane Bitter | 2016-02-15 20:21:57 UTC | Summary | rpc_response_timeout not set in undercloud heat.conf when upgrading to 7.3 | rpc_response_timeout not set in undercloud heat.conf when upgrading to 7.3 from 7.2 |
| Angus Thomas | 2016-02-15 21:02:00 UTC | Target Release | --- | 7.0 |
| Target Milestone | --- | y3 | ||
| Angus Thomas | 2016-02-15 21:15:08 UTC | Status | NEW | CLOSED |
| Resolution | --- | NOTABUG | ||
| Last Closed | 2016-02-15 16:15:08 UTC | |||
| John Skeoch | 2016-04-18 07:11:43 UTC | CC | srevivo |
Back to bug 1308702