Hello experts,

#BUG

OCP version= 4.8
Jboss image version : 7.4.3

image: "jboss-eap-7/eap73-openjdk11-openshift-rhel8"

Those logger categories are not updating in the standalone-openshift.xml. I have checked pod logs but unfortunately not able to find any hints on what's is getting wrong.

Below are the steps to reproduce this issue:
1. Create jbaas-arg-dvl namespace
2. Create eldows-logging configmap.
3. Use Image: jboss-eap-7/eap73-openjdk11-openshift-rhel8 and use it in the deploymentconfig.

4. Create a deploymentconfig and Rollout.
5. When pod started you can find env file in /properties/logging.env inside the pod

Those logger categories are not updating in the standalone-openshift.xml. I have checked pod logs but unfortunately not able to find any hints on what's is getting wrong.

It seems configure_logger_category.sh script is being called:

1. Usage:
2. It will look for a environment variable called LOGGER_CATEGORIES
3. It will expect for new loggers in the following patter: logger-category:logger-level,second-logger-category:level
4. Example: LOGGER_CATEGORIES=com.my.package:TRACE, com.my.other.package:TRACE
   #
5. The script will output the following format and add it to the standalone-openshift.xml file,
6. for the example above we'll have:
   #
7. <logger category="com.my.package">
8. <level name="TRACE"/>
9. </logger>
10. <logger category="com.my.other.package">
11. <level name="TRACE"/>
12. </logger>

The ConfigMap will create a file /properties/logging.env in the pod which contains "LOGGER_CATEGORIES=general:DEBUG, be.argenta:DEBUG, org.apache.tomcat.util.modeler:WARN, org.jboss.as:INFO".