Details
-
Bug
-
Resolution: Done
-
Major
-
JWS 4.0.0 DR1
-
None
-
Compatibility/Configuration, User Experience
-
Description
JWS4 systemD files should point to symlink /opt/rh/jws4/root/usr/share/tomcat/conf which leads to /etc/opt/rh/jws4/tomcat/ instead of pointing to its destination.
ll opt/rh/jws4/root/usr/share/tomcat/ lrwxrwxrwx. 1 root root 23 May 29 12:58 conf -> /etc/opt/rh/jws4/tomcat
grep EnvironmentFile /usr/lib/systemd/system/jws4-tomcat* /usr/lib/systemd/system/jws4-tomcat-jsvc.service:EnvironmentFile=/etc/opt/rh/jws4/tomcat/tomcat.conf /usr/lib/systemd/system/jws4-tomcat-jsvc.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat /usr/lib/systemd/system/jws4-tomcat.service:EnvironmentFile=/etc/opt/rh/jws4/tomcat/tomcat.conf /usr/lib/systemd/system/jws4-tomcat.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat /usr/lib/systemd/system/jws4-tomcat@.service:EnvironmentFile=/etc/opt/rh/jws4/tomcat/tomcat.conf /usr/lib/systemd/system/jws4-tomcat@.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat@%I
If symlink defined at /opt/rh/jws4/root/usr/share/tomcat/conf points to different folder then /etc/opt/rh/jws4/tomcat, it will lead to jws4 service startup failure. Tomcat doesn't go online due to missing configuration files.
Expected output:
grep EnvironmentFile /usr/lib/systemd/system/jws4-tomcat* /usr/lib/systemd/system/jws4-tomcat-jsvc.service:EnvironmentFile=/opt/rh/jws4/root/usr/share/tomcat/conf/tomcat.conf /usr/lib/systemd/system/jws4-tomcat-jsvc.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat /usr/lib/systemd/system/jws4-tomcat.service:EnvironmentFile=/opt/rh/jws4/root/usr/share/tomcat/conf/tomcat.conf /usr/lib/systemd/system/jws4-tomcat.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat /usr/lib/systemd/system/jws4-tomcat@.service:EnvironmentFile=/opt/rh/jws4/root/usr/share/tomcat/conf/tomcat.conf /usr/lib/systemd/system/jws4-tomcat@.service:EnvironmentFile=-/etc/opt/rh/jws4/sysconfig/tomcat@%I