This bug was initially created as a copy of Bug #1879531
I am copying this bug because:
This affects all versions after 13, including 16.1. If a user is reusing tags, the containers are not fetched and not rebuilt using updated images.
Description of problem:
Customer performed minor update from RHOSP13z11 to 13z12. The update went successfull, but it was observed that some of the container's images were not pulled correctly.
Version-Release number of selected component (if applicable):
Satellite 6.x is used as image registry
- Container images are prepared with the tag 'latest'.
- Minor update from 13z11 to 13z12 is performed.
Steps to Reproduce:
Latest image is not pulled during update for some of the containers
we Identified 2 container in existing customer setup.
It is expected that all the containers should be updated to the latest images present in satellite content view.
- Same satellite content view is used when scale-out of new compute is done and it is observed that newly scaled out computes having containers with latest packages in them.
- Manually doing the docker pull with tag 'latest' is pulling the latest image for those containers but it seems that it is not happening during minor update.
[root@com003 ~]# docker pull satellite.deployment.be:5000/cloud-oscar05-pxs_osp13-osp13_containers-neutron-openvswitch-agent:latest
Trying to pull repository satellite.deployment.be:5000/cloud-oscar05-pxs_osp13-osp13_containers-neutron-openvswitch-agent ...
latest: Pulling from satellite.deployment.be:5000/cloud-oscar05-pxs_osp13-osp13_containers-neutron-openvswitch-agent
Status: Image is up to date for satellite.deployment.be:5000/cloud-oscar05-pxs_osp13-osp13_containers-neutron-openvswitch-agent:latest
*** Bug 1913039 has been marked as a duplicate of this bug. ***
Followed https://docs.google.com/document/d/1UB3s_U0_Cy-FRfbgYHKbMX9BWrtGn4-zsVCmAM1C7yY/edit doc
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat OpenStack Platform 16.1.4 director bug fix advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.