Chapter 7. Known issues in Red Hat Decision Manager 7.12.0
This section lists known issues with Red Hat Decision Manager 7.12.
7.1. Business Central Copy linkLink copied to clipboard!
In the test scenarios table, today() and now() functions are not evaluated correctly [RHDM-1816]
Issue: In the test scenarios table, today() and now() functions are not evaluated correctly. For example, the string(today()) function should produce output similar to 2021-05-11 but instead it displays a null value.
Steps to reproduce:
Import the check-today-1.dmn and check-today-test-1.scesim files attached in the [RHDM-1816] issue and check the results.
Workaround: None.
7.2. Red Hat build of Kogito Copy linkLink copied to clipboard!
Unable to run the tests for Red Hat build of Kogito examples with scenario simulations [RHPAM-4068]
Issue: It is not possible to run the tests for Red Hat build of Kogito examples which contain scenario simulation dependency. The Surefire plugin fails with an exception.
The following two modules in the Red Hat build of Kogito examples fail because there is a mismatch of JUnit version dependency:
-
dmn-pmml-quarkus-example -
dmn-quarkus-example
These examples are included in the sources.zip and kogito-quickstarts.zip files.
Steps to reproduce:
- Download the Red Hat build of Kogito examples.
-
Execute the
mvn clean installcommand fordmn-quarkus-exampleordmn-pmml-quarkus-example.
Workaround: Override the transitive JUnit dependency of kogito-scenario-simulation file and use the version 4.13.1.redhat-00001.
7.3. KIE Server Copy linkLink copied to clipboard!
When you initialize Swagger on WebSphere, you receive an IllegalArgumentException error [RHPAM-3949]
Issue: When you use the KIE Server Swagger extension on WebSphere, KIE Server is unavailable and it returns the HTTP 500 error with an IllegalArgumentException exception.
Steps to reproduce:
- Start KIE Server with basic configuration on WebSphere.
Try to access the
http://localhost:9080/kie-server/services/rest/serverURL.You receive the HTTP 500 error.
Workaround: Disable Swagger UI by setting the value of the org.kie.swagger.server.ext.disabled system property to true.
7.4. DMN designer Copy linkLink copied to clipboard!
Elbow lines for object connections do not work [RHDM-1856]
Issue: You can adjust the DMN connections shape by adding control point to it. However this feature does not work for connections with the text annotation nodes.
Steps to reproduce for Red Hat build of Kogito:
-
Enter
http://sandbox.kie.org/#/in a browser. -
Import the
association.dmnfile attached in the [RHDM-1856] issue. -
In the Import field, upload the
association.dmnfile. - Run the project.
Steps to reproduce for Business Central:
- Open an existing project or create a new one.
-
Import the
association.dmnfile attached in the [RHDM-1856] issue. - Build the project and observe the results.
Workaround: None.
7.5. Red Hat OpenShift Container Platform Copy linkLink copied to clipboard!
When you set the default role variable as AUTH_LDAP_DEFAULT_ROLE, Red Hat OpenShift Container Platform images ignore the LDAP roles [RHPAM-4132]
Issue: For Red Hat OpenShift Container Platform images, when you set the LDAP default roles as AUTH_LDAP_DEFAULT_ROLE, all the roles from LDAP are ignored and you can not log in to the Business Central application. But when you do not set the default roles, all the roles from the LDAP are used correctly and you can log in to the Business Central application.
Steps to reproduce for operator on Red Hat OpenShift Container Platform 4.x:
Create a KieApp application and set the default role as follows:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Log in to the Business Central.
Steps to reproduce for templates on Red Hat OpenShift Container Platform 3.11:
- Create a template.
-
Set the
AUTH_LDAP_DEFAULT_ROLEenvironment variable asAUTH_LDAP_DEFAULT_ROLE = "guest". - Log in to the Business Central.
Workaround for operator on Red Hat OpenShift Container Platform 4.x: Remove the set defaultRole: guest from your KieApp application.
Workaround for templates on Red Hat OpenShift Container Platform 3.11: Do not set the environment variable as AUTH_LDAP_DEFAULT_ROLE = "guest".
When the KieApp instance containing one server configuration to pull the image from a given registry, the operator fails to deploy the server and you receive errors [RHPAM-3787]
Issue: When deploying Red Hat Decision Manager on Red Hat OpenShift Container Platform using the operator, you can not use a docker image for the KIE Server by enabling the Set KIE Server Image option and setting the Kind value to DockerImage. To use a docker image for the KIE Server, you must set the image Context, name, and image tag fields from the from the custom registry.
Steps to reproduce:
- Install the operator on Red Hat OpenShift Container Platform platform.
-
Configure one KieApp instance using
DockerImageimage as Kind value and provide the image name including the registry name. - Click Set KIE Server image.
-
Change the Kind value to
DockerImage, and then provide the image name including the registry name, but without the version tag
Workaround: None.
Authorization fails while using the role mapping [RHPAM-4146]
Issue: When you set the roleMapper, authorization fails and it is not specified in the KIELdapSecurityDomain security-domain.
Workaround:
Create the
workaround.cliscript as follows:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Create a empty file as
delayedpostconfigure.sh. Create the
postconfigure.shfile and add the following content:echo "trying to execute /opt/eap/bin/jboss-cli.sh --file=/opt/eap/extensions/workaround.cli " /opt/eap/bin/jboss-cli.sh --file=/opt/eap/extensions/workaround.cli echo "END - cli script executed"
echo "trying to execute /opt/eap/bin/jboss-cli.sh --file=/opt/eap/extensions/workaround.cli " /opt/eap/bin/jboss-cli.sh --file=/opt/eap/extensions/workaround.cli echo "END - cli script executed"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the
config-mapand add the following content:oc create configmap postconfigure \ --from-file=workaround.cli=workaround.cli \ --from-file=delayedpostconfigure.sh=delayedpostconfigure.sh \ --from-file=postconfigure.sh=postconfigure.sh
oc create configmap postconfigure \ --from-file=workaround.cli=workaround.cli \ --from-file=delayedpostconfigure.sh=delayedpostconfigure.sh \ --from-file=postconfigure.sh=postconfigure.shCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
To mount the
config-map, follow the steps mentioned in Operator method.
You will receive the following message in the logs during Red Hat JBoss EAP startup:
The security domain is also updated as follows:
<security-domain name="KIELdapSecurityDomain" default-realm="KIELdapRealm" permission-mapper="default-permission-mapper">
<realm name="KIELdapRealm" role-decoder="from-roles-attribute" role-mapper="kie-custom-role-mapper"/>
</security-domain>
<security-domain name="KIELdapSecurityDomain" default-realm="KIELdapRealm" permission-mapper="default-permission-mapper">
<realm name="KIELdapRealm" role-decoder="from-roles-attribute" role-mapper="kie-custom-role-mapper"/>
</security-domain>