search

openshift / origin

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

OCPBUGS-38713: Adjust createDNSPod() to support hypershift dual-stack test #29231

Closed LiangquanLi930 closed 3 weeks ago

LiangquanLi930 commented 1 month ago

For HyperShift, since master nodes are not visible in the HostedCluster, adjust createDNSPod() to support dual-stack testing in HyperShift.

test job: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29228/pull-ci-openshift-origin-release-4.16-e2e-agent-connected-ovn-dualstack-metal3/1849379580285030400

passed: (20.9s) 2024-10-24T12:00:01 "[sig-network-edge] DNS should answer A and AAAA queries for a dual-stack service [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]"
openshift-ci-robot commented 1 month ago

@LiangquanLi930: This pull request references Jira Issue OCPBUGS-38713, 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 New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @melvinjoseph86

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/29231): > 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 1 month ago

@LiangquanLi930: This pull request references Jira Issue OCPBUGS-38713, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @melvinjoseph86

In response to [this](https://github.com/openshift/origin/pull/29231): >For HyperShift, since master nodes are not visible in the HostedCluster, adjust createDNSPod() to support dual-stack testing in HyperShift. > >test job: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29228/pull-ci-openshift-origin-release-4.16-e2e-agent-connected-ovn-dualstack-metal3/1849379580285030400 >``` >passed: (20.9s) 2024-10-24T12:00:01 "[sig-network-edge] DNS should answer A and AAAA queries for a dual-stack service [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" >``` 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 1 month ago

/retest

LiangquanLi930 commented 1 month ago

/retest

jparrill commented 1 month ago

/lgtm

candita commented 1 month ago

/assign

openshift-trt-bot commented 1 month ago

Job Failure Risk Analysis for sha: a5319033c1dd8f94f97079b62857a47eefa64a8b

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-serial High
[sig-arch][Late][Jira:"kube-apiserver"] collect certificate data [Suite:openshift/conformance/parallel]
This test has passed 100.00% of 59 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.
---
[sig-node] node-lifecycle detects unexpected not ready node
This test has passed 100.00% of 59 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.

Open Bugs
etcd-scaling jobs failing ~60% of the time
---
[sig-node] node-lifecycle detects unreachable state on node
This test has passed 100.00% of 59 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.

Open Bugs
etcd-scaling jobs failing ~60% of the time
pull-ci-openshift-origin-master-e2e-aws-ovn-kube-apiserver-rollout Low
[Conformance][Suite:openshift/kube-apiserver/rollout][Jira:"kube-apiserver"][sig-kube-apiserver] kube-apiserver should roll out new revisions without disruption [apigroup:config.openshift.io][apigroup:operator.openshift.io]
This test has passed 42.86% of 14 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-kube-apiserver-rollout'] in the last 14 days.
openshift-trt-bot commented 1 month ago

Job Failure Risk Analysis for sha: 1e927cdd25d62a0d37646b4a748b86d3d51a3115

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn IncompleteTests
Tests for this run (101) are below the historical average (1894): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-aws-ovn-kube-apiserver-rollout Low
[Conformance][Suite:openshift/kube-apiserver/rollout][Jira:"kube-apiserver"][sig-kube-apiserver] kube-apiserver should roll out new revisions without disruption [apigroup:config.openshift.io][apigroup:operator.openshift.io]
This test has passed 42.86% of 14 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-kube-apiserver-rollout'] in the last 14 days.
LiangquanLi930 commented 1 month ago

/retest

LiangquanLi930 commented 4 weeks ago

/retest

openshift-trt-bot commented 4 weeks ago

Job Failure Risk Analysis for sha: 2220db72af53c71815640591b66149c73a9eae1a

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial Medium
[sig-node] static pods should start after being created
This test has passed 85.07% of 67 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-serial'] in the last 14 days.

Open Bugs
Static pod controller pods sometimes fail to start [kube-controller-manager]
Static pod controller pods sometimes fail to start [etcd]
LiangquanLi930 commented 4 weeks ago

/retest

candita commented 3 weeks ago

/test verify

candita commented 3 weeks ago

/lgtm /approve

candita commented 3 weeks ago

@LiangquanLi930 please run make verify against this PR and add any generated changes to it. @sosiouxme explained that this is likely the issue here.

/hold

LiangquanLi930 commented 3 weeks ago

/retest

LiangquanLi930 commented 3 weeks ago

/retest

openshift-trt-bot commented 3 weeks ago

Job Failure Risk Analysis for sha: 9573127d41c0812f63d26537c75f0ca2bceb82ee

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade Low
[sig-node] static pods should start after being created
This test has passed 78.01% of 191 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

Open Bugs
Static pod controller pods sometimes fail to start [kube-controller-manager]
Static pod controller pods sometimes fail to start [etcd]
---
[sig-node] static pods should start after being created
This test has passed 78.42% of 190 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

Open Bugs
Static pod controller pods sometimes fail to start [kube-controller-manager]
Static pod controller pods sometimes fail to start [etcd]
candita commented 3 weeks ago

/lgtm /approve

Miciah commented 3 weeks ago

/approve per https://github.com/openshift/origin/pull/29231#issuecomment-2447124212.

candita commented 3 weeks ago

Hi @deads2k - we'll need your approval on this one. I added #29247 so we can review/approve our own PRs in these directories in the future.

/assign deads2k

candita commented 3 weeks ago

Lots of etcd issues today, including in this test. /test e2e-aws-ovn-single-node-upgrade

dgoodwin commented 3 weeks ago

/approve

openshift-ci[bot] commented 3 weeks ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita, dgoodwin, jparrill, LiangquanLi930, Miciah

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/master/OWNERS)~~ [dgoodwin] 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 3 weeks ago

@LiangquanLi930: all tests passed!

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 3 weeks ago

@LiangquanLi930: Jira Issue OCPBUGS-38713: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to [this](https://github.com/openshift/origin/pull/29231): >For HyperShift, since master nodes are not visible in the HostedCluster, adjust createDNSPod() to support dual-stack testing in HyperShift. > >test job: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29228/pull-ci-openshift-origin-release-4.16-e2e-agent-connected-ovn-dualstack-metal3/1849379580285030400 >``` >passed: (20.9s) 2024-10-24T12:00:01 "[sig-network-edge] DNS should answer A and AAAA queries for a dual-stack service [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" >``` 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 3 weeks ago

/cherry-pick release-4.17 release-4.16 release-4.15 release-4.14

openshift-cherrypick-robot commented 3 weeks ago

@LiangquanLi930: new pull request created: #29254

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2450440615): >/cherry-pick release-4.17 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 3 weeks ago

[ART PR BUILD NOTIFIER]

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

LiangquanLi930 commented 3 weeks ago

/jira backport release-4.17,release-4.16,release-4.15,release-4.14

openshift-ci-robot commented 3 weeks ago

@LiangquanLi930: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges: /cherrypick release-4.17 /cherrypick release-4.16 /cherrypick release-4.15 /cherrypick release-4.14

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451499334): >/jira backport release-4.17,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 3 weeks ago

@openshift-ci-robot: new pull request created: #29256

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451500701): >@LiangquanLi930: The following backport issues have been created: >- [OCPBUGS-44062](https://issues.redhat.com//browse/OCPBUGS-44062) for branch release-4.17 >- [OCPBUGS-44105](https://issues.redhat.com//browse/OCPBUGS-44105) for branch release-4.16 >- [OCPBUGS-44106](https://issues.redhat.com//browse/OCPBUGS-44106) for branch release-4.15 >- [OCPBUGS-44107](https://issues.redhat.com//browse/OCPBUGS-44107) for branch release-4.14 > >Queuing cherrypicks to the requested branches to be created after this PR merges: >/cherrypick release-4.17 >/cherrypick release-4.16 >/cherrypick release-4.15 >/cherrypick release-4.14 > >
> >In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451499334): > >>/jira backport release-4.17,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. >

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 commented 3 weeks ago

@openshift-ci-robot: new pull request created: #29257

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451500701): >@LiangquanLi930: The following backport issues have been created: >- [OCPBUGS-44062](https://issues.redhat.com//browse/OCPBUGS-44062) for branch release-4.17 >- [OCPBUGS-44105](https://issues.redhat.com//browse/OCPBUGS-44105) for branch release-4.16 >- [OCPBUGS-44106](https://issues.redhat.com//browse/OCPBUGS-44106) for branch release-4.15 >- [OCPBUGS-44107](https://issues.redhat.com//browse/OCPBUGS-44107) for branch release-4.14 > >Queuing cherrypicks to the requested branches to be created after this PR merges: >/cherrypick release-4.17 >/cherrypick release-4.16 >/cherrypick release-4.15 >/cherrypick release-4.14 > >
> >In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451499334): > >>/jira backport release-4.17,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. >

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 commented 3 weeks ago

@openshift-ci-robot: new pull request created: #29258

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451500701): >@LiangquanLi930: The following backport issues have been created: >- [OCPBUGS-44062](https://issues.redhat.com//browse/OCPBUGS-44062) for branch release-4.17 >- [OCPBUGS-44105](https://issues.redhat.com//browse/OCPBUGS-44105) for branch release-4.16 >- [OCPBUGS-44106](https://issues.redhat.com//browse/OCPBUGS-44106) for branch release-4.15 >- [OCPBUGS-44107](https://issues.redhat.com//browse/OCPBUGS-44107) for branch release-4.14 > >Queuing cherrypicks to the requested branches to be created after this PR merges: >/cherrypick release-4.17 >/cherrypick release-4.16 >/cherrypick release-4.15 >/cherrypick release-4.14 > >
> >In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451499334): > >>/jira backport release-4.17,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. >

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 commented 3 weeks ago

@openshift-ci-robot: new pull request could not be created: failed to create pull request against openshift/origin#release-4.17 from head openshift-cherrypick-robot:cherry-pick-29231-to-release-4.17: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-29231-to-release-4.17."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451500701): >@LiangquanLi930: The following backport issues have been created: >- [OCPBUGS-44062](https://issues.redhat.com//browse/OCPBUGS-44062) for branch release-4.17 >- [OCPBUGS-44105](https://issues.redhat.com//browse/OCPBUGS-44105) for branch release-4.16 >- [OCPBUGS-44106](https://issues.redhat.com//browse/OCPBUGS-44106) for branch release-4.15 >- [OCPBUGS-44107](https://issues.redhat.com//browse/OCPBUGS-44107) for branch release-4.14 > >Queuing cherrypicks to the requested branches to be created after this PR merges: >/cherrypick release-4.17 >/cherrypick release-4.16 >/cherrypick release-4.15 >/cherrypick release-4.14 > >
> >In response to [this](https://github.com/openshift/origin/pull/29231#issuecomment-2451499334): > >>/jira backport release-4.17,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. >

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.