CNV-46660: show disk pvc not the original source

[upalatucci]

📝 Description

Before

VM disk list show the original PVC where data source clone the data for the disk

VM -> DataSource -> PVC (source cloned)

The PVC that you see here is not the PVC that the VM will use but what the datavolume will clone. This will probably create confusion to the user.

After

Vm disk list show the actual PVC used by the VM

VM -> DataVolume -> Actual PVC used (The one that we have to resize, not the source cloned)

Why we did that?

Because in the instancetype we want to show in the disk list the source size that will be cloned. In order to do that, we have to set the storage.resources.requests.storage property

[openshift-ci-robot]

@upalatucci: This pull request references CNV-46660 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 either version "4.18." or "openshift-4.18.", but it targets "CNV v4.18.0" instead.

In response to this:

📝 Description

Before

VM disk list show the original PVC where data source clone the data for the disk

VM -> DataSource -> PVC (source cloned)

After

Vm disk list show the actual PVC used by the VM

VM -> DataVolume -> Actual PVC used (The one that we have to resize, not the source cloned)

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-robot]

@upalatucci: This pull request references CNV-46660 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 either version "4.18." or "openshift-4.18.", but it targets "CNV v4.18.0" instead.

In response to this:

📝 Description

Before

VM disk list show the original PVC where data source clone the data for the disk

VM -> DataSource -> PVC (source cloned)

After

Vm disk list show the actual PVC used by the VM

VM -> DataVolume -> Actual PVC used (The one that we have to resize, not the source cloned)

Why we did that?

Because in the instancetype we want to show in the disk list the source size that will be cloned. But we have to find another way to show that.

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-robot]

@upalatucci: This pull request references CNV-46660 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 either version "4.18." or "openshift-4.18.", but it targets "CNV v4.18.0" instead.

In response to this:

📝 Description

Before

VM disk list show the original PVC where data source clone the data for the disk

VM -> DataSource -> PVC (source cloned)

After

Vm disk list show the actual PVC used by the VM

VM -> DataVolume -> Actual PVC used (The one that we have to resize, not the source cloned)

Why we did that?

Because in the instancetype we want to show in the disk list the source size that will be cloned. In order to do that, we have to set the storage.resources.requests.storage property

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-robot]

@upalatucci: This pull request references CNV-46660 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 either version "4.18." or "openshift-4.18.", but it targets "CNV v4.18.0" instead.

In response to this:

📝 Description

Before

VM disk list show the original PVC where data source clone the data for the disk

VM -> DataSource -> PVC (source cloned)

The PVC that you see here is not the PVC that the VM will use but what the datavolume will clone. This will probably create confusion to the user.

After

Vm disk list show the actual PVC used by the VM

VM -> DataVolume -> Actual PVC used (The one that we have to resize, not the source cloned)

Why we did that?

Because in the instancetype we want to show in the disk list the source size that will be cloned. In order to do that, we have to set the storage.resources.requests.storage property

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]

[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

[metalice]

@upalatucci i dont see SC and PVC link in the after screen shot?