Skip to content

OCPBUGS-77683: Add c8g* to tested_instance_types_aarch64#10356

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
lwan-wanglin:aws-arm-instance
Mar 6, 2026
Merged

OCPBUGS-77683: Add c8g* to tested_instance_types_aarch64#10356
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
lwan-wanglin:aws-arm-instance

Conversation

@lwan-wanglin
Copy link
Contributor

I have run jobs to test installation and storage on the newly added instance type.

@openshift-ci openshift-ci bot requested review from mtulio and patrickdillon March 4, 2026 08:52
@lwan-wanglin lwan-wanglin changed the title Add c8g* to tested_instance_types_aarch64 OCPBUGS-77683: Add c8g* to tested_instance_types_aarch64 Mar 4, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This pull request references Jira Issue OCPBUGS-77683, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

I have run jobs to test installation and storage on the newly added instance type.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 4, 2026
@lwan-wanglin
Copy link
Contributor Author

/jira refresh

@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 Mar 5, 2026
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This pull request references Jira Issue OCPBUGS-77683, 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 (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lwan-wanglin

Details

In response to this:

/jira refresh

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 removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 5, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 5, 2026

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: lwan-wanglin.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@lwan-wanglin: This pull request references Jira Issue OCPBUGS-77683, 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 (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lwan-wanglin

In response to this:

/jira refresh

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.

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.

@lwan-wanglin
Copy link
Contributor Author

/verified by lwan

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 5, 2026
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This PR has been marked as verified by lwan.

Details

In response to this:

/verified by lwan

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.

@lwan-wanglin
Copy link
Contributor Author

cc @yunjiang29 @gpei to review

@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Mar 5, 2026
@gpei
Copy link
Contributor

gpei commented Mar 5, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2026
@lwan-wanglin
Copy link
Contributor Author

/verified by lwan

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 5, 2026
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: This PR has been marked as verified by lwan.

Details

In response to this:

/verified by lwan

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.

@lwan-wanglin
Copy link
Contributor Author

hi @sadasu, could you please approve the PR? Thanks!

@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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

The pull request process is described 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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 5, 2026
@lwan-wanglin
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 6, 2026

@lwan-wanglin: The following tests 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/e2e-aws-ovn-edge-zones 2df87ea link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-single-node 2df87ea link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-heterogeneous 2df87ea link false /test e2e-aws-ovn-heterogeneous

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.

@lwan-wanglin
Copy link
Contributor Author

/test artifacts-images

@openshift-merge-bot openshift-merge-bot bot merged commit 67a8be4 into openshift:main Mar 6, 2026
14 of 17 checks passed
@openshift-ci-robot
Copy link
Contributor

@lwan-wanglin: Jira Issue Verification Checks: Jira Issue OCPBUGS-77683
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-77683 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

I have run jobs to test installation and storage on the newly added instance type.

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.

@lwan-wanglin
Copy link
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@lwan-wanglin: #10356 failed to apply on top of branch "release-4.20":

Applying: Add c8g* to tested_instance_types_aarch64
Using index info to reconstruct a base tree...
M	docs/user/aws/tested_instance_types_aarch64.md
Falling back to patching base and 3-way merge...
Auto-merging docs/user/aws/tested_instance_types_aarch64.md
CONFLICT (content): Merge conflict in docs/user/aws/tested_instance_types_aarch64.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Add c8g* to tested_instance_types_aarch64

Details

In response to this:

/cherry-pick release-4.20

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.

@lwan-wanglin
Copy link
Contributor Author

/cherry-pick release-4.21

@openshift-cherrypick-robot

@lwan-wanglin: new pull request created: #10366

Details

In response to this:

/cherry-pick release-4.21

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.22.0-0.nightly-2026-03-06-163638

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants