+++ This bug was initially created as a clone of Bug #2072311 +++ 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:
Verified with MTC 1.7.2 (prestage) metadata_nvr: openshift-migration-operator-metadata-container-v1.7.2-15 HPA resource (Source cluster) $ oc get hpa -ntest -o yaml spec: maxReplicas: 7 minReplicas: 2 scaleTargetRef: apiVersion: v1 kind: DeploymentConfig name: nginx-deployment targetCPUUtilizationPercentage: 50 HPA resource (Target Cluster) $ oc get hpa -ntest -o yaml spec: maxReplicas: 7 metrics: - resource: name: cpu target: averageUtilization: 80 type: Utilization type: Resource minReplicas: 2 scaleTargetRef: apiVersion: apps.openshift.io/v1 kind: DeploymentConfig name: nginx-deployment 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.7.2 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:5483