Skip to content

MGMT-20659: Select virtualization bundle and LVM operator when user came from Assisted Migration wizard#2953

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ammont82:MGMT-20659-changes-related-with-assisted-migration
May 21, 2025
Merged

MGMT-20659: Select virtualization bundle and LVM operator when user came from Assisted Migration wizard#2953
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ammont82:MGMT-20659-changes-related-with-assisted-migration

Conversation

@ammont82
Copy link
Member

@ammont82 ammont82 commented May 20, 2025

Related with https://issues.redhat.com/browse/MGMT-20659

When we go to cluster creating wizard with the parameter "source=assisted_migration" (openshift/assisted-installer/clusters/~new?source=assisted_migration) we select the Virtualization bundle by default and the LVMS operator.

image

Summary by CodeRabbit

  • Bug Fixes

    • Improved cluster creation flow for assisted migration scenarios, ensuring the correct operator is added and UI settings are updated appropriately.
  • Chores

    • Removed legacy logic and provisional YAML resources related to assisted migration manifests, streamlining the cluster configuration process.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 20, 2025

@ammont82: This pull request references MGMT-20659 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Related with https://issues.redhat.com/browse/MGMT-20659

When we go to cluster creating wizard with the parameter "source=assisted_migration" (openshift/assisted-installer/clusters/~new?source=assisted_migration) we select the Virtualization bundle by default and the LVMS operator.

image

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from celdrake and jgyselov May 20, 2025 13:54
@ammont82 ammont82 added this to the v2.41 milestone May 20, 2025
@coderabbitai
Copy link

coderabbitai bot commented May 20, 2025

Walkthrough

This change removes provisional assisted migration logic from the codebase. It deletes the creation and injection of custom manifests for assisted migration, eliminates related YAML constants, and updates the cluster creation flow to select a virtualization bundle instead. The affected logic spans cluster configuration, cluster creation, constants, and service layers.

Changes

File(s) Change Summary
libs/ui-lib/lib/ocm/components/clusterConfiguration/CustomManifestCheckbox.tsx Removed useLocation import and effect for auto-enabling custom manifest on assisted migration URLs.
libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx Updated handleClusterCreate to add LVM operator and select virtualization bundle for assisted migration.
libs/ui-lib/lib/ocm/config/constants.ts Removed exported YAML constants for assisted migration manifests.
libs/ui-lib/lib/ocm/services/ClustersService.ts Removed createClusterManifestsForAssistedMigration method and related imports.

Poem

A bunny hopped through code so wide,
Sweeping old migration tricks aside.
No more YAML stacks to juggle,
Just bundles now—less code to struggle!
With lighter paws and simpler cheer,
The cluster’s path is crystal clear.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "@openshift-assisted/eslint-config" to extend from. Please check that the name of the config is correct.

The config "@openshift-assisted/eslint-config" was referenced from the config file in "/libs/ui-lib/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

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

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.

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 20, 2025

@ammont82: This pull request references MGMT-20659 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Related with https://issues.redhat.com/browse/MGMT-20659

When we go to cluster creating wizard with the parameter "source=assisted_migration" (openshift/assisted-installer/clusters/~new?source=assisted_migration) we select the Virtualization bundle by default and the LVMS operator.

image

Summary by CodeRabbit

  • Bug Fixes

  • Improved cluster creation flow for assisted migration scenarios, ensuring the correct operator is added and UI settings are updated appropriately.

  • Chores

  • Removed legacy logic and provisional YAML resources related to assisted migration manifests, streamlining the cluster configuration process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link

@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 (2)
libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx (2)

78-81: Fix comment formatting and consider preserving existing operators

The comment has a grammatical error. Additionally, the current implementation might override any existing olmOperators in the params object rather than adding to them.

-        //For Assisted Migration we need to LVMs operator
+        // For Assisted Migration we need to add the LVM operator
         if (isAssistedMigration) {
-          params.olmOperators = [{ name: 'lvm' }];
+          params.olmOperators = params.olmOperators ? [...params.olmOperators, { name: 'lvm' }] : [{ name: 'lvm' }];
         }

85-88: Fix comment formatting

The comment should follow consistent formatting standards with space after //.

-        //For Assisted Migration we need to enable virtualization bundle
+        // For Assisted Migration we need to enable virtualization bundle
         if (isAssistedMigration) {
           await UISettingService.update(cluster.id, { bundlesSelected: ['virtualization'] });
         }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between e596899 and e74d68d.

📒 Files selected for processing (4)
  • libs/ui-lib/lib/ocm/components/clusterConfiguration/CustomManifestCheckbox.tsx (0 hunks)
  • libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx (1 hunks)
  • libs/ui-lib/lib/ocm/config/constants.ts (0 hunks)
  • libs/ui-lib/lib/ocm/services/ClustersService.ts (0 hunks)
💤 Files with no reviewable changes (3)
  • libs/ui-lib/lib/ocm/components/clusterConfiguration/CustomManifestCheckbox.tsx
  • libs/ui-lib/lib/ocm/config/constants.ts
  • libs/ui-lib/lib/ocm/services/ClustersService.ts
🧰 Additional context used
🧬 Code Graph Analysis (1)
libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx (1)
libs/ui-lib/lib/ocm/components/clusterWizard/wizardTransition.ts (1)
  • ClusterWizardFlowStateNew (48-48)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: translation-files
  • GitHub Check: tests
  • GitHub Check: unit-tests
  • GitHub Check: lint
  • GitHub Check: format
  • GitHub Check: circular-deps
🔇 Additional comments (1)
libs/ui-lib/lib/ocm/components/clusterWizard/ClusterDetails.tsx (1)

72-99:

Details

✅ Verification successful

Verify parameter propagation to ClustersService.create()

The code correctly implements the requirements by adding LVM operator and enabling the virtualization bundle. However, I'd like to verify that the isAssistedMigration parameter is correctly used in the ClustersService.create() method.


🏁 Script executed:

#!/bin/bash
# Search for ClustersService.create implementation to verify how isAssistedMigration is used
rg -A 10 "create\s*\(\s*params.*isAssistedMigration" --type ts

Length of output: 2481


ClustersService.create correctly handles isAssistedMigration
Confirmed that when isAssistedMigration is true, ClustersService.create adds the AI_ASSISTED_MIGRATION_TAG to params.tags before calling the API. No further changes needed.

@ammont82
Copy link
Member Author

/cherry-pick releases/v2.41

@openshift-cherrypick-robot
Copy link
Contributor

@ammont82: once the present PR merges, I will cherry-pick it on top of releases/v2.41 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick releases/v2.41

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
@openshift-ci
Copy link

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, celdrake

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 9db44ae into openshift-assisted:master May 21, 2025
11 checks passed
@openshift-cherrypick-robot
Copy link
Contributor

@ammont82: new pull request created: #2954

Details

In response to this:

/cherry-pick releases/v2.41

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants