Skip to content

Conversation

@betoredhat
Copy link
Contributor

@betoredhat betoredhat commented Apr 16, 2025

SUMMARY
  • StorageCluster takes around 10 minutes to reconcile
  • Use full device ID in the hosts template
ISSUE TYPE
  • Nominal change
Tests

Test-hints: no-check

@betoredhat betoredhat requested a review from a team as a code owner April 16, 2025 19:19
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 16, 2025

Walkthrough

A new task was appended to the OpenShift storage operator playbook to implement a wait mechanism that ensures the StorageCluster resource reaches the "Ready" phase before the playbook proceeds. The task employs the kubernetes.core.k8s_info module to repeatedly query the status of the StorageCluster, retrying up to 40 times with 30-second intervals, and only continues once the resource is confirmed to be ready. Additionally, a template file was updated to modify the value of the local_storage_devices variable when local storage operator (LSO) is enabled, changing the device identifier string used.

Changes

File(s) Change Summary
roles/odf_setup/tasks/openshift-storage-operator.yml Added a task to wait for the StorageCluster resource to reach the "Ready" phase using retries.
roles/ocp_on_libvirt/templates/hosts.j2 Modified the local_storage_devices variable value when enable_lso is true to a different device string.

Suggested reviewers

  • manurodriguez

Poem

A cluster waits, the playbook stalls,
For "Ready" status in the storage halls.
Forty checks, with patience true,
Thirty seconds, then retry anew.
When all is set, the tasks resume—
The rabbit hops, no hint of gloom!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3ddf01a and e531138.

📒 Files selected for processing (1)
  • roles/odf_setup/tasks/openshift-storage-operator.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • roles/odf_setup/tasks/openshift-storage-operator.yml
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Sanity Check (stable-2.17)
  • GitHub Check: Sanity Check (stable-2.9)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@softwarefactory-project-zuul
Copy link

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (2)
roles/odf_setup/tasks/openshift-storage-operator.yml (2)

84-84: Task name grammar and clarity refinement
The name could be more grammatically clear and align with other task names. For example:

- name: Wait up to 20 mins Storage Cluster to be ready
+ name: Wait for StorageCluster to be ready (up to 20 minutes)

90-92: Consistent and descriptive register variable naming
The registration variable _of_sc uses a leading underscore and an abbreviation that may be less readable. For consistency with earlier tasks (e.g., ocs_health_status), consider renaming it to something like storagecluster_info:

-  register: _of_sc
+  register: storagecluster_info
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 82d25a8 and 7905fb6.

📒 Files selected for processing (1)
  • roles/odf_setup/tasks/openshift-storage-operator.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Sanity Check (stable-2.17)
  • GitHub Check: Sanity Check (stable-2.9)

@betoredhat betoredhat force-pushed the wait_storagecluster branch from 7905fb6 to 690fd22 Compare April 16, 2025 19:32
@softwarefactory-project-zuul
Copy link

@betoredhat
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link

@betoredhat
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link

@betoredhat betoredhat force-pushed the wait_storagecluster branch from 690fd22 to 3ddf01a Compare April 16, 2025 21:39
@betoredhat
Copy link
Contributor Author

recheck

@dcibot
Copy link
Collaborator

dcibot commented Apr 16, 2025

from change #649:

  • ERROR no DCI job found

@softwarefactory-project-zuul
Copy link

@betoredhat
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link

@betoredhat
Copy link
Contributor Author

recheck

@dcibot
Copy link
Collaborator

dcibot commented Apr 16, 2025

from change #649:

  • ERROR no DCI job found

@softwarefactory-project-zuul
Copy link

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

@betoredhat
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

@tonyskapunk
Copy link
Contributor

retest

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

@betoredhat
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

@tonyskapunk
Copy link
Contributor

retest

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

@tonyskapunk tonyskapunk added this pull request to the merge queue Apr 17, 2025
Merged via the queue into main with commit e15b136 Apr 17, 2025
8 checks passed
@tonyskapunk tonyskapunk deleted the wait_storagecluster branch April 17, 2025 17:14
@coderabbitai coderabbitai bot mentioned this pull request Sep 11, 2025
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.

4 participants