Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2010495

Summary: Update Service payload mismatch with upstream
Product: OpenShift Container Platform Reporter: Harshil <hsabhnan>
Component: OpenShift Update ServiceAssignee: Over the Air Updates <aos-team-ota>
OpenShift Update Service sub component: operand QA Contact: liujia <jiajliu>
Status: CLOSED DUPLICATE Docs Contact: Kathryn Alexander <kalexand>
Severity: unspecified    
Priority: unspecified CC: wking
Version: 4.6   
Target Milestone: ---   
Target Release: ---   
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: 2021-10-20 16:46:33 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:

Description Harshil 2021-10-04 19:48:52 UTC 
Description of problem (please be detailed as possible and provide log
snippests):

OSUS was deployed and is running properly. After OSUS builds the graph, on querying the graph, The payload for OCP release version is not accurate to upstream payload.   

Version of all relevant components (if applicable):
OSUS 4.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Since the graph returns wrong payload, we cannot use the updater service to upgrade any of the OCP Clusters

Is there any workaround available to the best of your knowledge?
Nope

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

1

Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Mirror openshift release images to a private jfrog artifactory registry
2. Install OSUS operator and point to artifactory
3. Query the graph to check the payload


Actual results:
payload for OCP release version should be the same as found in quay or in production OSUS service

For eg, for OCP-4.7.9. Expected payload should be sha256:dd75546170e65d7d17130de10a6ffeb425f960399640632cbc8426b9da338458

Expected results:

payload for OCP release version is a random string
For Ocp-4.7.9 OSUS release version payload found is "sha256:d5639f376e94842e8ade89b9743d4ba6104db38562b8816f48b551a9e7503384"


Additional info:
Comment 1 W. Trevor King 2021-10-20 16:46:33 UTC 

*** This bug has been marked as a duplicate of bug 2010497 ***