Bug 2028931

Summary: RHACM can not deploy Helm Charts with version numbers starting with letters (e.g. v1.6.1)
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Wolfgang Kulhanek <wkulhane>
Component: App LifecycleAssignee: Mike Ng <ming>
Status: CLOSED ERRATA QA Contact: Almen Ng <almng>
Severity: high Docs Contact: bswope <bswope>
Priority: unspecified    
Version: rhacm-2.4CC: almng, xiangli, yuhe
Target Milestone: ---Flags: almng: qe_test_coverage?
bot-tracker-sync: rhacm-2.4.z+
Target Release: rhacm-2.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: 2022-03-03 06:58: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:

Description Wolfgang Kulhanek 2021-12-03 18:34:41 UTC 
Description of the problem:

When creating a subscription for a Helm chart it is possible to set a packageFilter and version to select a specific Helm chart version. If that version starts with a character instead of a number RHACM does not deploy the application. Removing the filter allows it to deploy.

Release version:
2.4

OCP version:
4.9.8

This works (note version is 0.18.0):

---
apiVersion: apps.open-cluster-management.io/v1
kind: Subscription
metadata:
  name: vault-subscription
  namespace: vault
  labels:
    app: vault
spec:
  channel: vault/hashicorp-vault-helm
  name: vault
  packageOverrides:
  - packageName: vault
    packageAlias: vault
    packageOverrides:
    - path: spec
      value:
        global:
          openshift: true
        server:
          ha:
            enabled: true
            raft:
              enabled: true
          affinity: ''
          image:
            repository: registry.connect.redhat.com/hashicorp/vault
            tag: 1.9.0-ubi
          updateStrategyType: "RollingUpdate"
        injector:
          authPath: auth/ocp-local
          image:
            repository: registry.connect.redhat.com/hashicorp/vault-k8s
            tag: 0.14.1-ubi
          agentImage:
            repository: registry.connect.redhat.com/hashicorp/vault
            tag: 1.9.0-ubi
  packageFilter:
    version: "0.18.0"
  placement:
    placementRef:
      kind: PlacementRule
      name: vault

This does not (version v1.6.1). Removing the package filter makes it work.

---
apiVersion: apps.open-cluster-management.io/v1
kind: Subscription
metadata:
  annotations:
  labels:
    app: cert-manager
  name: cert-manager
  namespace: cert-manager
spec:
  channel: cert-manager/jetstack
  name: cert-manager
  packageOverrides:
  - packageName: cert-manager
    packageAlias: cert-manager
    packageOverrides:
    - path: spec
      value:
        installCRDs: true
        extraArgs: ['--dns01-recursive-nameservers=1.1.1.1:53','--dns01-recursive-nameservers-only']
  packageFilter:
    version: "v1.6.1"
  placement:
    placementRef:
      kind: PlacementRule
      name: cert-manager
Comment 1 Almen Ng 2022-02-03 21:53:19 UTC 
Tested and verified on `2.4.2-DOWNSTREAM-2022-01-28-23-20-07` on `OCP 4.8.2`.
Comment 7 errata-xmlrpc 2022-03-03 06:58:36 UTC 
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 (Important: Red Hat Advanced Cluster Management 2.4.2 security updates and bug fixes), 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:0735