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-36798: Provisioning percentage #1844

Merged

Conversation

upalatucci
Copy link
Member

@upalatucci upalatucci commented Mar 11, 2024

📝 Description

Provisioning percentage for one or multiple disks

🎥 Demo

image
Screenshot from 2024-03-11 18-02-49
Screenshot from 2024-03-11 17-57-59

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Mar 11, 2024

@upalatucci: This pull request references CNV-36798 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 epic to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

Add a brief description

🎥 Demo

Screenshot from 2024-03-11 18-20-48
Screenshot from 2024-03-11 18-02-49
Screenshot from 2024-03-11 17-57-59

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 metalice and yaacov March 11, 2024 19:48
@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label Mar 11, 2024
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Mar 11, 2024

@upalatucci: This pull request references CNV-36798 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 epic to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

Provisioning percentage for one or multiple disks

🎥 Demo

Screenshot from 2024-03-11 18-20-48
Screenshot from 2024-03-11 18-02-49
Screenshot from 2024-03-11 17-57-59

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.

@upalatucci
Copy link
Member Author

/retest

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Mar 12, 2024

@upalatucci: This pull request references CNV-36798 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 epic to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

Provisioning percentage for one or multiple disks

🎥 Demo

image
Screenshot from 2024-03-11 18-02-49
Screenshot from 2024-03-11 17-57-59

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.

@upalatucci
Copy link
Member Author

/retest

@metalice
Copy link
Member

/lgtm

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

openshift-ci bot commented Mar 13, 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 d52db7c into kubevirt-ui:main Mar 13, 2024
9 checks passed
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.

3 participants