Red Hat Bugzilla – Bug 1309084
[Docs] [Director] Document for update 7.x to 7.3
Last modified: 2016-04-13 00:53:24 EDT
We need to track adding the following BZs to the update documentation:
(1) https://bugzilla.redhat.com/show_bug.cgi?id=1307125 - heat-engine crash ( workaround with docs)
(2) https://bugzilla.redhat.com/show_bug.cgi?id=1308702 ( RPC_Timeout is not 600 ( workaround with docs)
Version-Release number of selected component (if applicable):
Assigning to Dan for review.
Link here: http://file.bne.redhat.com/~dmacpher/OpenStack/7.3/Director/#chap-Updating_the_Environment
Under section 9.1.
After the package update, make sure all OpenStack services are running properly on the director. Check the ironic-api and ironic-discoverd services are running. If not, please start them:
$ sudo systemctl restart openstack-ironic-api openstack-ironic-discoverd
Likewise, heat-engine on the Undercloud can fail to start if its database is unavailable. If this occurs, restart heat-engine manually after the update:
$ sudo systemctl start openstack-heat-engine.service
If upgrading from OpenStack Platform director 7.2 to OpenStack Platform director 7.3 or greater:
Heat on the Undercloud requires an increase in the RPC response timeout to accomodate a known issue (see BZ#1305947). Edit the /etc/heat/heat.conf and set the following parameter:
Then restart all Heat services:
$ systemctl restart openstack-heat-api.service
$ systemctl restart openstack-heat-api-cfn.service
$ systemctl restart openstack-heat-engine.service
We don't re-run Puppet after upgrading the undercloud, so if the undercloud was originally installed with a version of openstack-puppet-modules that exhibited bug 1305947 (i.e. 7.2), it will NOT be fixed after upgrading to 7.3 and the user will still have to apply the second workaround above.
The first workaround should not actually be needed with respect to heat-engine though, because we included a fix for bug 1307125 in 7.3.
Actually, the build that fixed bug 1307125 may not be in 7.3 after all; it seems to still be ON_QA.
Sasha, based on Zane's comments, it looks like we'll be keeping both workarounds in the docs. Do you know if there's anything else required for this BZ?
Nothing else is required for the bz.
The doc looks OK.
This content is now live on the Customer Portal.