MCO-1419: OCL E2E Testing

RishabhSaini commented 2 weeks ago

ocl test: Tests whether one can turn on and opt in a pool for OCL. This involves verifying if the custom image specified in the mosc is built and successfully rolled out the specified nodes within 20 mins

go.mod changes: adds github.com/machine-config-operator 2024 version which updates github.com/docker/docker from v20.10.27 -> v24.0.7 which breaks github.com/fsouza/go-dockerclient v1.7.1 since it relies on docker v20.10.27

Hence, I manually update both github.com/docker/docker to v27.3.1 and github.com/fsouza/go-dockerclient to v1.12.0 which is their latest version

This keeps go dependencies happy :)

openshift-ci[bot] commented 2 weeks ago

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

openshift-ci[bot] commented 2 weeks ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: RishabhSaini Once this PR has been reviewed and has the lgtm label, please assign sosiouxme 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: - **[OWNERS](https://github.com/openshift/origin/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

openshift-ci-robot commented 2 weeks ago

@RishabhSaini: This pull request references MCO-1419 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29276): > 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.

RishabhSaini commented 3 days ago

/refresh

openshift-ci-robot commented 2 days ago

@RishabhSaini: This pull request references MCO-1419 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29276): >adds github.com/machine-config-operator 2024 version >which updates github.com/docker/docker from v20.10.27 -> v24.0.7 >which breaks github.com/fsouza/go-dockerclient v1.7.1 since it relies on docker v20.10.27 > >Hence, I manually update both github.com/docker/docker to v27.3.1 and github.com/fsouza/go-dockerclient to v1.12.0 which is their latest version > >This keeps go dependencies happy :) 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 2 days ago

@RishabhSaini: This pull request references MCO-1419 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29276): >ocl test: >Tests whether one can turn on and opt in a pool for OCL. This involves verifying if the custom image specified in the mosc is built and successfully rolled out the specified nodes within 20 mins > >go.mod changes: >adds github.com/machine-config-operator 2024 version >which updates github.com/docker/docker from v20.10.27 -> v24.0.7 >which breaks github.com/fsouza/go-dockerclient v1.7.1 since it relies on docker v20.10.27 > >Hence, I manually update both github.com/docker/docker to v27.3.1 and github.com/fsouza/go-dockerclient to v1.12.0 which is their latest version > >This keeps go dependencies happy :) 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[bot] commented 2 days ago

@RishabhSaini: 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-aws-ovn-upgrade	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-upgrade`
ci/prow/verify-deps	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test verify-deps`
ci/prow/e2e-aws-ovn-microshift-serial	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-aws-ovn-microshift-serial`
ci/prow/e2e-gcp-ovn-rt-upgrade	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-gcp-ovn-rt-upgrade`
ci/prow/unit	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test unit`
ci/prow/e2e-aws-ovn-single-node-serial	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-single-node-serial`
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-kube-apiserver-rollout`
ci/prow/e2e-aws-csi	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-csi`
ci/prow/e2e-aws-ovn-cgroupsv2	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-cgroupsv2`
ci/prow/e2e-agnostic-ovn-cmd	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-agnostic-ovn-cmd`
ci/prow/e2e-aws-ovn-fips	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-aws-ovn-fips`
ci/prow/e2e-gcp-ovn-upgrade	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-gcp-ovn-upgrade`
ci/prow/e2e-aws-ovn-single-node	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-single-node`
ci/prow/e2e-metal-ipi-ovn-ipv6	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-metal-ipi-ovn-ipv6`
ci/prow/e2e-gcp-csi	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-gcp-csi`
ci/prow/e2e-aws-ovn-serial	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-aws-ovn-serial`
ci/prow/e2e-aws-ovn-microshift	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-aws-ovn-microshift`
ci/prow/e2e-aws-ovn-edge-zones	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-aws-ovn-edge-zones`
ci/prow/e2e-aws-ovn-single-node-upgrade	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-aws-ovn-single-node-upgrade`
ci/prow/verify	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test verify`
ci/prow/e2e-openstack-ovn	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-openstack-ovn`
ci/prow/e2e-gcp-ovn	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	true	`/test e2e-gcp-ovn`
ci/prow/okd-scos-e2e-aws-ovn	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test okd-scos-e2e-aws-ovn`
ci/prow/e2e-metal-ipi-ovn	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-metal-ipi-ovn`
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	08667cba15cf4f3ce4a530ab905ac79de823a9c5	link	false	`/test e2e-metal-ipi-ovn-kube-apiserver-rollout`

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-trt[bot] commented 2 days ago

Job Failure Risk Analysis for sha: 08667cba15cf4f3ce4a530ab905ac79de823a9c5

Job Name	Failure Risk
pull-ci-openshift-origin-master-okd-scos-e2e-aws-ovn	IncompleteTests Tests for this run (98) are below the historical average (2993): 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-openstack-ovn	IncompleteTests Tests for this run (102) are below the historical average (3215): 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-metal-ipi-ovn-kube-apiserver-rollout	IncompleteTests Tests for this run (100) are below the historical average (1574): 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-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (100) are below the historical average (2721): 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-metal-ipi-ovn	IncompleteTests Tests for this run (100) are below the historical average (2548): 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-gcp-ovn-upgrade	IncompleteTests Tests for this run (104) are below the historical average (1816): 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-gcp-ovn-rt-upgrade	IncompleteTests Tests for this run (104) are below the historical average (1780): 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-gcp-ovn	IncompleteTests Tests for this run (104) are below the historical average (3136): 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-gcp-csi	IncompleteTests Tests for this run (104) are below the historical average (1744): 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-upgrade	IncompleteTests Tests for this run (105) are below the historical average (1816): 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-single-node-upgrade	IncompleteTests Tests for this run (104) are below the historical average (4289): 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-single-node-serial	IncompleteTests Tests for this run (103) are below the historical average (1566): 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-single-node	IncompleteTests Tests for this run (103) are below the historical average (2622): 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-serial	IncompleteTests Tests for this run (103) are below the historical average (1905): 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-microshift-serial	IncompleteTests Tests for this run (24) are below the historical average (706): 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-microshift	IncompleteTests Tests for this run (24) are below the historical average (1611): 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	IncompleteTests Tests for this run (103) are below the historical average (1709): 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-fips	IncompleteTests Tests for this run (103) are below the historical average (3177): 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-edge-zones	IncompleteTests Tests for this run (101) are below the historical average (3064): 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-cgroupsv2	IncompleteTests Tests for this run (103) are below the historical average (3063): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Showing 20 of 22 jobs analysis

openshift / origin

MCO-1419: OCL E2E Testing #29276