Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

5.4. 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.

注記

This issue is resolved with Red Hat Decision 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.

注記

This issue is resolved with Red Hat Decision 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 Decision 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 rhdm75-authoring-ha.yaml template is affected.

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 Decision 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
注記

This issue is resolved with Red Hat Decision 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 Decision Server Red Hat Business Optimizer extension. This property cannot be directly set on the Decision Server image.

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

The Decision 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 Decision 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 Decision 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 Decision Server pod down to 0 replicas and then scale up.

Expected result: The Decision Server pod starts normally.

Actual result: The Decision 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
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

Legal Notice

Theme

© 2026 Red Hatトップに戻る