From a5c64200358194a4767555370de775c18c0c9d04 Mon Sep 17 00:00:00 2001 From: Jan Provaznik Date: Wed, 30 Sep 2015 13:07:45 +0200 Subject: [PATCH] Add a doc note about updating changed templates Documents how to update an existing overcloud after new heat templates have been installed. Change-Id: I02c0610aca1cf7ac303a487326844d275b0ff1a6 Related-To: 1501296 --- doc/source/installation/updating.rst | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/doc/source/installation/updating.rst b/doc/source/installation/updating.rst index a892156b..461655ba 100644 --- a/doc/source/installation/updating.rst +++ b/doc/source/installation/updating.rst @@ -16,4 +16,24 @@ You can upgrade any packages that are installed on the undercloud machine. # You can specify the package names to update as options in the yum update command. -You do not need to restart any services after you update. + .. note:: + + You do not need to restart any services after you update. + +#. Update stack environment of the existing overcloud: + + If you use heat templates from default location + (`/usr/share/openstack-tripleo-heat-templates`), it's possible that these + templates have changed when updating undercloud machine. You should update + the existing overcloud to reflect any changes in template and environment + files. The reason is that CLI commands which change existing overcloud pass + new template to Heat but reuse existing environment of the overcloud so a + new resource type referenced in updated template might be missing in the + existing environment:: + + openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e + + .. note:: + + Make sure you pass all environment files you used when deploying + overcloud.