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

[jinyunma]

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]

@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-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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• docs/user/azure/OWNERS

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

[jinyunma]

cc @jianlinliu @gpei @sadasu to review

[jianlinliu]

/lgtm

[openshift-ci]

@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.