Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2289

Add RHPAM version validation for RHPAM operator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 7.5.0.GA
    • 7.4.0.GA
    • Cloud
    • None
    • CR1
    • Hide

      1. I provisioned an OpenShift cluster and added the Business Automation operator to a project.
      2. I attempted to create a kieapp; however, that failed because the 7.4 images are not yet available by default in the OCP internal registry (they can be imported from registry.redhat.io). Reviewing the image streams that are available in the internal registry, I noted that the 7.3 images were available.
      3. I reviewed the generated CR for the kieapp that I created, and I noted the spec.commonConfig.version field which is defaulted to 7.4.
      4. I created a new kieapp, explicitly specifying version to 7.3, e.g. :

      apiVersion: app.kiegroup.org/v1
      kind: KieApp
      metadata:
        name: rhpam-trial73
        namespace: pam-test1
      spec:
        environment: rhpam-trial
        commonConfig:
          version: '73'
      

      5. The operator attempts to run the 7.3 version and fails to start the kieserver pod with an error that looks like the following :
      " PostStartHookError: command '/bin/sh /opt/eap/bin/launch/jboss-kie-kieserver-hooks.sh' exited with 127: /bin/sh: /opt/eap/bin/launch/jboss-kie-kieserver-hooks.sh: No such file or directory "

      Show
      1. I provisioned an OpenShift cluster and added the Business Automation operator to a project. 2. I attempted to create a kieapp; however, that failed because the 7.4 images are not yet available by default in the OCP internal registry (they can be imported from registry.redhat.io). Reviewing the image streams that are available in the internal registry, I noted that the 7.3 images were available. 3. I reviewed the generated CR for the kieapp that I created, and I noted the spec.commonConfig.version field which is defaulted to 7.4. 4. I created a new kieapp, explicitly specifying version to 7.3, e.g. : apiVersion: app.kiegroup.org/v1 kind: KieApp metadata: name: rhpam-trial73 namespace: pam-test1 spec: environment: rhpam-trial commonConfig: version: '73' 5. The operator attempts to run the 7.3 version and fails to start the kieserver pod with an error that looks like the following : " PostStartHookError: command '/bin/sh /opt/eap/bin/launch/jboss-kie-kieserver-hooks.sh' exited with 127: /bin/sh: /opt/eap/bin/launch/jboss-kie-kieserver-hooks.sh: No such file or directory "
    • 2019 Week 32-34, 2019 Week 35-37

      The Business Automation operator that is available in OpenShift (through operatorhub) is apparently only expected to work with PAM 7.4 and above. If that is a clear / expected limitation, the spec.commonConfig.version field should be validated for the expected/supported versions of PAM.

      Additionally, the documentation for provisioning with operators on OpenShift should clearly state the expectation / limitation of the operator.

              tohughes Tommy Hughes
              akochnev@redhat.com Aleksandar Kochnev (Inactive)
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: