Skip to content

ESO-47: Fix CI falures in external-secrets-operator-release #65277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

ESO-47: Fix CI falures in external-secrets-operator-release #65277

wants to merge 1 commit into from

Conversation

bharath-b-rh
Copy link
Contributor

@bharath-b-rh bharath-b-rh commented May 22, 2025 •
edited
Loading

Fix for below error observed in CI runs

ERRO[2025-05-22T14:57:24Z] Some steps failed:                           
ERRO[2025-05-22T14:57:24Z] 
  * could not sort nodes
  * steps are missing dependencies
  * step src is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"root", unsatisfiableError:""}>
  * step verify is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"src", unsatisfiableError:""}> 
INFO[2025-05-22T[14](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_external-secrets-operator-release/15/pull-ci-openshift-external-secrets-operator-release-main-verify/1925566646336884736#1:build-log.txt%3A14):57:24Z] Reporting job state 'failed' with reason 'building_graph' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown'

Ref: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_external-secrets-operator-release/15/pull-ci-openshift-external-secrets-operator-release-main-verify/1925566646336884736

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

openshift-ci-robot commented May 22, 2025 •
edited by openshift-ci bot
Loading

@bharath-b-rh: This pull request references ESO-47 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.20.0" version, but no target version was set.

In response to this:

Fix for below error observed in CI runs

ERRO[2025-05-22T14:57:24Z] Some steps failed:                           
ERRO[2025-05-22T14:57:24Z] 
 * could not sort nodes
 * steps are missing dependencies
 * step src is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"root", unsatisfiableError:""}>
 * step verify is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"src", unsatisfiableError:""}> 
INFO[2025-05-22T[14](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_external-secrets-operator-release/15/pull-ci-openshift-external-secrets-operator-release-main-verify/1925566646336884736#1:build-log.txt%3A14):57:24Z] Reporting job state 'failed' with reason 'building_graph' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown'

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.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2025 •
edited by openshift-ci bot
Loading

@bharath-b-rh: This pull request references ESO-47 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.20.0" version, but no target version was set.

In response to this:

Fix for below error observed in CI runs

ERRO[2025-05-22T14:57:24Z] Some steps failed:                           
ERRO[2025-05-22T14:57:24Z] 
 * could not sort nodes
 * steps are missing dependencies
 * step src is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"root", unsatisfiableError:""}>
 * step verify is missing dependencies: <&api.internalImageStreamTagLink{name:"pipeline", tag:"src", unsatisfiableError:""}> 
INFO[2025-05-22T[14](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_external-secrets-operator-release/15/pull-ci-openshift-external-secrets-operator-release-main-verify/1925566646336884736#1:build-log.txt%3A14):57:24Z] Reporting job state 'failed' with reason 'building_graph' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown' 
INFO[2025-05-22T14:57:24Z] Reporting job state 'failed' with reason 'unknown'

Ref: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_external-secrets-operator-release/15/pull-ci-openshift-external-secrets-operator-release-main-verify/1925566646336884736

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.

@bharath-b-rh
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bharath-b-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci bot requested review from swghosh and TrilokGeer May 22, 2025 15:15
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 22, 2025
@bharath-b-rh
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bharath-b-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@bharath-b-rh
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@bharath-b-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@bharath-b-rh: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-external-secrets-operator-release-release-0.1-verify openshift/external-secrets-operator-release presubmit Ci-operator config changed
pull-ci-openshift-external-secrets-operator-release-main-verify openshift/external-secrets-operator-release presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 23, 2025

@bharath-b-rh: 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/rehearse/openshift/external-secrets-operator-release/main/verify efbda31 link unknown /pj-rehearse pull-ci-openshift-external-secrets-operator-release-main-verify
ci/rehearse/openshift/external-secrets-operator-release/release-0.1/verify efbda31 link unknown /pj-rehearse pull-ci-openshift-external-secrets-operator-release-release-0.1-verify

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
Reviewers

@swghosh swghosh Awaiting requested review from swghosh

@TrilokGeer TrilokGeer Awaiting requested review from TrilokGeer

Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@bharath-b-rh @openshift-ci-robot