Skip to main content
Solved

26R1 upgrade error: "UPGRADE FAILED: resource mapping not found for name..:"

  • June 1, 2026
  • 4 replies
  • 57 views
BerenguerE
Do Gooder (Employee)
Forum|alt.badge.img+2

Can anyone help us?

Complete error message:

Error: UPGRADE FAILED: resource mapping not found for name: "ifsapp-am-datapump" namespace: "XXXXX" from "": no matches for kind "ScaledJob" in version "keda.sh/v1alpha1"
ensure CRDs are installed first
HelmPod Failed

We’re upgrading grom 25R2 (SU 5)

It seems to me that something is missing from our installation, but if that’s the case, IFS should mention somewhere that a new functionality is needed… :(

 

Best answer by chughes

From support 

The installation failure was caused by a missing Kubernetes Custom Resource Definition (CRD) required for ScaledJob (keda.sh/v1alpha1). This CRD is part of KEDA and is required by the IFS Cloud datapump component.

As a result, Helm was unable to process the deployment manifest, which caused the 'helm-job' to time out and the installation to fail. This issue has already been identified and addressed by the Product Development team.

Resolution

Install KEDA (including its CRDs) in the cluster and then re-run the IFS Cloud middle-tier deployment.

You can execute the following commands before starting the installation (depending on where you run it, you should prefix with microk8s or not):

microk8s helm repo add kedacore https://kedacore.github.io/charts
microk8s helm repo update
microk8s helm install keda kedacore/keda --namespace ifs-autoscaler --create-namespace --version 2.16.1

4 replies

B
Superhero (Employee)
Forum|alt.badge.img+15
  • Ben Monroe
  • Superhero (Employee)
  • June 2, 2026

Hi Elaine,

The Helm chart is trying to deploy a KEDA ScaledJob resource.
Kubernetes is failing as it does not recognize that resource type.
This could happen if KEDA CRDs (Custom Resource Definition) are missing.

Data Pump (ifsapp-am-datapump) now uses KEDA ScaledJobs in 26R1.
Lets verify whether your cluster has ScaledJob available.
Run this command:
kubectl get crd | grep scaledjob
grep is only available directly on the cluster.
From Windows you can omit the pipe and manually view the output.

Which ifs-remote are you using?
KEDA should be deployed using 2.12.0 or later.

Best regards.

    BerenguerE
    Do Gooder (Employee)
    Forum|alt.badge.img+2
    • BerenguerE
    • Author
    • Do Gooder (Employee)
    • June 2, 2026

    Thank you very much for this information ​@Ben Monroe ! But I thought IFS would do it automatically…

    So you know, just after posting this question, I did a further investigation and realized that there was another error before this one (of the datapump pod):

    [Mon Jun 01 13:22:43 BRT 2026][MTINSTALL] - INFO: Running helm pod version 1.1.0.0.0
    [Mon Jun 01 13:27:43 BRT 2026][MTINSTALL] - SEVERE: timed out waiting for the condition on jobs/helm-job
    [Mon Jun 01 13:27:43 BRT 2026][MTINSTALL] - SEVERE: Failed waiting for helm-job to complete
    [Mon Jun 01 13:27:43 BRT 2026][MTINSTALL] - SEVERE: UPGRADE FAILED: resource mapping not found for name: "ifsapp-am-datapump" namespace: "mpt01tst" from "": no matches for kind "ScaledJob" in version "keda.sh/v1alpha1"
     

    I don’t know if the error with datapump pod originated because of the previous error (timeout when trying to upgrade the helm), so we’re doing a fresh installation to see how it goes.

     

    Best regards,

    Elaine Berenguer

    C
    Do Gooder (Customer)
    Forum|alt.badge.img+2
    • chughes
    • Do Gooder (Customer)
    • Answer
    • June 3, 2026

    From support 

    The installation failure was caused by a missing Kubernetes Custom Resource Definition (CRD) required for ScaledJob (keda.sh/v1alpha1). This CRD is part of KEDA and is required by the IFS Cloud datapump component.

    As a result, Helm was unable to process the deployment manifest, which caused the 'helm-job' to time out and the installation to fail. This issue has already been identified and addressed by the Product Development team.

    Resolution

    Install KEDA (including its CRDs) in the cluster and then re-run the IFS Cloud middle-tier deployment.

    You can execute the following commands before starting the installation (depending on where you run it, you should prefix with microk8s or not):

    microk8s helm repo add kedacore https://kedacore.github.io/charts
    microk8s helm repo update
    microk8s helm install keda kedacore/keda --namespace ifs-autoscaler --create-namespace --version 2.16.1

      BerenguerE
      Do Gooder (Employee)
      Forum|alt.badge.img+2
      • BerenguerE
      • Author
      • Do Gooder (Employee)
      • June 9, 2026

      Hi ​@chughes ! Installing KEDA and its CRDs first worked like a charm, thank you very much!

      Can you tell me if this is an expected behavior in upgrade process only? We did a clean install using this 26.1 version and there was no problem at all…

      IFS should’ve documented this in Upgrade Considerations documentation… :\

      Anyway, thank you very very much.

      Regards,

      Elaine Berenguer

      Terms & ConditionsAccessibility statement