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-48044: [Nutanix] Install multi-NICs cluster failed with failureDomains #9376

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

OCPBUGS-48044: [Nutanix] Install multi-NICs cluster failed with failureDomains #9376

wants to merge 2 commits into from
+798,080 −115,351

Conversation

yanhua121
Copy link
Contributor

OCPBUGS-48044:
[Nutanix] Install multi-NICs cluster failed with failureDomains

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

@yanhua121: This pull request references Jira Issue OCPBUGS-48044, which is invalid:

  • expected the bug to target the "4.19.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.

In response to this:

OCPBUGS-48044:
[Nutanix] Install multi-NICs cluster failed with failureDomains

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.

@yanhua121
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@yanhua121: This pull request references Jira Issue OCPBUGS-48044, which is invalid:

  • expected the bug to target the "4.19.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.

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 openshift-ci bot requested review from barbacbd and jhixson74 January 17, 2025 15:55
@yanhua121
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 17, 2025
@openshift-ci-robot
Copy link
Contributor

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

Requesting review from QA contact:
/cc @gpei

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 openshift-ci bot requested a review from gpei January 17, 2025 15:57
@yanhua121
Copy link
Contributor Author

/retest-required

@yanhua121
Copy link
Contributor Author

/retest

@yanhua121
Copy link
Contributor Author

/retest-required

@jhixson74
Copy link
Member

Can you break the commits up here? A description of the fix would be nice too.

@yanhua121
Copy link
Contributor Author

/retest-required

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 28, 2025

[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 rvanderp3 for approval. For more information see the 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:

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

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 28, 2025
@yanhua121
Copy link
Contributor Author

/retest-required

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 30, 2025
@yanhua121
Copy link
Contributor Author

/retest-required

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@yanhua121: 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-azure-ovn-shared-vpc 2ed5a34 link false /test e2e-azure-ovn-shared-vpc
ci/prow/e2e-azurestack 2ed5a34 link false /test e2e-azurestack
ci/prow/altinfra-e2e-aws-ovn 2ed5a34 link false /test altinfra-e2e-aws-ovn
ci/prow/e2e-aws-ovn-shared-vpc-edge-zones 2ed5a34 link false /test e2e-aws-ovn-shared-vpc-edge-zones
ci/prow/e2e-aws-ovn-single-node 2ed5a34 link false /test e2e-aws-ovn-single-node
ci/prow/okd-scos-e2e-aws-ovn 2ed5a34 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-shared-vpc-custom-security-groups 2ed5a34 link false /test e2e-aws-ovn-shared-vpc-custom-security-groups
ci/prow/e2e-vsphere-static-ovn 2ed5a34 link false /test e2e-vsphere-static-ovn
ci/prow/e2e-aws-ovn-imdsv2 2ed5a34 link false /test e2e-aws-ovn-imdsv2
ci/prow/e2e-aws-ovn-fips 2ed5a34 link false /test e2e-aws-ovn-fips
ci/prow/e2e-openstack-nfv-intel 2ed5a34 link false /test e2e-openstack-nfv-intel
ci/prow/e2e-aws-ovn-edge-zones 2ed5a34 link false /test e2e-aws-ovn-edge-zones
ci/prow/e2e-vsphere-host-groups-ovn-custom-no-upgrade 2ed5a34 link false /test e2e-vsphere-host-groups-ovn-custom-no-upgrade
ci/prow/e2e-aws-ovn-heterogeneous 2ed5a34 link false /test e2e-aws-ovn-heterogeneous

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.

@yanhua121
Copy link
Contributor Author

/retest

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

@barbacbd barbacbd Awaiting requested review from barbacbd

@jhixson74 jhixson74 Awaiting requested review from jhixson74

@gpei gpei Awaiting requested review from gpei

Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@yanhua121 @openshift-ci-robot @jhixson74 @openshift-merge-robot