Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OCPBUGS-42412: add new tested azure instance types detected during QE 4.17 full function test #9057

Merged
merged 1 commit into from
Oct 2, 2024
Merged

OCPBUGS-42412: add new tested azure instance types detected during QE 4.17 full function test #9057

merged 1 commit into from
Oct 2, 2024

Conversation

jinyunma
Copy link
Contributor

Following instance type families are detected during 4.17 full function test, and verified by QE, append them into azure doc tested_instance_types_x86_64.md

  • standardBasv2Family
  • standardMDSHighMemoryv3Family
  • standardMIDSHighMemoryv3Family
  • standardMISHighMemoryv3Family
  • standardMSHighMemoryv3Family
  • StandardNGADSV620v1Family

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 27, 2024
@openshift-ci-robot
Copy link
Contributor

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

Requesting review from QA contact:
/cc @jinyunma

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

In response to this:

Following instance type families are detected during 4.17 full function test, and verified by QE, append them into azure doc tested_instance_types_x86_64.md

  • standardBasv2Family
  • standardMDSHighMemoryv3Family
  • standardMIDSHighMemoryv3Family
  • standardMISHighMemoryv3Family
  • standardMSHighMemoryv3Family
  • StandardNGADSV620v1Family

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

openshift-ci bot commented Sep 27, 2024

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

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

In response to this:

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

Requesting review from QA contact:
/cc @jinyunma

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

In response to this:

Following instance type families are detected during 4.17 full function test, and verified by QE, append them into azure doc tested_instance_types_x86_64.md

  • standardBasv2Family
  • standardMDSHighMemoryv3Family
  • standardMIDSHighMemoryv3Family
  • standardMISHighMemoryv3Family
  • standardMSHighMemoryv3Family
  • StandardNGADSV620v1Family

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.

@jinyunma jinyunma changed the title OCPBUGS-42412: add new tested azure instance types detected during QE 4.17 full functin test OCPBUGS-42412: add new tested azure instance types detected during QE 4.17 full function test Sep 27, 2024
@jinyunma
Copy link
Contributor Author

cc @jianlinliu @gpei @sadasu to review

@jianlinliu
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 27, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Sep 27, 2024

@jinyunma: 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/azure-ovn-marketplace-images 6de3bd1 link false /test azure-ovn-marketplace-images
ci/prow/e2e-azurestack 6de3bd1 link false /test e2e-azurestack

Full PR test history. Your PR dashboard.

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.

@sadasu
Copy link
Contributor

sadasu commented Oct 1, 2024

/approve

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu

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

The pull request process is described here

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 Oct 1, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 5abd624 into openshift:master Oct 2, 2024
6 of 9 checks passed
@openshift-ci-robot
Copy link
Contributor

@jinyunma: Jira Issue OCPBUGS-42412: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-42412 has been moved to the MODIFIED state.

In response to this:

Following instance type families are detected during 4.17 full function test, and verified by QE, append them into azure doc tested_instance_types_x86_64.md

  • standardBasv2Family
  • standardMDSHighMemoryv3Family
  • standardMIDSHighMemoryv3Family
  • standardMISHighMemoryv3Family
  • standardMSHighMemoryv3Family
  • StandardNGADSV620v1Family

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.

@jinyunma jinyunma deleted the az_new_instance_417 branch October 8, 2024 02:21
@jinyunma
Copy link
Contributor Author

jinyunma commented Oct 8, 2024

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link

@jinyunma: new pull request created: #9080

In response to this:

/cherry-pick release-4.17

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jhixson74 jhixson74 Awaiting requested review from jhixson74

@mtulio mtulio Awaiting requested review from mtulio

Assignees

@jianlinliu jianlinliu

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@jinyunma @openshift-ci-robot @jianlinliu @sadasu @openshift-cherrypick-robot