Skip to content

Conversation

@alanconway
Copy link

@alanconway alanconway commented Dec 19, 2025

Which issue(s) this PR fixes: Fixes LOG-8153

@openshift-ci openshift-ci bot requested review from btaani and shwetaap December 19, 2025 17:38
@openshift-ci
Copy link

openshift-ci bot commented Dec 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanconway

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 19, 2025
@alanconway alanconway changed the title **What this PR does / why we need it**: Creates AGENTS.md Creates AGENTS.md Dec 19, 2025
@alanconway
Copy link
Author

@xperimental updated with an "Operator deep dive" section to focus on the operator.

@alanconway
Copy link
Author

Updated with separate AGENTS.md in operators subdirectory, mentioned and linked from root AGENTS.md. AFAIK models will follow such a link. @xperimental thoughts?

@alanconway
Copy link
Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Jan 5, 2026

@alanconway: The following test 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/test-operator 4054667 link true /test test-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.

@alanconway
Copy link
Author

Seems to be failing due to resource issues, any idea how to fix?

   *[2026-01-05T17:38:06Z]NoClusters: No clusters in pool are ready to be claimed 
INFO[2026-01-05T18:38:06Z] Releasing cluster claims for test test-operator 
INFO[2026-01-05T18:38:06Z] Ran for 1h29m10s                             
ERRO[2026-01-05T18:38:06Z] Some steps failed:                           
ERRO[2026-01-05T18:38:06Z] 
  * could not run steps: step test-operator failed: failed to wait for the created cluster claim to become ready: timed out waiting for the condition 
INFO[2026-01-05T18:38:06Z] Reporting job state 'failed' with reason 'executing_graph:step_failed:utilizing_cluster_claim:acquiring_cluster_claim'

@xperimental
Copy link

I'm taking my first looks at this now ... I think a good first step would be to focus on the operator only and remove the modification to the upper-level project. We're only interested in the operator.

Was the AGENTS.md file in the operator directory generated or have you written/checked the content yourself? I'm trying to figure out how much I can trust the content of that file.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants