Bug 2221898

Summary:	rhel-guest-image-container Dockerfile needs to be updated to correct RHEL release
Product:	Red Hat Enterprise Linux 9	Reporter:	Wei Shi <wshi>
Component:	rhel-guest-image-container	Assignee:	Achilleas Koutsou <akoutsou>
Status:	VERIFIED ---	QA Contact:	Wei Shi <wshi>
Severity:	high	Docs Contact:	Eliane Ramos Pereira <elpereir>
Priority:	unspecified
Version:	9.3	CC:	jwboyer
Target Milestone:	rc	Keywords:	Triaged
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:		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 Wei Shi 2023-07-11 08:03:09 UTC

This bug was initially created as a copy of Bug #2137800

I am copying this bug because: We need to do the same update for 9.3



Description of problem:
brew builds with name rhel-guest-image-container-9.2 has 9.3 qcow2 image inside and 
guest-rhel-9.3.0-candidate tag

Version-Release number of selected component (if applicable):
rhel-guest-image-container-9.2-755
rhel-guest-image-container-8.8.0-1101

How reproducible:
100%

Steps to Reproduce:
1. cat /etc/redhat-release
2.
3.

Actual results:
rhel-guest-image-container-9.2-755
Red Hat Enterprise Linux release 9.3 Beta (Plow)

Expected results:
rhel-guest-image-container-9.3-$ver

Additional info:
Same issue also happens on 8.9

Comment 1 Achilleas Koutsou 2023-07-13 11:43:31 UTC

Updated the version label in the rhel-9.3.0 branch to 9.3.
Sources point to Beta product ID (486).
https://pkgs.devel.redhat.com/cgit/containers/rhel-guest-image/commit/?h=rhel-9.3.0&id=612a519961b52878a5d6ca8f0a767f2b4e2fec71

Same for rhel-8.9.0
https://pkgs.devel.redhat.com/cgit/containers/rhel-guest-image/commit/?h=rhel-8.9.0&id=3c0f5b21d61c531b130ed8507a07f86e959697bf

Comment 2 Wei Shi 2023-07-14 10:23:47 UTC

Verified this issue has been fixed.