Bug 1845569
| Summary: | The part namespace can not work correctly after migration when set max PVs limit in azure cluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | whu | ||||
| Component: | Migration Tooling | Assignee: | Scott Seago <sseago> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4 | CC: | chezhang, dwhatley, ernelson, jmatthew, jmontleo, mberube, rjohnson, sregidor, whu | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.4.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1845704 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-06-17 00:04:13 UTC | Type: | Bug | ||||
| 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: | 1845704 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Bugfix in PR https://github.com/konveyor/mig-controller/pull/564 Has been verified in CAM 1.2.2 stage. The fix has worked. Thanks Scott Seago
Image information:
- openshift-migration-rhel7-operator@sha256:ab124c3917a2ea22e03618f287c629e727bbcdf7ec76db5e7d0f8654064b7a52
- openshift-migration-controller-rhel8@sha256:ca9ab7ecf0d939afa1aae2540bb3daf5d7ce651ad58b94c6987484d12af1d211
- openshift-migration-velero-restic-restore-helper-rhel8@sha256:e9459138ec3531eefbefa181dae3fd93fe5cf210b2a0bd3bca7ba38fbec97f60
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:2571 |
Created attachment 1696343 [details] The whole process of test case 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: