Skip to content

[Automated] OCPBUGS-100433: Update AMI Whitelist - #6358

Open
openshift-ci-robot wants to merge 1 commit into
openshift:mainfrom
openshift-ci-robot:automated-ami-update-20260801-000738
Open

[Automated] OCPBUGS-100433: Update AMI Whitelist#6358
openshift-ci-robot wants to merge 1 commit into
openshift:mainfrom
openshift-ci-robot:automated-ami-update-20260801-000738

Conversation

@openshift-ci-robot

@openshift-ci-robot openshift-ci-robot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Summary

This automated PR updates AMI IDs to the latest versions.

AMI Changes

  • Added 200 new AMI(s)
  • Total AMI count: 9574

File Changes

 pkg/controller/bootimage/ami.go | 42 ++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 41 insertions(+), 1 deletion(-)

Generated by: periodic-ci-openshift-machine-config-operator-update-amis
Generated at: 2026-08-01T00:07:40+0000

Summary by CodeRabbit

  • Improvements
    • Expanded the list of supported Amazon Machine Images (AMIs).
    • Existing supported AMIs remain available.

This is an automated commit to update AMI IDs.
@openshift-ci-robot

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.22
/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-cherrypick-robot

Copy link
Copy Markdown

@openshift-ci-robot: once the present PR merges, I will cherry-pick it on top of release-4.19, release-4.20, release-4.21, release-4.22 in new PRs and assign them to you.

Details

In response to this:

/cherry-pick release-4.22
/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 1, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor Author

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-100433, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

This automated PR updates AMI IDs to the latest versions.

AMI Changes

  • Added 200 new AMI(s)
  • Total AMI count: 9574

File Changes

pkg/controller/bootimage/ami.go | 42 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)

Generated by: periodic-ci-openshift-machine-config-operator-update-amis
Generated at: 2026-08-01T00:07:40+0000

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 1, 2026
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: fa4578d4-3223-4dc1-8f6d-17c3f7593f05

📥 Commits

Reviewing files that changed from the base of the PR and between 16dce44 and 9620146.

📒 Files selected for processing (1)
  • pkg/controller/bootimage/ami.go

Walkthrough

The boot image controller now allows additional AMI IDs through the expanded AllowedAMIs set. Existing IDs remain included.

Changes

Allowed AMI configuration

Layer / File(s) Summary
Expand allowed AMI set
pkg/controller/bootimage/ami.go
The exported AllowedAMIs set retains its existing IDs and includes numerous additional AMI IDs.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the primary change: updating the AMI whitelist.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR changes only pkg/controller/bootimage/ami.go by adding AMI IDs; no test files or Ginkgo test-title declarations changed.
Test Structure And Quality ✅ Passed The patch changes only the data-only AllowedAMIs set in ami.go; it adds no Ginkgo tests, cluster operations, waits, or assertions to assess.
Microshift Test Compatibility ✅ Passed The patch changes only the AMI data declaration in pkg/controller/bootimage/ami.go; it adds no Ginkgo tests or test references requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The commit changes only the AllowedAMIs data in pkg/controller/bootimage/ami.go; no Ginkgo tests or test files were added, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The commit changes only the data-only AllowedAMIs set in pkg/controller/bootimage/ami.go; no scheduling APIs, manifests, selectors, affinity, replicas, taints, or tolerations are introduced.
Ote Binary Stdout Contract ✅ Passed The commit changes only the top-level AllowedAMIs data initializer; the changed file has no main, suite setup, logging, or stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes only the AllowedAMIs data in pkg/controller/bootimage/ami.go; no Ginkgo tests or IPv4/external connectivity logic were added.
No-Weak-Crypto ✅ Passed The PR changes only AMI string literals in AllowedAMIs; all added values match ami-[0-9a-f]{17}, with no weak-crypto APIs, custom crypto, or secret comparisons.
Container-Privileges ✅ Passed The PR changes only pkg/controller/bootimage/ami.go by adding AMI IDs; no changed manifest contains privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR changes only AllowedAMIs data in ami.go; the 200 added values are AMI IDs, with no added logging calls or sensitive-data values.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-ci-robot
Once this PR has been reviewed and has the lgtm label, please assign harshwardhanpatil07 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot

Copy link
Copy Markdown
Contributor Author

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-100433, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

Summary

This automated PR updates AMI IDs to the latest versions.

AMI Changes

  • Added 200 new AMI(s)
  • Total AMI count: 9574

File Changes

pkg/controller/bootimage/ami.go | 42 ++++++++++++++++++++++++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)

Generated by: periodic-ci-openshift-machine-config-operator-update-amis
Generated at: 2026-08-01T00:07:40+0000

Summary by CodeRabbit

  • Improvements
  • Expanded the list of supported Amazon Machine Images (AMIs).
  • Existing supported AMIs remain available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-images 9620146 link true /test okd-scos-images

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants