-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.16
Description of problem:
Config custom AMI for cluster: platform.aws.defaultMachinePlatform.amiID Or installconfig.controlPlane.platform.aws.amiID installconfig.compute.platform.aws.amiID Master machines still use default AMI instead of custom one. aws ec2 describe-instances --filters "Name=tag:kubernetes.io/cluster/yunjiang-cap6-qjc5t,Va│ lues=owned" "Name=tag:Name,Values=*worker*" --output json | jq '.Reservations[].Instances[].ImageId' | sort | uniq │ "ami-0f71147cab4dbfb61" aws ec2 describe-instances --filters "Name=tag:kubernetes.io/cluster/yunjiang-cap6-qjc5t,Va│ lues=owned" "Name=tag:Name,Values=*master*" --output json | jq '.Reservations[].Instances[].ImageId' | sort | uniq │ "Ami-0ae9b509738034a2c" <- default ami
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-05-08-222442
How reproducible:
Steps to Reproduce:
1.See description 2. 3.
Actual results:
See description
Expected results:
master machines use custom AMI
Additional info:
- blocks
-
OCPBUGS-34760 [AWS CAPI install] custom AMI can not be applied to master machines
- Closed
- is cloned by
-
OCPBUGS-34760 [AWS CAPI install] custom AMI can not be applied to master machines
- Closed
- is related to
-
CORS-2890 Provision AWS with CAPI (no mgmt cluster)
- Testing
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update