search

openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.49k stars 4.7k forks source link

[release-4.17] OCPBUGS-44062: Adjust createDNSPod() to support hypershift dual-stack test #29254

Closed openshift-cherrypick-robot closed 2 weeks ago

openshift-cherrypick-robot commented 3 weeks ago

This is an automated cherry-pick of #29231

/assign LiangquanLi930

/cherrypick release-4.16 release-4.15 release-4.14

openshift-ci-robot commented 3 weeks ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-38713 has been cloned as Jira Issue OCPBUGS-44062. Will retitle bug to link to clone. /retitle [release-4.17] OCPBUGS-44062: Adjust createDNSPod() to support hypershift dual-stack test

In response to [this](https://github.com/openshift/origin/pull/29254): >This is an automated cherry-pick of #29231 > >/assign LiangquanLi930 > >/cherrypick release-4.16 release-4.15 release-4.14 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 3 weeks ago

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44062, which is invalid:

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](https://github.com/openshift/origin/pull/29254): >This is an automated cherry-pick of #29231 > >/assign LiangquanLi930 > >/cherrypick release-4.16 release-4.15 release-4.14 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
LiangquanLi930 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

@LiangquanLi930: This pull request references Jira Issue OCPBUGS-44062, which is invalid:

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](https://github.com/openshift/origin/pull/29254#issuecomment-2452920284): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
LiangquanLi930 commented 2 weeks ago

/jira refresh

openshift-ci-robot commented 2 weeks ago

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

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.17.z) matches configured target version for branch (4.17.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-38713](https://issues.redhat.com//browse/OCPBUGS-38713) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-38713](https://issues.redhat.com//browse/OCPBUGS-38713) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

Requesting review from QA contact: /cc @LiangquanLi930

In response to [this](https://github.com/openshift/origin/pull/29254#issuecomment-2452922835): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
LiangquanLi930 commented 2 weeks ago

/retest

neisw commented 2 weeks ago

/approved

neisw commented 2 weeks ago

/approve

lihongan commented 2 weeks ago

/retest

lihongan commented 2 weeks ago

/lgtm

openshift-ci[bot] commented 2 weeks ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lihongan, neisw, openshift-cherrypick-robot

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: - ~~[OWNERS](https://github.com/openshift/origin/blob/release-4.17/OWNERS)~~ [neisw] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 2 weeks ago

@openshift-cherrypick-robot: 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-vsphere-ovn-dualstack-primaryv6 8c1cfb6b5f34de0d664e06cc6fe59ec2da29feae link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-upgrade 8c1cfb6b5f34de0d664e06cc6fe59ec2da29feae link false /test e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 2 weeks ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-44062: All pull requests linked via external trackers have merged:

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

In response to [this](https://github.com/openshift/origin/pull/29254): >This is an automated cherry-pick of #29231 > >/assign LiangquanLi930 > >/cherrypick release-4.16 release-4.15 release-4.14 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-cherrypick-robot commented 2 weeks ago

@openshift-cherrypick-robot: new pull request created: #29267

In response to [this](): >This is an automated cherry-pick of #29231 > >/assign LiangquanLi930 > >/cherrypick release-4.16 release-4.15 release-4.14 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-bot commented 2 weeks ago

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202411052236.p0.gb231f76.assembly.stream.el9. All builds following this will include this PR.