openstack/tripleo-docs
Code Issues Proposed changes

Add a note about verifying container images after hotfix

Browse Source 
Add a paragraph that explains why it's important to check that the
patched images have the right rpm version or it can lead to problems
when testing the component later.

Change-Id: Ifef628bb255529083383b372ea58466b3d085116
Co-Authored-By: Assaf Muller <amuller@redhat.com>
This commit is contained in:
Emilien Macchi 2020-09-09 15:40:55 -04:00
parent 4ae12630aa
commit bf90c44ccd
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
deploy-guide/source/deployment/container_image_prepare.rst
View File

@ -516,3 +516,18 @@ where it's needed. Two ways are supported:
* (Short but not persistent after a minor update): Run Paunch or Ansible
to update the container on a host. The procedure is already documented
in the :doc:`./tips_tricks` manual.
Once the hotfixed container image has been deployed, it's very important to
check that the container is running with the right rpm version.
For example, if the nova-compute container was updated with a new hotfix image,
we want to check that the right nova-compute rpm is installed:
.. code-block:: shell
sudo podman exec -ti -u root nova_compute rpm -qa | grep nova-compute
It will return the version of the openstack-nova-compute rpm and we can compare
it with the one that was delivered via rpm. If the version is not correct (e.g.
older), it means that the hotfix image is wrong and doesn't contain the rpm
provided to build the new image. The image has to be rebuilt and redeployed.