A customer is using ubi8 openjdk images for sometime and he noticed that openjdk-17:1.17.x images no longer are picking   JAVA_OPTS_APPEND if JAVA_OPTS is specified.

Here are the test results.
1. oc new-app --context-dir=getting-started --name=quickstart --image-stream=test/openjdk-17:1.17-2~
https://github.com/quarkusio/quarkus-quickstarts.git#3.2
--build-env='JAVA_OPTS=-Xmx1024M' --build-env='JAVA_OPTS_APPEND=-Dbox=fox'

results in the container running with the following jvm and option

sh-4.4$ jps -v
1 quarkus-run.jar -Xmx1024M
164 Jps Dapplication.home=/usr/lib/jvm/java-17-openjdk
17.0.9.0
.9-2.el8.x86_64 -Xms8m -Djdk.module.main=jdk.jcmd

2. oc new-app --context-dir=getting-started --name=quickstart --image-stream=java/openjdk-17:1.15-1~
https://github.com/quarkusio/quarkus-quickstarts.git#3.2
--build-env='JAVA_OPTS=-Xmx1024M' --build-env='JAVA_OPTS_APPEND=-Dbox=fox'

results in the container running with the following jvm and options

sh-4.4$ jps -v
112 Jps Dapplication.home=/usr/lib/jvm/java-17-openjdk
17.0.6.0
.10-3.el8_7.x86_64 -Xms8m -Djdk.module.main=jdk.jcmd
1 quarkus-run.jar -Xmx1024M -XX:MaxRAMPercentage=50.0 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -Dbox=fox
 

I understand we have a KCS article (below) to indicate that it is the expected behaviour, however since Cu is using both JAVA_OPTS and JAVA_OPTs_APPEND for sometime, he is considering this a bug.

https://access.redhat.com/solutions/7031183

So before opening the bug, I have aksed a question in the java slack forum and I was asked to open a ticket.

Please confirm the expected behaviour..