Bug 1929806
| Summary: | Direct Image Migration MigCluster validation fails on a cluster configured with a proxy | ||
|---|---|---|---|
| Product: | Migration Toolkit for Containers | Reporter: | Dylan Murray <dymurray> |
| Component: | Controller | Assignee: | Dylan Murray <dymurray> |
| Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> |
| Severity: | unspecified | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | unspecified | ||
| Version: | 1.4.0 | CC: | ernelson, rjohnson, sregidor |
| Target Milestone: | --- | ||
| Target Release: | 1.4.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-15 08:15:36 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: | |||
Verified CAM 1.4.2 openshift-migration-rhel7-operator@sha256:ad60243222deb83002403e9ad0d02d5e69cbfa2b8df3a91a12f827011b2c52c8 I made a mistake and moved to verified the wrong BZ. I move this BZ back to ON_QA Verified using MTC 1.4.2. proxy AWS 4.5 (controller) -> proxy AWS (4.7), AWS S3
- name: MIG_CONTROLLER_REPO
value: openshift-migration-controller-rhel8@sha256
- name: MIG_CONTROLLER_TAG
value: f02f9a62479b9ec712c622880128a80dafb5e034a97df6c34fc14cf0c0699f21
Migcluster showed no error, and an image could be migrated without problems using DIM.
Moved to VERIFIED statu.
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 (Migration Toolkit for Containers (MTC) image release advisory 1.4.2), 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/RHBA-2021:0814 |
Description of problem: Setup a proxy-enabled cluster and set `exposedRegistryPath` on a migcluster. The validation of the migcluster will fail with "connection timed out". Version-Release number of selected component (if applicable): 1.4.0 How reproducible: 100% Steps to Reproduce: 1. Create migcluster, set exposedRegistryPath 2. Create migplan with DIM enabled Actual results: Migcluster validation fails: message: 'Exposed registry route is invalid, Error : "Get \"https://docker-registry-default.apps.dymurray-ocp3.mg.dog8code.com/v2/\": dial tcp 18.223.202.130:443: connect: connection timed out"' Expected results: Migcluster validation fails Additional info: