Skip to content
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

CNV-42157: Fix disk modal template #1977

Merged

Conversation

upalatucci
Copy link
Member

📝 Description

  • use VM parameter to create dataVolumes and PVC names. For each vms we'll have different datavolumes

@openshift-ci openshift-ci bot requested review from pcbailey and vojtechszocs May 27, 2024 09:04
@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label May 27, 2024
@upalatucci upalatucci changed the title Fix disk modal template CNV-42157: Fix disk modal template May 27, 2024
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented May 27, 2024

@upalatucci: This pull request references CNV-42157 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.17.0" version, but no target version was set.

In response to this:

📝 Description

  • use VM parameter to create dataVolumes and PVC names. For each vms we'll have different datavolumes

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.

@@ -43,13 +41,6 @@ import { DYNAMIC } from '../components/utils/constants';
import { getInitialStateDiskForm, mapSourceTypeToVolumeType } from './constants';
import { DiskFormState, DiskModalProps, SourceTypes, VolumeTypes } from './types';

const nameWithoutParameter = (name: string, defaultValue?) => {
Copy link
Member

Choose a reason for hiding this comment

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

why we used it in the first place?

Copy link
Member Author

Choose a reason for hiding this comment

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

Me and aviv have no idea.

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label May 29, 2024
Copy link
Contributor

openshift-ci bot commented May 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metalice, upalatucci

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

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [metalice,upalatucci]

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 42dbedb into kubevirt-ui:main May 29, 2024
10 checks passed
@gouyang
Copy link
Member

gouyang commented Jun 5, 2024

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Collaborator

@gouyang: new pull request created: #2013

In response to this:

/cherry-pick release-4.16

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 This issue is something we want to fix jira/valid-reference lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants