Bug 2077999

Summary: [4.9] Publish RHEL CoreOS AMIs in AWS ap-southeast-3 region
Product: OpenShift Container Platform Reporter: RHCOS Bug Bot <rhcos-bot>
Component: RHCOSAssignee: Michael Nguyen <mnguyen>
Status: CLOSED ERRATA QA Contact: HuijingHei <hhei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.11CC: dornelas, jligon, miabbott, mrussell, nstielau
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2077998
: 2078000 (view as bug list) Environment:
Last Closed: 2022-06-30 05:31:20 UTC 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: 2043298, 2077998    
Bug Blocks: 2078000    

Description RHCOS Bug Bot 2022-04-22 19:30:15 UTC
Backport the fix for bug 2077994 to 4.9.

Comment 1 RHCOS Bug Bot 2022-06-03 12:18:01 UTC
This bug has been reported fixed in a new RHCOS build and is ready for QE verification.  To mark the bug verified, set the Verified field to Tested.  This bug will automatically move to MODIFIED once the fix has landed in a new bootimage.

Comment 2 Michael Nguyen 2022-06-03 12:21:41 UTC
To Verify: Provision RHCOS in ap-southeast-3 

You can use coreos-assembler to do this:
[coreos-assembler]$ kola spawn -d -p aws --aws-type t3.small --aws-ami 	ami-0096a4072f356f710 --aws-region ap-southeast-3

Comment 3 Micah Abbott 2022-06-03 13:26:06 UTC
[coreos-assembler]$ kola spawn -d -p aws --aws-type t3.small --aws-ami     ami-0096a4072f356f710 --aws-region ap-southeast-3
2022-06-03T13:22:33Z cli: Started logging at level DEBUG
2022-06-03T13:22:33Z cli: Started logging at level DEBUG
2022-06-03T13:22:45Z platform/api/aws: created security group sg-015abaa54a2cb380b
2022-06-03T13:22:48Z util: WaitUntilReady: checkFunction took 362.097144ms
2022-06-03T13:22:58Z util: WaitUntilReady: checkFunction took 365.081293ms
2022-06-03T13:23:22Z util: RetryUntilTimeout: f() took 23.860204101s
2022-06-03T13:23:34Z util: RetryUntilTimeout: f() took 1.805768065s
2022-06-03T13:23:50Z util: RetryUntilTimeout: f() took 6.153826129s
2022-06-03T13:23:53Z util: RetryUntilTimeout: f() took 2.972343005s
Red Hat Enterprise Linux CoreOS 49.84.202205311501-0
  Part of OpenShift 4.9, RHCOS is a Kubernetes native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).

WARNING: Direct SSH access to machines is not recommended; instead,
make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.9/architecture/architecture-rhcos.html

---
[bound] -bash-4.4$ rpm-ostree status
State: idle
Deployments:
* ostree://c7995a310da90340b572f2a6fbc4d454f206c45ef990e2eb948e4c0325ac47eb
                   Version: 49.84.202205311501-0 (2022-05-31T15:05:00Z)

Comment 4 RHCOS Bug Bot 2022-06-09 16:49:57 UTC
The fix for this bug has landed in a bootimage bump, as tracked in bug 2043298 (now in status MODIFIED).  Moving this bug to MODIFIED.

Comment 7 HuijingHei 2022-06-15 08:52:59 UTC
Verify passed using command:

[coreos-assembler]$ kola spawn -d -p aws --aws-type t3.small --aws-ami ami-0096a4072f356f710 --aws-region ap-southeast-3
Red Hat Enterprise Linux CoreOS 49.84.202205311501-0
  Part of OpenShift 4.9, RHCOS is a Kubernetes native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).

WARNING: Direct SSH access to machines is not recommended; instead,
make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.9/architecture/architecture-rhcos.html

---
[bound] -bash-4.4$ rpm-ostree status
State: idle
Deployments:
* ostree://c7995a310da90340b572f2a6fbc4d454f206c45ef990e2eb948e4c0325ac47eb
                   Version: 49.84.202205311501-0 (2022-05-31T15:05:00Z)

Comment 11 errata-xmlrpc 2022-06-30 05:31:20 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 (OpenShift Container Platform 4.9.40 bug fix update), 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/RHBA-2022:5180