Chapter 5. Known issues

This section lists known issues with Red Hat Process Automation Manager 7.5.

5.1. Installation

Red Hat Process Automation Manager in a Red Hat JBoss Web Server datasource configuration is missing elements [RHPAM-2428]

Issue: When you use the installer to install Red Hat Process Automation Manager in Red Hat JBoss Web Server and you configure a datasource, there are some missing elements that are needed for the setup to work properly.

Steps to reproduce:

  1. Use the installer to install Red Hat Process Automation Manager on Red Hat JBoss Web Server.
  2. When prompted, click Configure Advanced Properties → Configure Database Settings.
  3. Configure your settings and add a user name and password.
  4. Try running the server.

Expected result: Red Hat Process Automation Manager starts.

Actual result: Red Hat Process Automation Manager does not start.

Workaround: Modify the resource in the context.xml file as described in the "Configuring JDBC Web Server data sources" section of Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss Web Server.

On Red Hat JBoss EAP, the Red Hat Process Automation Manager installer creates an incorrect password vault for the created datasource [RHPAM-2407]

Issue: If you use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP and you configure database settings, the datasource element in the standalone files is wrong and connection to the database fails.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Use the installer to install Process Server only onto Red Hat JBoss EAP.
  2. When prompted, click Configure Advanced Properties → Configure Database Settings.
  3. Open the standalone.xml or standalone-full.xml file to verify user credentials.

Expected result: The datasource element in the standalone files should look similar to the following, where <NEWDATASOURCE> is the name of your database: 

<password>${VAULT::datasource.<NEWDATASOURCE>::password::1}</password>

Actual Result: The datasource element in the standalone files looks similar to the following: 

<password>:datasource.<NEWDATASOURCE>::password::1</password>

Workaround: Replace the <password> entry with the correct password vault entry for the database. In this example, <NEWDATASOURCE> is the name of your database: 

${VAULT::datasource.<NEWDATASOURCE>::password::1}

5.2. Business Central

You cannot start a task if the Elytron adapter is installed [RHPAM-2450]

Issue: If Business Central on Red Hat JBoss EAP is integrated with RH-SSO using the Elytron adapter, errors are displayed after a task is started.

Steps to reproduce:

  1. Install Red Hat Process Automation Manager on Red Hat JBoss EAP.
  2. Configure Business Central with RH-SSO using the Elytron adapter.
  3. Import a process sample.
  4. Start the process.
  5. Start a task.

Expected result: The task starts correctly.

Actual result: The task does not start and an error is displayed.

Workaround: Use the legacy adapter instead of the Elytron adapter. Enter the following command to install the legacy adapter: 

./bin/jboss-cli.sh -c --file=bin/adapter-install.cli

An error might occur if you import a sample project twice [RHPAM-2434]

Issue: An Unable to complete your request error might appear if you import a sample project that has already been imported.

Steps to reproduce:

  • Import a sample project twice. Note that this error does not always occur.

Workaround: If the sample project that failed to import is present in your space, remove it then import it again.

In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values [RHPAM-2457]

Issue: In the guided rule editor, you cannot use the is contained in comma separated list constraint in combination with complex values. Complex values are values that contain a comma or are wrapped by brackets.

Workaround: None.

The Bulk Reassign check boxes on the Task List page reset before finishing the selected operation [RHPAM-2387]

Issue: If you select multiple tasks on the Task List page and then select a bulk reassignment operation, when the dialog box appears over the Task List page, the previously selected tasks are no longer selected.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  • On the Task List page, select multiple tasks and choose a bulk reassignment operation.

Expected result: A dialog box appears on top of the Task List page. The list of tasks is visible on the Task List page and the previously selected tasks are still selected.

Actual result: A dialog box appears on top of the Task List page. The list of tasks is visible on the Task List page and the previously selected tasks are not selected.

Workaround: None.

The Bulk Reassign operation fails if you include tasks that are in a state that does not allow reassignment [RHPAM-2386]

Issue: If you select multiple tasks with various states, for example Ready and Reserved, including tasks that are in a state that does not allow reassignment, for example Suspended and Completed, then the bulk reassign operation fails.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Select tasks with various states and include one task that is in the Suspended state.
  2. Run the bulk reassignment. An error message appears telling you that some of the the tasks could not be reassigned because they were not in the correct state.
  3. Click OK.

Expected result: The dialog box closes and the operation is attempted on all of the tasks. Results for particular tasks are presented separately as notifications.

Actual result: The dialog box does not close. When you close it manually by clicking the x in the top right corner, and you check the states of the previously selected tasks, only the tasks processed before first failure are reassigned.

Workaround: Before running the bulk action, filter the tasks and omit any task that will interrupt the reassignment.

In the DMN designer, the DMN file validation operation does not report invalid operators [RHDM-1119]

Issue: In the DMN designer, if the DMN model contains an invalid operator (an operator that does not exist), for example >>>>, the validation operation does not report the invalid operator.

Workaround: None.

5.3. High availability

In a high-availability authoring environment, when one user imports a project, another user is unable to see it [RHPAM-2470]

Issue: When multiple users connect to a high-availability Business Central and one user creates a project, another user cannot see the project.

Steps to reproduce:

  1. Log in to Business Central as two different users (A and B) from two different hosts or browsers.
  2. As user A and as user B, open the same space.
  3. As user A, import a project using an external Git repository URL.

Expected result: As user B, you can see the imported project in the space.

Actual result: As user B, you cannot see the imported project in the space.

Workaround: As user B, reload the space.

In a high-availability authoring environment, role changes in Business Central are not saved [RHPAM-2342]

Issue: If you configure a role change in high-availability Business Central, the change can be lost after a time and the roles reset to defaults.

Workaround: Configure the role change again.

In a high-availability authoring environment, an imported project in Business Central appears multiple times [RHPAM-2372]

Issue: If you import a sample project in high-availability Business Central, the project can appear in the list several times. Some copies might not have all of the assets. The environment can slow down when this issue occurs.

Workaround: Ensure one copy has all of the assets, then remove all other copies. If Business Central performance is slow, restart all of the nodes connected to it.

In a high-availability authoring environment, project creation fails when a Business Central node is down [RHPAM-2475]

Issue: When you create a project, the project creation does not complete. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: Create the project again.

In a high-availability authoring environment, asset creation is not completed when a Business Central node is down [RHPAM-2476]

Issue: When you create an asset, the asset is not indexed. It is displayed in Business Central but you cannot use it. The cause is one Business Central node in a high-availability authoring environment going down.

Workaround: In the Project Explorer view, open the asset and click Save.

In a high-availability authoring environment, multi-project import slows down Business Central [RHPAM-2477]

Issue: When a user imports multiple projects in a high-availability Business Central with multi-project import enabled, Business Central slows down and consumes significant resources.

Steps to reproduce:

  1. In the Settings menu of Business Central, enable multi-project import.
  2. Enter a space and import all samples at one time.

Expected result: Business Central operates normally and imports the samples.

Actual result: Business Central slows down and consumes a lot of resources. In a Red Hat OpenShift Container Platform environment, the pod eventually fails.

Workaround: Restart all Business Central nodes. To avoid this issue, do not enable multi-project import.

5.4. Process designer

If you try to migrate a process with a sequence flow without the source and target nodes set, you should receive a warning message, but you do not [RHPAM-2453]

Issue: If a process in the legacy process designer contains a sequence flow without the source and target nodes set, and you try to migrate that process to the new process designer, you should receive a warning message, but you do not. It is also not possible to migrate process.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a sequence flow to the process, do not set the source and target nodes, and then save the process.
  3. Click the Migrate button.

Expected result: You see a message telling you that the source and target nodes for a sequence flow are not set and you cannot migrate the process.

Actual result: No message appears and you cannot migrate the process.

Workaround: None.

If you migrate a process from the legacy process designer to the new process designer, you receive an incorrect warning that a node will be ignored [RHPAM-2452]

Issue: If you migrate a process from the legacy process designer to the new process designer, you receive a warning that a node will be ignored. However, the node is not ignored and is migrated successfully.

Steps to reproduce:

  1. Create a Start to End process in the legacy process designer.
  2. Migrate the process to the new process designer.

Expected result: No warning about ignoring elements are shown if no elements will be ignored after migration.

Actual result: Warnings are shown that some unknown element will be ignored.

Workaround: Ignore the warnings and confirm that all nodes migrate successfully.

In the new process designer, the warning message for migrating a Group element is missing [RHPAM-2454]

Issue: If you migrate a process that contains a Group element from the legacy process designer to the new process designer, the warning message about ignoring the node is missing.

Steps to reproduce:

  1. Create a process in the legacy process designer.
  2. Add a Group element to the process and then save the process.
  3. Migrate the process from the legacy process designer to the new process designer.

Expected result: You see a warning message about ignoring the node.

Actual result: You do not see the warning message.

Workaround: None.

In the new process designer, some end events have incorrect icons [RHPAM-2413]

Issue: In the new process designer, signal, escalation, compensation, and message end events are not filled, but they should be according to the BPMN 2.0 specification.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Workaround: None.

5.5. Red Hat OpenShift Container Platform

The role properties file configuration is available for internal authentication [RHPAM-2247]

Issue: The role properties file configuration should be available only when RH-SSO or LDAP authentication is used. However, currently it is also available when internal authentication is used.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Retain the authentication mode Internal.
  4. Complete the role properties file configuration.
  5. Deploy the result.

Expected result: When internal authentication is used, it is not possible to specify the role properties file.

Actual result: When internal authentication is used, it is possible to specify the role properties file.

Workaround: If you plan to use internal authentication, leave the role properties file property in Business Automation Operator UI empty.

Resource requests have an incorrect name in the customer resource (CR) YAML file [RHPAM-2248]

Issue: Resource requests are specified as request in the Business Automation Operator UI, however in the customer resource definition (CRD) they are specified as requests. Therefore, CPU and memory requests from the UI are not applied.

Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Steps to reproduce:

  1. Open the Business Automation Operator UI.
  2. Assign values to mandatory parameters.
  3. Complete CPU and memory requests for Console.
  4. Check the resulting YAML file.

Expected result: In the generated YAML file, resource requests are specified as requests.

Actual result: In the generated YAML file, resource requests are specified as request.

Workaround: In the generated YAML file, change the resource request specification from request to requests.

Product environment fails to deploy on Amazon Web Services (AWS) with AWS Elastic Block Storage (EBS) because of AWS EBS volume plugin lack of support for ReadWriteMany (RWX) persistent volume access mode [RHPAM-2480]

Issue: Several templates used for installing Red Hat Process Automation Manager on Red Hat OpenShift Container Platform, as well as deployment of several environment types using the Business Automation Operator, fail to deploy on AWS with EBS. The templates and environment types include persistent volume claims that require support for the ReadWriteMany access mode and the AWS EBS volume plugin does not provision persistent volumes with this access mode.

The following templates are affected:

  • rhpam75-managed.yaml
  • rhpam75-prod.yaml
  • rhpam75-prod-immutable-monitor.yaml
  • rhpam75-authoring.yaml
  • rhpam75-authoring-ha.yaml

Workaround: Deploy an NFS server and provision the persistent volumes using NFS. For information about provisioning persistent volumes using NFS, see one of the following guides:

Optaweb Vehicle Routing tests fail due to different versions of dependencies [RHDM-1129]

Issue: Optaweb Vehicle Routing is distributed with the incorrect package-lock.json file. As a result, snapshot tests of the optaweb-vehicle-routing-frontend module fail because of changes in HTML code generated by different versions of dependencies.

Workaround:

  1. Change directory to the optaweb-vehicle-routing-frontend module.

  2. Enter the following command to download the required dependencies: 

    $ npm install

  3. Enter the following command to run the tests: 

    $ npm test
  4. Press the u key to update failing snapshots.

The optaweb-employee-rostering example fails to build with the offline Maven repository ZIP files [RHPAM-2465]

Issue: When you build the optaweb-employee-rostering example with only Business Central and the Red Hat Process Automation Manager offline Maven repository, the build fails with the following message: 

Could not resolve dependencies for project org.optaweb.employeerostering:employee-rostering-server:jar:7.26.0.Final-redhat-00004: The following artifacts could not be resolved: net.jcip:jcip-annotations:jar:1.0.0.redhat-8, org.jboss.logging:jboss-logging:jar:3.3.2.Final-redhat-00001: Could not find artifact net.jcip:jcip-annotations:jar:1.0.0.redhat-8 in bxms-product-repo
Note

This issue is resolved with Red Hat Process Automation Manager patch release 7.5.1.

Workaround: Use the the Red Hat GA repository to fetch the missing artifacts.

Red Hat Business Optimizer is missing an environment variable for thread pool queue size [RHDM-1096]

Issue: The org.optaplanner.server.ext.thread.pool.queue.size system property has been added to the Process Server Red Hat Business Optimizer extension. This property cannot be directly set on the Process Server image.

Workaround: Use the existing JAVA_OPTS_APPEND environment variable and append the system property.

The Process Server pod fails to start after a user updates the BusyBox image on Red Hat OpenShift Container Platform [RHPAM-2431]

Issue: In a Red Hat OpenShift Container Platform environment, a Process Server pod fails to start or restart with the latest version of the BusyBox image.

Steps to reproduce:

  1. In your Red Hat OpenShift Container Platform environment, use a template or operator to deploy a Process Server that uses a MySQL or PostgreSQL database server.

  2. Enter the following command to manually update the OpenShift registry to the latest BusyBox image: 

    $ docker pull busybox
  3. Scale the Process Server pod down to 0 replicas and then scale up.

Expected result: The Process Server pod starts normally.

Actual result: The Process Server pod fails to start and remains at 0 replicas.

Workaround:

  1. On a local machine that has access to the cluster and has Docker installed, enter the following command to pull the BusyBox image version 1.28.4: 

    $ docker pull docker.io/busybox:1.28.4

  2. Enter the following comand to tag the image with the latest tag: 

    docker tag docker.io/busybox:1.28.4 myopenshiftcluster/openshift/busybox:latest

  3. Push the image into your Red Hat OpenShift Container Platform environment. For instructions, refer to the following documentation:

High available event-driven decisioning (HA CEP server) build fails [RHPAM-2530]

Issue: The image build for the HA CEP server fails with the following message: 

The command '/bin/sh -c microdnf install --nodocs java-1.8.0-openjdk-headless && microdnf clean all' returned a non-zero code: 141

The probem is caused by a recently found issue with microdnf.

Workaround:

In the springboot directory, edit the Dockerfile file. Replace the line that contains the microdnf command with the following line: 

RUN microdnf install java-1.8.0-openjdk-headless && microdnf clean all