Bug 2234781
Summary: | Migrated builder pod fails to push to image registry | ||
---|---|---|---|
Product: | Migration Toolkit for Containers | Reporter: | ssingla |
Component: | General | Assignee: | Dylan Murray <dymurray> |
Status: | NEW --- | QA Contact: | ssingla |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.8.0 | CC: | dymurray, rjohnson |
Target Milestone: | --- | ||
Target Release: | 1.8.4 | ||
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: | 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: |
Description
ssingla
2023-08-25 13:25:55 UTC
This is a bug affecting OCP 4->4 migrations. There is a configmap that is generated by the build pod which contains a certificate to be used when pushing to the internal registry. MTC is migrating all of the configmaps from the source namespace which include these builder generated configmaps from previously completed builds. On the target cluster these configmaps don't get patched, and the builder pod uses the certificate from the source cluster. OADP should be discarding this configmap on restore or openshift needs to be patching the configmap on build pod startup. |