How can we adapt RHOSP13 deployment to Red Hat Satellite 6.10+ ?

Environment

• Red Hat OpenStack Platform 13
• Red Hat Satellite 6.10+

Issue

• Red Hat Satellite was upgraded from an older version (eg. 6.8) to 6.10+.
• What are the required steps to adapt existing RHOSP13 deployment to the upgraded Satellite server ?

Resolution

• Enable unauthenticated container
  Select “Lifecycle Environments” -> “Library” -> “Details” and set “Unauthenticated Pull” to Yes.

• Regenerate overcloud_images.yaml and use the updated environment file in the subsequent openstack overcloud .. commands.
  Note: :5000 in --namespace option should be removed so that tcp/443 is used instead of tcp/5000

  $ openstack overcloud image prepare --namespace <satellite host> ...
  

• Check the generated overcloud_images.yaml file to find the updated image names, which do NOT include :5000

• Before updating the deployment, tag all container images with the pcmklatest tag to remove :5000 from the image names, following the example below.

  • This step should be executed in all controller nodes.

  $ sudo docker tag <satellite host>:5000/<organization>-<product>_rabbitmq:pcmklatest <satellite host>/<organization>-<product>_rabbitmq:pcmklatest
  

• Update all bundle resources in pacemaker to use the new container image without :5000, following the example below.

  • These steps should be executed in one controller node

  $ sudo pcs resource unmanage rabbitmq-bundle
  $ sudo pcs resource bundle update rabbitmq-bundle container image="<satellite host>/<organization>-<product>_rabbitmq:pcmklatest"
  $ sudo pcs resource refresh rabbitmq-bundle
  $ sudo pcs resource manage rabbitmq-bundle
  

Root Cause

• Satellite 6.10+ no longer provides container registry feature at tcp/5000 and the registry now listens to tcp/443 instead.
  • Also see this solution for RHOSP16.x
• The container registry at tcp/443 requires authentication by default, which can be disabled by the config option
• There is This content is not included.a known issue with minor update in RHOSP13, and change in container image names are not properly handled during minor update.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.