Bug 2076901

Summary: assisted-service pin-latest.py script should exclude the postgres image
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Omer Tuchfeld <otuchfel>
Component: Infrastructure OperatorAssignee: Omer Tuchfeld <otuchfel>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact: Derek <dcadzow>
Priority: unspecified    
Version: rhacm-2.6CC: cbynum, ccrum, mfilanov, trwest, vkolodny, yfirst
Target Milestone: ---Flags: cbynum: rhacm-2.6+
cbynum: rhacm-2.6.z+
Target Release: rhacm-2.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-06 22:30:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2076998    

Description Omer Tuchfeld 2022-04-20 08:03:46 UTC 
Description of the problem:
The pin-latest.py script should only perform pinning for image manifest tags
that are also pointed at by another persistent, unmoving tag. This is because
otherwise the sha we pin to may get garbage collected. This is not a problem
for assisted components because we have such persistent tag. But recently we
moved to using the postgres image from a quay organization outside of our
control. That organization doesn't not have a persistent tag for every manifest
the `:latest` tag happened to be on, so we can not do pinning for the postgres
image. Pinning postgres is not too important anyway because it's very stable.

Release version:
N/A

Operator snapshot version:
N/A

OCP version:
N/A

Browser Info:
N/A

Steps to reproduce:
N/A

Actual results:
pin-latest.py pins the postgres image and as a result

Expected results:
pin-latest.py should not pin the postgres image

Additional info:
Comment 5 errata-xmlrpc 2022-09-06 22:30:54 UTC 
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 (Moderate: Red Hat Advanced Cluster Management 2.6.0 security updates and bug fixes), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6370