Skip to content

MGMT-20351: selecting CNV - not able to deselect it using UI#2906

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ElayAharoni:selecting-CNV--not-able-to-deselect-it-using-UI
Apr 9, 2025
Merged

MGMT-20351: selecting CNV - not able to deselect it using UI#2906
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
ElayAharoni:selecting-CNV--not-able-to-deselect-it-using-UI

Conversation

@ElayAharoni
Copy link
Contributor

@ElayAharoni ElayAharoni commented Apr 9, 2025

https://issues.redhat.com/browse/MGMT-20351
after the change the CNV operator is disabled by default until we select the MTV operator because right now the CNV operator can be selected only when selecting the MTV as well.
and then it will be automatically checked but if user wants it can remove the CNV operator and remain only with MTV.

https://www.loom.com/share/3f15f5622457465da194b51c56f3d3d9?sid=1fb93a91-fb97-4db8-9408-1239766b9b7e

Summary by CodeRabbit

  • Refactor

    • Streamlined the logic for determining CNV availability based solely on the Migration Toolkit for Virtualization.
  • New Features

    • Added a method to the operators page for interacting with the Migration Toolkit for Virtualization checkbox.
  • Tests

    • Updated test sequences to include interaction with the Migration Toolkit for Virtualization during cluster update checks.

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

openshift-ci-robot commented Apr 9, 2025

@ElayAharoni: This pull request references MGMT-20351 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/MGMT-20351
after the change the CNV operator is disabled by default until we select the MTV operator because right now the CNV operator can be selected only when selecting the MTV as well.
and then it will be automatically checked but if user wants it can remove the CNV operator and remain only with MTV.

https://www.loom.com/share/3f15f5622457465da194b51c56f3d3d9?sid=1fb93a91-fb97-4db8-9408-1239766b9b7e

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 rawagner April 9, 2025 12:37
@coderabbitai
Copy link

coderabbitai bot commented Apr 9, 2025

Walkthrough

The function getCnvDisabledWithMtvReason in featureStateUtils.ts has been simplified. The conditional logic was reduced to check only for the absence of the Migration Toolkit for Virtualization (!operatorValues.useMigrationToolkitforVirtualization) to determine if CNV should be disabled. The redundant check for operatorValues.useContainerNativeVirtualization was removed, while the original return message remains unchanged. The function signature is preserved. Additionally, a new method migrationToolkitForVirtualization was added to the operatorsPage object, and a test case was updated to include interaction with the migration toolkit.

Changes

File(s) Change Summary
libs/ui-lib/.../featureSupportLevels/featureStateUtils.ts Simplified the conditional logic in getCnvDisabledWithMtvReason by removing the check for useContainerNativeVirtualization, now only verifying the absence of MTV.
libs/ui-lib-tests/cypress/views/operatorsPage.ts Added method migrationToolkitForVirtualization to retrieve a checkbox element for the migration toolkit for virtualization.
libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts Updated test case to include interaction with the migration toolkit for virtualization by adding a click action before proceeding with other operations.

Sequence Diagram(s)

sequenceDiagram
    participant Caller as Caller
    participant FS as getCnvDisabledWithMtvReason
    Caller->>+FS: call(operatorValues)
    Note right of FS: Check if !useMigrationToolkitforVirtualization
    FS-->>-Caller: Return CNV disable reason message
Loading

Poem

I'm just a rabbit, coding through the night,
Hopping over conditions with pure delight.
Removed a check, now the logic is light,
Fewer twists in the code, everything feels right.
Carrots and clean code, both a beautiful sight!

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/featureSupportLevels/featureStateUtils.ts

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.


📜 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 2bbd16c and 09b2154.

📒 Files selected for processing (3)
  • libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts (1 hunks)
  • libs/ui-lib-tests/cypress/views/operatorsPage.ts (1 hunks)
  • libs/ui-lib/lib/ocm/components/featureSupportLevels/featureStateUtils.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • libs/ui-lib-tests/cypress/views/operatorsPage.ts
  • libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts
  • libs/ui-lib/lib/ocm/components/featureSupportLevels/featureStateUtils.ts
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: tests
  • GitHub Check: translation-files
  • GitHub Check: lint
  • GitHub Check: unit-tests
  • GitHub Check: circular-deps
  • GitHub Check: format

🪧 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 plan to trigger planning for file edits and PR creation.
  • @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 the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 9, 2025

@ElayAharoni: This pull request references MGMT-20351 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/MGMT-20351
after the change the CNV operator is disabled by default until we select the MTV operator because right now the CNV operator can be selected only when selecting the MTV as well.
and then it will be automatically checked but if user wants it can remove the CNV operator and remain only with MTV.

https://www.loom.com/share/3f15f5622457465da194b51c56f3d3d9?sid=1fb93a91-fb97-4db8-9408-1239766b9b7e

Summary by CodeRabbit

  • Refactor
  • Streamlined the backend logic used to determine virtualization feature availability, ensuring a consistent messaging experience regarding installation requirements.

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.

@ElayAharoni ElayAharoni force-pushed the selecting-CNV--not-able-to-deselect-it-using-UI branch from 6fe538f to 2bbd16c Compare April 9, 2025 13:18
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 9, 2025

@ElayAharoni: This pull request references MGMT-20351 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/MGMT-20351
after the change the CNV operator is disabled by default until we select the MTV operator because right now the CNV operator can be selected only when selecting the MTV as well.
and then it will be automatically checked but if user wants it can remove the CNV operator and remain only with MTV.

https://www.loom.com/share/3f15f5622457465da194b51c56f3d3d9?sid=1fb93a91-fb97-4db8-9408-1239766b9b7e

Summary by CodeRabbit

  • Refactor

  • Streamlined the logic for determining CNV availability based solely on the Migration Toolkit for Virtualization.

  • New Features

  • Added a method to the operators page for interacting with the Migration Toolkit for Virtualization checkbox.

  • Tests

  • Updated test sequences to include interaction with the Migration Toolkit for Virtualization during cluster update checks.

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6fe538f and 2bbd16c.

📒 Files selected for processing (3)
  • libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts (1 hunks)
  • libs/ui-lib-tests/cypress/views/operatorsPage.ts (1 hunks)
  • libs/ui-lib/lib/ocm/components/featureSupportLevels/featureStateUtils.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • libs/ui-lib/lib/ocm/components/featureSupportLevels/featureStateUtils.ts
🧰 Additional context used
🧬 Code Graph Analysis (1)
libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts (1)
libs/ui-lib-tests/cypress/views/operatorsPage.ts (1)
  • operatorsPage (1-11)
🪛 Biome (1.9.4)
libs/ui-lib-tests/cypress/views/operatorsPage.ts

[error] 5-5: Did you mean to use a :? An = can only follow a property name when the containing object literal is part of a destructuring pattern.

(parse)

🔇 Additional comments (1)
libs/ui-lib-tests/cypress/integration/ui-behaviour/cluster-updates.cy.ts (1)

40-40: LGTM: Test update aligns with CNV dependency on MTV

The test has been correctly updated to click the Migration Toolkit for Virtualization checkbox before attempting to enable OpenShift Virtualization, which aligns with the PR objective where "CNV operator is now disabled by default until the MTV operator is selected."

Signed-off-by: Elay Aharoni <elayaha@gmail.com>
@ElayAharoni ElayAharoni force-pushed the selecting-CNV--not-able-to-deselect-it-using-UI branch from 2bbd16c to 09b2154 Compare April 9, 2025 13:22
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 9, 2025

@ElayAharoni: This pull request references MGMT-20351 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 bug to target the "4.19.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/MGMT-20351
after the change the CNV operator is disabled by default until we select the MTV operator because right now the CNV operator can be selected only when selecting the MTV as well.
and then it will be automatically checked but if user wants it can remove the CNV operator and remain only with MTV.

https://www.loom.com/share/3f15f5622457465da194b51c56f3d3d9?sid=1fb93a91-fb97-4db8-9408-1239766b9b7e

Summary by CodeRabbit

  • Refactor

  • Streamlined the logic for determining CNV availability based solely on the Migration Toolkit for Virtualization.

  • New Features

  • Added a method to the operators page for interacting with the Migration Toolkit for Virtualization checkbox.

  • Tests

  • Updated test sequences to include interaction with the Migration Toolkit for Virtualization during cluster update checks.

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.

@ammont82
Copy link
Member

ammont82 commented Apr 9, 2025

/lgtm

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

openshift-ci bot commented Apr 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 9, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 4f46665 into openshift-assisted:master Apr 9, 2025
11 checks passed
ammont82 added a commit to ammont82/assisted-installer-ui that referenced this pull request Apr 11, 2025
openshift-merge-bot bot pushed a commit that referenced this pull request Apr 11, 2025
…anges (#2909)

* Revert "selecting CNV - not able to deselect it using UI (#2906)"

This reverts commit 4f46665.

* Selecting CNV - not able to deselect it using UI
@ammont82
Copy link
Member

/cherry-pick releases/v2.39

@openshift-cherrypick-robot
Copy link
Contributor

@ammont82: new pull request created: #2914

Details

In response to this:

/cherry-pick releases/v2.39

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.

ammont82 pushed a commit to ammont82/assisted-installer-ui that referenced this pull request Sep 12, 2025
ammont82 added a commit to ammont82/assisted-installer-ui that referenced this pull request Sep 12, 2025
…anges (openshift-assisted#2909)

* Revert "selecting CNV - not able to deselect it using UI (openshift-assisted#2906)"

This reverts commit 4f46665.

* Selecting CNV - not able to deselect it using UI
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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants