Bug 2076998

Summary:	assisted-service pin-latest.py script should exclude the postgres image
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Infrastructure Operator	Assignee:	Omer Tuchfeld <otuchfel>
Status:	ON_QA ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhacm-2.6	CC:	ccrum, trwest, yfirst
Target Milestone:	---
Target Release:	rhacm-2.5
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:		Type:	---
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:	2076901
Bug Blocks:

Description OpenShift BugZilla Robot 2022-04-20 11:49:39 UTC

+++ This bug was initially created as a clone of Bug #2076901 +++

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: