Skip to content

fix: revert oc download from cluster#364

Closed
lugi0 wants to merge 2 commits intoopendatahub-io:mainfrom
lugi0:fix/oc_revert
Closed

fix: revert oc download from cluster#364
lugi0 wants to merge 2 commits intoopendatahub-io:mainfrom
lugi0:fix/oc_revert

Conversation

@lugi0
Copy link
Copy Markdown
Contributor

@lugi0 lugi0 commented Jun 19, 2025

Description

How Has This Been Tested?

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Signed-off-by: lugi0 <lgiorgi@redhat.com>
@lugi0 lugi0 requested a review from a team as a code owner June 19, 2025 10:30
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jun 19, 2025

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the environment to include the Rosa CLI and OpenShift CLI tools.
    • Disabled certain test fixtures and related utility functions that managed CLI binaries and environment setup.

Summary by CodeRabbit

  • Chores
    • Updated the environment to include Rosa CLI and OpenShift CLI tools.
    • Disabled several test fixtures and related utility functions for managing CLI binaries and environment setup.
    • Removed unused imports associated with the disabled test and utility code.

Walkthrough

This change updates the Dockerfile to install the Rosa CLI and OpenShift CLI (oc) statically during image build. It also comments out Python code and fixtures in the test and utility modules that previously handled dynamic downloading and environment setup for the oc CLI, removing related imports as well.

Changes

Files/Paths Change Summary
Dockerfile Adds installation steps for Rosa CLI and OpenShift CLI (oc) before grpcurl installation.
tests/conftest.py Comments out all fixtures and imports related to dynamic oc CLI setup and environment management.
utilities/infra.py Comments out functions and removes imports related to dynamic oc CLI download, extraction, and platform detection.

Possibly related PRs

Suggested labels

commented-by-adolfo-ab, commented-by-lugi0, lgtm-by-lugi0

Suggested reviewers

  • lugi0
  • adolfo-ab

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38319a7 and 62a9c19.

📒 Files selected for processing (1)
  • tests/conftest.py (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • tests/conftest.py
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

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.

@lugi0
Copy link
Copy Markdown
Contributor Author

lugi0 commented Jun 19, 2025

/build-push-pr-image

@github-actions
Copy link
Copy Markdown

The following are automatically added/executed:

  • PR size label.
  • Run pre-commit
  • Run tox
  • Add PR author as the PR assignee
  • Build image based on the PR

Available user actions:

  • To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
  • To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
  • To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
    lgtm label removed on each new commit push.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
    and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
  • To build and push image to quay, add /build-push-pr-image in a comment. This would create an image with tag
    pr-<pr_number> to quay repository. This image tag, however would be deleted on PR merge or close action.
Supported labels

{'/cherry-pick', '/build-push-pr-image', '/hold', '/verified', '/wip', '/lgtm'}

@github-actions
Copy link
Copy Markdown

Status of building tag pr-364: success.
Status of pushing tag pr-364 to image registry: success.

Copy link
Copy Markdown
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: 1

🧹 Nitpick comments (1)
Dockerfile (1)

20-25: Add architecture specification for consistency and consider version pinning.

The Rosa CLI download uses a generic rosa-linux.tar.gz while the OC CLI download specifies x86_64 architecture. For consistency and to avoid potential architecture mismatches, consider specifying the architecture for Rosa CLI as well.

Additionally, using "latest" for Rosa CLI could lead to non-reproducible builds.

# Install the Rosa CLI
-RUN curl -L https://mirror.openshift.com/pub/openshift-v4/clients/rosa/latest/rosa-linux.tar.gz --output /tmp/rosa-linux.tar.gz \
+RUN curl -L https://mirror.openshift.com/pub/openshift-v4/clients/rosa/latest/rosa-linux-amd64.tar.gz --output /tmp/rosa-linux.tar.gz \
    && tar xvf /tmp/rosa-linux.tar.gz --no-same-owner \
    && mv rosa /usr/bin/rosa \
    && chmod +x /usr/bin/rosa \
+    && rm -f /tmp/rosa-linux.tar.gz \
    && rosa version
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 993a837 and 38319a7.

📒 Files selected for processing (3)
  • Dockerfile (1 hunks)
  • tests/conftest.py (1 hunks)
  • utilities/infra.py (1 hunks)
🔇 Additional comments (2)
utilities/infra.py (1)

1149-1231: Verify that commented functions are not referenced elsewhere in the codebase.

The OC CLI download functions have been properly commented out, which aligns with the shift to Docker-based CLI installation. The commenting approach (rather than deletion) allows for potential rollback if needed.

Please verify that no other parts of the codebase still reference these commented functions:

#!/bin/bash
# Description: Search for any remaining references to the commented OC CLI functions
# Expected: No active references should be found

echo "Searching for references to commented functions..."

# Search for function calls
rg -A 3 "get_machine_platform|get_os_system|get_oc_console_cli_download_link|get_server_cert|download_oc_console_cli" --type py

echo -e "\nSearching for imports of commented functions..."
rg "from.*infra.*import.*download_oc_console_cli" --type py
tests/conftest.py (1)

529-563: Verify that no tests depend on the commented fixtures.

The pytest fixtures for OC CLI binary management have been properly commented out, which is consistent with the shift to Docker-based CLI installation. The autouse_fixtures fixture that controlled execution order is also appropriately disabled.

Please verify that no test files still reference these commented fixtures:

#!/bin/bash
# Description: Search for any remaining references to the commented fixtures
# Expected: No active fixture references should be found

echo "Searching for references to commented fixtures..."

# Search for fixture usage
rg -A 2 "os_path_environment|bin_directory|bin_directory_to_os_path|oc_binary_path" --type py tests/

echo -e "\nSearching for autouse_fixtures references..."
rg "autouse_fixtures" --type py tests/

Comment on lines +27 to +31
# Install the OpenShift CLI (OC)
RUN curl -L https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/stable/openshift-client-linux.tar.gz --output /tmp/openshift-client-linux.tar.gz \
&& tar xvf /tmp/openshift-client-linux.tar.gz --no-same-owner \
&& mv oc /usr/bin/oc \
&& chmod +x /usr/bin/oc
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add verification command for OC CLI installation.

The Rosa CLI installation includes a verification step (rosa version), but the OC CLI installation lacks similar verification. This could lead to silent failures during the build process.

# Install the OpenShift CLI (OC)
RUN curl -L https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/stable/openshift-client-linux.tar.gz --output /tmp/openshift-client-linux.tar.gz \
    && tar xvf /tmp/openshift-client-linux.tar.gz --no-same-owner \
    && mv oc /usr/bin/oc \
-    && chmod +x /usr/bin/oc
+    && chmod +x /usr/bin/oc \
+    && rm -f /tmp/openshift-client-linux.tar.gz \
+    && oc version --client
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# Install the OpenShift CLI (OC)
RUN curl -L https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/stable/openshift-client-linux.tar.gz --output /tmp/openshift-client-linux.tar.gz \
&& tar xvf /tmp/openshift-client-linux.tar.gz --no-same-owner \
&& mv oc /usr/bin/oc \
&& chmod +x /usr/bin/oc
# Install the OpenShift CLI (OC)
RUN curl -L https://mirror.openshift.com/pub/openshift-v4/x86_64/clients/ocp/stable/openshift-client-linux.tar.gz --output /tmp/openshift-client-linux.tar.gz \
&& tar xvf /tmp/openshift-client-linux.tar.gz --no-same-owner \
&& mv oc /usr/bin/oc \
&& chmod +x /usr/bin/oc \
&& rm -f /tmp/openshift-client-linux.tar.gz \
&& oc version --client
🤖 Prompt for AI Agents
In Dockerfile lines 27 to 31, the OpenShift CLI (OC) installation lacks a
verification step to confirm successful installation. Add a command after
setting permissions to run `oc version` or a similar command to verify the OC
CLI is correctly installed and executable, ensuring any installation issues are
caught during the build process.

@adolfo-ab
Copy link
Copy Markdown
Contributor

/lgtm

Copy link
Copy Markdown
Contributor

@fege fege left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Copy Markdown
Contributor

@sheltoncyril sheltoncyril left a comment

Choose a reason for hiding this comment

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

/lgtm

os.chmod(binary_path, stat.S_IRUSR | stat.S_IXUSR)
return binary_path
# def get_machine_platform() -> str:
# os_machine_type = platform.machine()
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Wondering if commenting is the best way to stow away changes, I will not block it though.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Tox seems to be complaining about unused code https://github.com/opendatahub-io/opendatahub-tests/actions/runs/15758251029/job/44418477232?pr=364
I might be wrong but if true, maybe deleting this and reverting it later is the better option, else it will complain everytime Tox runs.

Copy link
Copy Markdown
Collaborator

@dbasunag dbasunag left a comment

Choose a reason for hiding this comment

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

Please don't merge the revert.

@dbasunag
Copy link
Copy Markdown
Collaborator

#366 fixes this issue.

@sheltoncyril
Copy link
Copy Markdown
Contributor

Closing this as the issue was addressed in #366

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants