-
Notifications
You must be signed in to change notification settings - Fork 43
Wait for StorageCluster to be ready #649
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.
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
Conversation
WalkthroughA 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 Changes
Suggested reviewers
Poem
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (2)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 49s |
There was a problem hiding this 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
Thenamecould 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 descriptiveregistervariable naming
The registration variable_of_scuses 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 likestoragecluster_info:- register: _of_sc + register: storagecluster_info
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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)
7905fb6 to
690fd22
Compare
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 52s |
|
recheck |
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 46s |
|
recheck |
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 56s |
690fd22 to
3ddf01a
Compare
|
recheck |
|
from change #649:
|
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 51s |
|
recheck |
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 46s |
Co-authored-by: Tony Garcia <[email protected]>
|
recheck |
|
from change #649:
|
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 47s |
|
from change #649: |
|
recheck |
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 50s |
|
from change #649: |
|
retest |
|
from change #649: |
|
recheck |
|
Build succeeded. ✔️ dci-rpm-build-el8 SUCCESS in 2m 53s |
|
from change #649: |
|
retest |
|
from change #649: |
SUMMARY
ISSUE TYPE
Tests
Test-hints: no-check