[WIP] Test e2e-gcp-operator

[gcs278]

WIP to test e2e operator

[openshift-ci-robot]

@gcs278: This pull request references Jira Issue OCPBUGS-13106, which is invalid:

• expected the bug to target the "4.15.0" version, but it targets "4.14.0" instead

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.

Details

In response to this:

Standardize the timeouts for waiting for Ingress Controllers to become available in E2E tests. This also updates the provisioning timeout for load-balancer-type Ingress Controllers to be 10 minutes, resolving flakes we sometimes see in GCP.

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/test-infra 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 ask for approval from gcs278. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[gcs278]

/jira refresh

[openshift-ci-robot]

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

Requesting review from QA contact:
/cc @ShudiLi

Details

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 kubernetes/test-infra repository.

[openshift-ci-robot]

@gcs278: This pull request references Jira Issue OCPBUGS-13106, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

Details

In response to this:

Standardize the timeouts for waiting for Ingress Controllers to become available in E2E tests. This also updates the provisioning timeout for load-balancer-type Ingress Controllers to be 10 minutes, resolving flakes we sometimes see in GCP.

To further illustrate, some E2E authors chose 10 minutes for load-balancer-type service and some chose 5 minutes. My intent is that this update pushes our E2E tests to be more standard to avoid inconsistencies in timeouts, which can lead to wasted investigation time.

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/test-infra repository.

[openshift-ci-robot]

@gcs278: This pull request references Jira Issue OCPBUGS-13106, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Standardize the timeouts for waiting for Ingress Controllers to become available in E2E tests. This also updates the provisioning timeout for load-balancer-type Ingress Controllers to be 10 minutes, resolving flakes we sometimes see in GCP.

To further illustrate, some E2E authors chose 10 minutes for load-balancer-type service and some chose 5 minutes. My intent is that this update pushes our E2E tests to be more standard to avoid inconsistencies in timeouts, which can lead to wasted investigation time.

WIP: Waiting for GCP CCM to work so I can compare the two to see if there is a real issue.

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/test-infra repository.

[openshift-ci-robot]

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

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

WIP to test e2e operator

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/test-infra repository.

[gcs278]

/test e2e-gcp-operator

[gcs278]

/test e2e-gcp-operator

[gcs278]

/test e2e-gcp-operator

[gcs278]

infrastructure failure
/test e2e-gcp-operator

[gcs278]

/test e2e-gcp-operator

[gcs278]

It looked like it timed out here:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-ingress-operator/981/pull-ci-openshift-cluster-ingress-operator-master-e2e-gcp-operator/1712904337807642624

Need to investigate.

[rfredette]

Borrowing this to check on the health of e2e-gcp-operator again
/test e2e-gcp-operator

[rfredette]

/test e2e-gcp-operator

[openshift-ci]

@gcs278: 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-single-node	3a5d732	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-ovn	3a5d732	link	false	/test e2e-gcp-ovn

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@gcs278: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

WIP to test e2e operator

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.

[gcs278]

openshift/cluster-cloud-controller-manager-operator#329 merged so the problem, in theory, should have gone away:
/test e2e-gcp-operator

[gcs278]

/close

[openshift-ci]

@gcs278: Closed this PR.

Details

In response to this:

/close

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/test-infra repository.