Bug 1845704

Summary: The part namespace can not work correctly after migration when set max PVs limit in azure cluster
Product: Migration Toolkit for Containers Reporter: John Matthews <jmatthew>
Component: GeneralAssignee: John Matthews <jmatthew>
Status: VERIFIED --- QA Contact: Xin jiang <xjiang>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: unspecified    
Version: 1.3.0CC: jmatthew, jmontleo, rjohnson, sregidor, sseago, xjiang
Target Milestone: ---   
Target Release: 1.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1845569 Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1845569    

Description John Matthews 2020-06-09 20:37:55 UTC
+++ This bug was initially created as a clone of Bug #1845569 +++

Description of problem:
When set max PVs limit is 2.  then migrate 2 namespaces, each namespace involves 2 pvs, after migration, the migration process will finish without error. but only one namespace work well in target cluster, the other namespace will hit porblem "Unable to attach or mount volumes: unmounted volumes=[nginx-logs nginx-html], unattached volumes=[nginx-logs nginx-html default-token-78kr5]: timed out waiting for the condition" when create the pod. 

Version-Release number of selected component (if applicable):
CAM 1.2.2 stage
SOURCE: OCP 4.3 azure
TARGET: OCP 4.4 azure
azure S3 BUCKET

How reproducible:
Always

Steps to Reproduce:
1 set max PVs limit is 2 in the cluster which has controller.
2 deploy the same nginx service in 2 different namespace, each one has 2 PVs.
3 run migration aganist these 2 namespaces.
4 after migration finish successfully, check the work status of the 2 namespaces in the target cluster

Actual results:

After migration, one namespace works correctly in target cluster.But another one hit problem "Unable to attach or mount   volumes: unmounted volumes=[nginx-logs nginx-html], unattached   volumes=[nginx-logs nginx-html default-token-78kr5]: timed out waiting   for the condition" when create the pod

Expected Results:

After migration, the 2 namespaces will work correctly in target cluster. 


Additional info:

Comment 1 Sergio 2020-11-17 13:27:44 UTC
Verified using MTC 1.3.2 stage

openshift-migration-rhel7-operator@sha256:2eafc06e24cf1b815906f3eb4ba5ddd3362b607d26605d594a7ef17a51059d7e

    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 2a40d53cfa09c83b8063c3ca3d3acfd7d323b825005c9de3aacf5457ed7029ae
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: 44c9be260fcfa6e2a854f58d3498c620483ac6c360e811811401de266e895e43
    - name: MIGRATION_REGISTRY_REPO
      value: openshift-migration-registry-rhel8@sha256
    - name: MIGRATION_REGISTRY_TAG
      value: 980b8ab84e7cf3e8664a052e2fcbda74123a31b674e64f0648d49bcc472ba3a2
    - name: VELERO_REPO
      value: openshift-migration-velero-rhel8@sha256
    - name: VELERO_TAG
      value: 349db22c468b5923e415a88e03a9f14a4df249969a7275b94197bc78f2a0b26c
    - name: VELERO_PLUGIN_REPO
      value: openshift-velero-plugin-rhel8@sha256
    - name: VELERO_PLUGIN_TAG
      value: cff7527e3906dbfc494bbfc9573b645dcaa7b8d5d5777b8d013ccaac211a3dff


In order to verify the test we run the testcase ocp-33378-max-pvs that basically follows the same instructions detailed in this BZ.

Moved to VERIFIED.