Skip to content

Conversation

barbacbd
Copy link

@barbacbd barbacbd commented Sep 4, 2025

** Go Get update on openshift/api. github.com/openshift/api v0.0.0-20250806102053-6a7223edb2fc ** Go mod vendor (requires updates to numerous packages).

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 4, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 4, 2025

@barbacbd: This pull request references CORS-4204 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.21.0" version, but no target version was set.

In response to this:

** Go Get update on openshift/api. github.com/openshift/api v0.0.0-20250806102053-6a7223edb2fc ** Go mod vendor (requires updates to numerous packages).

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.

@barbacbd
Copy link
Author

barbacbd commented Sep 4, 2025

/cc @flavianmissi

@barbacbd
Copy link
Author

barbacbd commented Sep 4, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 4, 2025
** Go Get update on openshift/api. github.com/openshift/api v0.0.0-20250806102053-6a7223edb2fc ** Go mod vendor (requires updates to numerous packages).
@barbacbd barbacbd force-pushed the gcp_custom_endpoint branch from d9c4fe9 to 8b5e82e Compare September 4, 2025 19:04
@barbacbd
Copy link
Author

barbacbd commented Sep 4, 2025

/hold cancel

@barbacbd barbacbd closed this Sep 4, 2025
@barbacbd barbacbd reopened this Sep 4, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 4, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 4, 2025

@barbacbd: This pull request references CORS-4204 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.21.0" version, but no target version was set.

In response to this:

** Go Get update on openshift/api. github.com/openshift/api v0.0.0-20250806102053-6a7223edb2fc ** Go mod vendor (requires updates to numerous packages).

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.

@barbacbd barbacbd force-pushed the gcp_custom_endpoint branch from 8e0328d to fa0d4cf Compare September 5, 2025 10:59
** Add Clock to the `configv1helpers.SetStatusCondition`, because the number of arguments
changed to 3 to include a clock. RealClock{} is passed.
@barbacbd barbacbd force-pushed the gcp_custom_endpoint branch from fa0d4cf to b14707d Compare September 5, 2025 12:31
** Pass the feature gates to the GCS driver.
** Search for the correct featuregate and grab the service endpoints. When the endpoint for
the storage api is provided, then use the endpoint to override the endpoint when the client is
created.
** Update tests to include fake feature gate information.

pkg/storage/swift:
** Update test to stop complaining about bad string formatting.
@barbacbd barbacbd force-pushed the gcp_custom_endpoint branch from b14707d to f666b47 Compare September 5, 2025 17:54
@barbacbd
Copy link
Author

barbacbd commented Sep 8, 2025

/retest-required

1 similar comment
@barbacbd
Copy link
Author

barbacbd commented Sep 8, 2025

/retest-required

@flavianmissi
Copy link
Member

it looks like more tests have become flaky in the e2e-*-operator suite, particularly the TestScaleUp.
I'm hoping a couple more retests can help them pass 🤞🏼

/retest

@barbacbd
Copy link
Author

barbacbd commented Sep 9, 2025

/test e2e-gcp-operator

@barbacbd
Copy link
Author

barbacbd commented Sep 9, 2025

/retets-required

@barbacbd
Copy link
Author

/retest-required

1 similar comment
@barbacbd
Copy link
Author

/retest-required

@flavianmissi
Copy link
Member

/test e2e-gcp-operator
/test e2e-aws-operator

@flavianmissi
Copy link
Member

TestScaleUp is consistently failing on gcp. The image-registry operator is going degraded:

          - lastTransitionTime: "2025-09-12T14:44:10Z"
            message: 'Registry deployment has timed out progressing: ReplicaSet "image-registry-689fc5dcc"
              has timed out progressing.'
            reason: ProgressDeadlineExceeded
            status: "True"
            type: Degraded

As far as I can tell this test is perma-failing on gcp and azure. It's extremely flaky on aws but it does pass there.

I triggered the e2e-gcp-operator from another PR to see if the issue shows up there as well: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-image-registry-operator/1257/pull-ci-openshift-cluster-image-registry-operator-main-e2e-gcp-operator/1967513228040736768

I'll override these tests if we observe them failing on other PRs too.

@flavianmissi
Copy link
Member

These operator tests are flaking more and more :( The one I ran on a different PR also failed on TestScaleUp. We need to open a tracker on jira and look into it.

I'll override the test here so we can unblock this PR.
/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-gcp-operator
/override ci/prow/e2e-azure-operator

Copy link
Contributor

openshift-ci bot commented Sep 18, 2025

@flavianmissi: Overrode contexts on behalf of flavianmissi: ci/prow/e2e-aws-operator, ci/prow/e2e-azure-operator, ci/prow/e2e-gcp-operator

In response to this:

These operator tests are flaking more and more :( The one I ran on a different PR also failed on TestScaleUp. We need to open a tracker on jira and look into it.

I'll override the test here so we can unblock this PR.
/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-gcp-operator
/override ci/prow/e2e-azure-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-sigs/prow repository.

@flavianmissi
Copy link
Member

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 18, 2025
@barbacbd
Copy link
Author

/verifed by ci/prow/e2e-gcp-ovn

@patrickdillon
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2025
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd, flavianmissi, patrickdillon

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:

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

@flavianmissi
Copy link
Member

installer docs should cover the changes in here. since this change is an extension of platform functionality I don't think we need to involve IR PX either.

/label px-approved
/label docs-approved

@xiuwang could you please help with verification?

@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Sep 23, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 1, 2025
Copy link
Contributor

openshift-ci bot commented Oct 1, 2025

New changes are detected. LGTM label has been removed.

Copy link
Contributor

openshift-ci bot commented Oct 1, 2025

@barbacbd: 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/okd-scos-e2e-aws-ovn b567dee link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-ovn b567dee link false /test e2e-gcp-ovn
ci/prow/e2e-azure-operator b567dee link false /test e2e-azure-operator
ci/prow/verify b567dee link true /test verify
ci/prow/e2e-gcp-operator b567dee link false /test e2e-gcp-operator
ci/prow/e2e-openstack b567dee link false /test e2e-openstack
ci/prow/e2e-vsphere-operator b567dee link true /test e2e-vsphere-operator
ci/prow/verify-deps b567dee link true /test verify-deps
ci/prow/e2e-aws-operator b567dee link true /test e2e-aws-operator

Full PR test history. Your PR dashboard.

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. px-approved Signifies that Product Support has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants