-
Bug
-
Resolution: Done
-
Critical
-
7.0.5.GA
When EAP7 is installed via RPMs and is updated via standard yum update command, configuration files in /opt/rh/eap7/root/usr/share/wildfly/bin/standalone.conf and /opt/rh/eap7/root/usr/share/wildfly/bin/domain.conf are overwritten even if they contain some customer changes.
I understand that these files are not in 'etc' folder and in our documentation we instruct user to use files in /etc/opt/rh/eap7/wildfly/eap7-[standalone|domain].conf or /etc/sysconfig/eap7-[standalone|domain] respectively. But I think that we still should not silently overwhite such modifed files.
Note that there are more *.conf files in the EAP_HOME/bin directory, thus maybe same should apply also on these too:
# ll /opt/rh/eap7/root/usr/share/wildfly/bin/*.conf -rw-rw-r--. 1 root root 1841 Feb 21 04:15 /opt/rh/eap7/root/usr/share/wildfly/bin/appclient.conf -rw-rw-r--. 1 root root 2561 Feb 21 04:15 /opt/rh/eap7/root/usr/share/wildfly/bin/domain.conf -rw-rw-r--. 1 root root 48 Feb 21 04:15 /opt/rh/eap7/root/usr/share/wildfly/bin/product.conf -rw-rw-r--. 1 root root 2590 Feb 21 04:15 /opt/rh/eap7/root/usr/share/wildfly/bin/standalone.conf
- clones
-
JBEAP-10565 RPM - yum update overrides EAP_HOME/bin/[standalone|domain].conf files
-
- Closed
-