🤖 Triggering CI on branch 'release-next' after synching to upstream/main

[serverless-qe]

No description provided.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serverless-qe
Once this PR has been reviewed and has the lgtm label, please assign nak3 for approval by writing /assign @nak3 in a comment. 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

[skonto]

/retest

[skonto]

@nak3 Am I wrong here or TestAutoscaleSustaining/aggregation-weighted-exponential is becoming an issue (used to be flaky)?

[skonto]

/retest

[skonto]

/retest

[skonto]

error: failed to create configmap: Post "https://api.ci-ocp-4-10-amd64-aws-us-east-1-xkxbn.hive.aws.ci.openshift.org:6443/api/v1/namespaces/openshift-serverless/configmaps?fieldManager=kubectl-create": dial tcp 3.217.227.55:6443: i/o timeout

[skonto]

/retest

[nak3]

/retest

[nak3]

Am I wrong here or TestAutoscaleSustaining/aggregation-weighted-exponential is becoming an issue (used to be flaky)?

Not sure... The daily CI has been blocked by https://coreos.slack.com/archives/CF5ANN61F/p1661301259161499 so the issue happened only yesterday's CI env or something.

[serverless-qe]

OCF Webhook is merging this PR