Skip to content

Add wait time to extract artifacts task #650

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

rajchiluveru
Copy link
Contributor

@rajchiluveru rajchiluveru commented Apr 17, 2025

SUMMARY

This change is to allow wait time through retries for extract artifacts from release image

ISSUE TYPE

Enhanced feature

Tests
  • TestBos2Sno: sno

Summary by CodeRabbit

  • Enhancements
    • Improved the reliability of artifact extraction by adding automatic retry logic, reducing the chance of failures during the process.

@rajchiluveru rajchiluveru requested a review from a team as a code owner April 17, 2025 09:38
Copy link
Contributor

coderabbitai bot commented Apr 17, 2025

Walkthrough

The change introduces retry logic to the "Extract artifacts from release image" task within the Ansible playbook. The task now registers the extraction result, and if it fails, it will automatically retry up to three times with a 60-second delay between attempts. This adjustment enhances the reliability of the extraction process by handling transient failures.

Changes

File(s) Change Summary
roles/sno_installer/tasks/10_get_oc.yml Added retry logic to the "Extract artifacts from release image" task, registering results and retrying up to 3 times with a 60-second delay on failure.

Poem

A hop, a skip, a try again,
If at first we fail, we mend.
Three leaps more, with time to spare,
Artifacts extracted with extra care.
In the warren of code, we never tire,
For every retry takes us higher! 🐇✨

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.

🪧 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.

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: 0

🧹 Nitpick comments (1)
roles/sno_installer/tasks/10_get_oc.yml (1)

98-101: Consider parameterizing retries and using an explicit success check
To make these settings more flexible and improve readability, extract retries and delay into role defaults and switch the until to check result_extract.rc == 0. For example:

In defaults/main.yml:

artifact_extract_retries: 3
artifact_extract_delay: 60

Proposed diff:

-    register: result_extract
-    retries: 3
-    delay: 60
-    until: result_extract is not failed
+    register: result_extract
+    retries: "{{ artifact_extract_retries }}"
+    delay: "{{ artifact_extract_delay }}"
+    until: result_extract.rc == 0
📜 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 5b31561.

📒 Files selected for processing (1)
  • roles/sno_installer/tasks/10_get_oc.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Sanity Check (stable-2.9)
  • GitHub Check: Ansible-lint Check
  • GitHub Check: Sanity Check (stable-2.17)
🔇 Additional comments (1)
roles/sno_installer/tasks/10_get_oc.yml (1)

98-101: Robust retry mechanism added for artifact extraction
By registering the command result and retrying up to 3 times with a 60‑second delay, transient failures during artifact extraction will be handled automatically, improving reliability.

Copy link

@dcibot
Copy link
Collaborator

dcibot commented Apr 17, 2025

Copy link
Contributor

@ramperher ramperher left a comment

Choose a reason for hiding this comment

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

Looks like the retries are not really helping, according to the last DCI job:

https://www.distributed-ci.io/jobs/36f8123b-0713-4807-9680-74f070981f17/jobStates?sort=date&task=ac7ec125-5d49-4de6-902d-d71588aec5b9

task path: /var/lib/dci-openshift-agent/github/ansible-collection-redhatci-ocp-pr650-e3ae71b34cc1f90115f1927ef0b766c3/collections/ansible_collections/redhatci/ocp/roles/sno_installer/tasks/10_get_oc.yml:89
FAILED - RETRYING: Extract artifacts from release image (3 retries left).
FAILED - RETRYING: Extract artifacts from release image (2 retries left).
FAILED - RETRYING: Extract artifacts from release image (1 retries left).
fatal: [server06-sno.partnerci.bos2.lab -> server06-sno.partnerci.bos2.lab]: FAILED! => {"attempts": 3, "changed": true, "cmd": ["/tmp/sno_oc.l0alte68/oc", "adm", "release", "extract", "--registry-config", "/opt/cache/pull-secret.txt", "--tools", "--from", "registry.ci.openshift.org/ocp/release@sha256:a3c9dbafda0babdfdcafcebb083cbc7040a8422b22b9f0d341e9e8a7e939739f", "--to", "/opt/cache/4.18.0-0.nightly-2025-04-15-161728"], "delta": "0:00:00.319923", "end": "2025-04-17 06:08:33.104692", "msg": "non-zero return code", "rc": 1, "start": "2025-04-17 06:08:32.784769", "stderr": "error: image \"registry.ci.openshift.org/ocp/release@sha256:a3c9dbafda0babdfdcafcebb083cbc7040a8422b22b9f0d341e9e8a7e939739f\" not found: manifest unknown: manifest unknown", "stderr_lines": ["error: image \"registry.ci.openshift.org/ocp/release@sha256:a3c9dbafda0babdfdcafcebb083cbc7040a8422b22b9f0d341e9e8a7e939739f\" not found: manifest unknown: manifest unknown"], "stdout": "", "stdout_lines": []}

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