Description of problem: When migrating Version-Release number of selected component (if applicable): MTC 1.5.2 How reproducible: Always when migrating HPAs from Openshift 3.x to 4.x Steps to Reproduce: 1. Migrate a project based on a Openshift 3.x cluster containing a deploymentconfig and a horizontalpodautoscaler that scales this deployment config. Check that on the destination 4.x cluster, the apiversion/kind of the spec.scaleTargetRef of the migrated HPA is not using the updated GVK of DeploymentConfig on Openshift 4.x Actual results: - hpa.spec.scaleTargetRef.apiVersion is "v1" Expected results: - hpa.spec.scaleTargetRef.apiVersion should be "apps.openshift.io/v1" Additional info:
Unsure exactly where the breakdown here is. It could be something lost in translation during the Velero backup/restore, or a controller is reconciling the value potentially. Does this break workloads?
Erik, It does break workloads as the HPAs in the target cluster will attempt to find DeploymentConfig resource under Core group. Removing NEEDINFO
Verified with MTC 1.6.5 image: registry.redhat.io/rhmtc/openshift-migration-controller-rhel8@sha256:b8d3e08c0e74bf88348e7d46f32abd24747a3fe9c66e7890c48b1d366fd61693 HPA resource(source cluster) $ oc get hpa -n ocp-mysql -o yaml spec: maxReplicas: 7 minReplicas: 1 scaleTargetRef: apiVersion: v1 kind: DeploymentConfig name: mysql targetCPUUtilizationPercentage: 75 HPA resource after performing migration(target cluster) $ oc get hpa -n oc-mysql -o yaml spec: maxReplicas: 7 metrics: - resource: name: cpu target: averageUtilization: 80 type: Utilization type: Resource minReplicas: 1 scaleTargetRef: apiVersion: apps.openshift.io/v1 kind: DeploymentConfig name: mysql hpa.spec.scaleTargetRef.apiVersion is "apps.openshift.io/v1". I see the expected behaviour. Moving this to verified status.
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 (Moderate: Migration Toolkit for Containers (MTC) 1.6.5 security and bug fix update), 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/RHSA-2022:4814