Skip to content

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented May 6, 2025

This PR tests the bump from #1227 but excludes the changes to use the new options in OSSM 3.0.1.

This PR is only for testing.

Miciah added 3 commits May 6, 2025 10:57
This commit resolves NE-2022.

https://issues.redhat.com/browse/NE-2022

* cmd/ingress-operator/start.go (defaultGatewayAPIOperatorVersion):
* manifests/02-deployment-ibm-cloud-managed.yaml
(GATEWAY_API_OPERATOR_VERSION):
* manifests/02-deployment.yaml
(GATEWAY_API_OPERATOR_VERSION): Bump from OSSM v3.0.0 to v3.0.1.
* pkg/operator/controller/gatewayclass/istio.go (desiredIstio): Bump
from Istio v1.24.3 to v1.24.4.
Increase the timeout in assertDNSRecord for polling for the DNSRecord CR
from 1 minute to 10 minutes.

The cloud provider can easily take over a minute to provision the load balancer,
and the operator cannot create the DNSRecord CR before the load balancer has
been provisioned and assigned a host name or address.  Consequently, the polling
loop could easily reach the 1-minute timeout just on account of the time that it
takes to provision the load balancer.

* test/e2e/util_gatewayapi_test.go (assertDNSRecord): Increase timeout
for the DNSRecord CR polling loop from 1m to 10m.
Increase the timeout for polling the gateway, and dump the gateway if
the test fails.

* test/e2e/gateway_api_test.go (testGatewayAPIManualDeployment):
Increase the timeout for polling the gateway from 1m to 5m.  Dump the
gateway if the test fails.
@openshift-ci openshift-ci bot requested review from frobware and rfredette May 6, 2025 14:59
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 6, 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 frobware for approval. For more information see the 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:

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

@Miciah
Copy link
Contributor Author

Miciah commented Jun 30, 2025

/retest

@Miciah
Copy link
Contributor Author

Miciah commented Jun 30, 2025

/test e2e-aws-gatewayapi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 30, 2025

@Miciah: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-upgrade
/test e2e-azure-operator
/test e2e-gcp-operator
/test e2e-hypershift
/test hypershift-e2e-aks
/test images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-gatewayapi-conformance
/test e2e-aws-operator-techpreview
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-techpreview
/test e2e-azure-manual-oidc
/test e2e-azure-ovn
/test e2e-gcp-ovn
/test e2e-ibmcloud-operator
/test e2e-openstack-operator
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator-techpreview
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-hypershift-conformance
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-serial
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-single-node
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-techpreview
pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-upgrade
pull-ci-openshift-cluster-ingress-operator-master-e2e-azure-operator
pull-ci-openshift-cluster-ingress-operator-master-e2e-azure-ovn
pull-ci-openshift-cluster-ingress-operator-master-e2e-gcp-operator
pull-ci-openshift-cluster-ingress-operator-master-e2e-gcp-ovn
pull-ci-openshift-cluster-ingress-operator-master-e2e-hypershift
pull-ci-openshift-cluster-ingress-operator-master-hypershift-e2e-aks
pull-ci-openshift-cluster-ingress-operator-master-images
pull-ci-openshift-cluster-ingress-operator-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-cluster-ingress-operator-master-unit
pull-ci-openshift-cluster-ingress-operator-master-verify
pull-ci-openshift-cluster-ingress-operator-master-verify-deps
Details

In response to this:

/test e2e-aws-gatewayapi

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-ci
Copy link
Contributor

openshift-ci bot commented Jun 30, 2025

@Miciah: 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-gatewayapi 8f21f18 link false /test e2e-aws-gatewayapi
ci/prow/e2e-gcp-operator 8f21f18 link true /test e2e-gcp-operator
ci/prow/e2e-aws-operator-techpreview 8f21f18 link false /test e2e-aws-operator-techpreview
ci/prow/e2e-aws-operator 8f21f18 link true /test e2e-aws-operator
ci/prow/e2e-azure-operator 8f21f18 link true /test e2e-azure-operator

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

@Miciah
Copy link
Contributor Author

Miciah commented Jul 16, 2025

/close

@openshift-ci openshift-ci bot closed this Jul 16, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 16, 2025

@Miciah: 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-sigs/prow repository.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant