JR62833: MULTIPLE DEFECTS DETECTED BY DEVELOPMENT

APAR status

• Closed as program error.

Error description

• Problems resolved
  
   More than 60 small documentation issues and
  improvements
   CR and Scripts
   If auto-scaling is enabled, the
  operator should detect the conflicting settings given in
  replica_count versus min_replicas.
   Generated CR based on
  existing installation overwrites lots of value in the original
  one
   Remove "demo" deployment from User script
  (cp4a-deployment.sh) for "Other" (only OCP is supported)
   Admin
  Script (cp4a-clusteradmin-setup.sh) should not use "privileged"
  rights for default user
   Demo Pattern should avoid printing the
  routes which are not consumed by the users
   deployOperator.sh
  should support OCP 4.5
   Operator
   Application Engine check
  certificate code is failing when certificate is expired
   The
  os_label parameter in the FileNet causes invalid yaml when
  installed stand-alone
   PVC claim name is being set wrong in
  FileNet/Navigator Deployments, causing failure for pod when
  restarted
   BAI operator error if sc_deployment_platform is not
  present in the CR
   FileNet Does not deploy with MSSQL as it is
  missing an username
   FileNet External Share deployment fails
  due to templating issue
   Cluster role & role binding were not
  applied on cp4a-clusteradmin-setup.sh execution
   Defects
  encountered with helm required upgrading it to a later release
  (v2.16.10 )
   Content Analyzer uninstall does not remove
  registration information from Resource Registry
   Content
  Analyzer does not use the
  shared_configuration.sc_ingress_hostname_alias parameter
   Also
  includes 7 other minor defects for Business Automation
  Insights, 5 for Automation Decision Services and 6 for User
  Management Services
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users working with CP4A.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  *                                                              *
  *     More than 60 small documentation issues and improvements *
  *     CR and Scripts                                           *
  *         If auto-scaling is enabled, the operator should      *
  * detect the conflicting settings given in replica_count       *
  * versus min_replicas.                                         *
  *         Generated CR based on existing installation          *
  * overwrites lots of value in the original one                 *
  *         Remove "demo" deployment from User script            *
  * (cp4a-deployment.sh) for "Other" (only OCP is supported)     *
  *         Admin Script (cp4a-clusteradmin-setup.sh) should not *
  * use "privileged" rights for default user                     *
  *         Demo Pattern should avoid printing the routes which  *
  * are not consumed by the users                                *
  *         deployOperator.sh should support OCP 4.5             *
  *     Operator                                                 *
  *         Application Engine check certificate code is failing *
  * when certificate is expired                                  *
  *         The os_label parameter in the FileNet causes invalid *
  * yaml when installed stand-alone                              *
  *         PVC claim name is being set wrong in                 *
  * FileNet/Navigator Deployments, causing failure for pod when  *
  * restarted                                                    *
  *         BAI operator error if sc_deployment_platform is not  *
  * present in the CR                                            *
  *         FileNet Does not deploy with MSSQL as it is missing  *
  * an username                                                  *
  *         FileNet External Share deployment fails due to       *
  * templating issue                                             *
  *         Cluster role & role binding were not applied on      *
  * cp4a-clusteradmin-setup.sh execution                         *
  *         Defects encountered with helm required upgrading it  *
  * to a later release (v2.16.10 )                               *
  *         Content Analyzer uninstall does not remove           *
  * registration information from Resource Registry              *
  *         Content Analyzer does not use the                    *
  * shared_configuration.sc_ingress_hostname_alias parameter     *
  *     Also includes 7 other minor defects for Business         *
  * Automation Insights, 5 for Automation Decision Services and  *
  * 6 for User Management Services                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Multiple defects have been fixed.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLOUD PAK FOR A

• Fixed component ID

  5737I2300

Applicable component levels