Bug 1840315 - [RFE] Add validation to CAM for Azure cluster-specific ResourceGroup configuration for snapshot copy
Summary: [RFE] Add validation to CAM for Azure cluster-specific ResourceGroup configur...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 1.5.0
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 17:50 UTC by Scott Seago
Modified: 2021-04-07 20:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 20:46:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Scott Seago 2020-05-26 17:50:01 UTC
Description of problem:
Migration using an Azure MigStorage with snapshot PV copy will fail if either src or dest cluster is missing the AzureResourceGroup spec field. We need a MigPlan validation which will prevent migration attempts for this case.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Install CAM in an Azure host cluster, add an additional Azure MigCluster. One of these clusters should be configured without Spec.AzureResourceGroup being populated.
2. Create an Azure MigStorage.
3. Create a MigPlan to migrate a namespace which includes at least one Azure-backed PV between these two clusters, using the Azure MigStorage.
4. Configure the MigPlan to copy the PV by snapshot.
4. Start a migration.

Actual results:
Migration is attempted. The migration will fail if the src cluster is missing Spec.AzureResourceGroup. If the dest cluster is missing Spec.AzureResourceGroup, the migration may succeed but the PV will be created in the wrong ResourceGroup.

Expected results:
After configuring snapshot copy, the MigPlan should have a Fatal Condition added referencing the missing ResourceGroup param, preventing the user from being able to start a migration.

Comment 1 Erik Nelson 2021-04-07 20:46:25 UTC
Moving as an RFE into Jira for triage: https://issues.redhat.com/browse/MIG-605


Note You need to log in before you can comment on or make changes to this bug.