Skip to content

ci: fix failing go-tests#401

Merged
subhamkrai merged 2 commits intorook:masterfrom
ShravaniVangur:test-ci-errors
Oct 22, 2025
Merged

ci: fix failing go-tests#401
subhamkrai merged 2 commits intorook:masterfrom
ShravaniVangur:test-ci-errors

Conversation

@ShravaniVangur
Copy link
Contributor

The PR addresses the CI test failures.

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Reviewed the developer guide on Submitting a Pull Request
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

@subhamkrai
Copy link
Collaborator

@ShravaniVangur could try this

  1. deleting the rook-ceph-operator pod or we can re-start the rook-ceph-operator pod,
  2. wait for rook-ceph-operator pod to be in running state
  3. then check for radosnamespace readiness

I noticed, restarting rook-ceph-operator pod, helped.

subhamkrai and others added 2 commits October 22, 2025 13:45
Signed-off-by: subhamkrai <srai@redhat.com>
Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
Copy link
Collaborator

@subhamkrai subhamkrai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great to see CI working. Thanks for the PR

@subhamkrai subhamkrai merged commit e894ee0 into rook:master Oct 22, 2025
6 checks passed
@subhamkrai subhamkrai mentioned this pull request Oct 22, 2025
5 tasks
@@ -274,11 +276,16 @@ wait_for_deployment_to_be_running() {

wait_for_crd_to_be_ready() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The function name seems wrong, it should be wait for ceph_cluster_to_be_ready instead of crd_to_be_ready

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll create a separate PR to fix this.

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.

3 participants