-
Bug
-
Resolution: Unresolved
-
Major
-
8.1.z.GA
-
None
-
False
-
-
False
-
-
-
-
-
-
-
Customer, in domain mode, is trying to update from EAP 8.0.7 to 8.0.8 in an environment using symbolic link across different file systems (only for the /domain folder) and is receiving the following error while trying to update via the jboss-cli method:
installer update --host=master --maven-repo-files=/app/mid/patches/copy/jboss-eap-8.0.8-runtime-maven-repository.zip --confirm shutdown --host=master --perform-installation Caused by: java.nio.file.FileSystemException: /app/mid/jboss/.update.old/domain/configuration/mgmt-users.properties -> /app/mid/jboss/domain/configuration/mgmt-users.properties: Invalid cross-device link
I replicated customer's environment (with symbolic link for domain folder in a different file system) with the following steps:
1) I copied the content of the domain folder inside the target symlink folder:
cp -a /home/mcolonne/work/cases/04228266/jboss-eap-8.0/domain/* /run/media/mcolonne/ESD-USB/the_real_domain_dir/
2) I deleted the 'real' domain folder:
rm -rf /home/mcolonne/work/cases/04228266/jboss-eap-8.0/domain/
3) I created the symlink:
ln -s /run/media/mcolonne/ESD-USB/the_real_domain_dir /home/mcolonne/work/cases/04228266/jboss-eap-8.0/domain/
mcolonne@mcolonne-thinkpadp1gen7:~/work/cases/04228266/jboss-eap-8.0$ ls -l total 464 drwxr-xr-x. 1 mcolonne mcolonne 26 Jan 19 2024 appclient drwxr-xr-x. 1 mcolonne mcolonne 1852 Jun 11 15:22 bin drwxr-xr-x. 1 mcolonne mcolonne 44 Jan 19 2024 docs lrwxrwxrwx. 1 mcolonne mcolonne 47 Aug 22 12:16 domain -> /run/media/mcolonne/ESD-USB/the_real_domain_dir rw-rr-. 1 mcolonne mcolonne 419 Jan 19 2024 JBossEULA.txt rw-rr-. 1 mcolonne mcolonne 431592 Jan 19 2024 jboss-modules.jar rw-rr-. 1 mcolonne mcolonne 26530 Jan 19 2024 LICENSE.txt drwxr-xr-x. 1 mcolonne mcolonne 12 Jan 19 2024 modules drwxr-xr-x. 1 mcolonne mcolonne 74 Jun 11 14:24 standalone rw-rr-. 1 mcolonne mcolonne 63 Jan 19 2024 version.txt drwxr-xr-x. 1 mcolonne mcolonne 176 Jan 19 2024 welcome-content
Once the environment has been replicated, I attempted the following updates with the resulting outcomes:
1) 8.0.0 -> 8.0.4 via the 8.0.4 standalone jboss-eap-installation-manager -> update goes through
2) 8.0.4 -> 8.0.7 via the 8.0.4 standalone jboss-eap-installation-manager -> update goes through
3) 8.0.7 -> 8.0.8 via the 8.0.7/8.0.8 standalone jboss-eap-installation-manager -> update DOES NOT goes through -> issued same exact customer's error
4) 8.0.7 -> 8.0.8 via the 8.0.4 standalone jboss-eap-installation-manager -> update goes through
Here, an example of the update command used:
./jboss-eap-installation-manager.sh update perform --offline --repositories local-mrrc::file:/home/mcolonne/work/eap/jboss-eap-8.0.4-runtime-maven-repository/jboss-eap-8.0.4.GA-runtime-maven-repository/maven-repository --dir=/home/mcolonne/work/cases/04228266/jboss-eap-8.0
There have been some changes I haven't found regarding that after 8.0.4 installation-manager version? Or is it unexpected behaviour?
- clones
-
JBEAP-30876 (8.0.z) installation-manager >8.0.4 update fails with symbolic link
-
- Ready for QA
-
- is incorporated by
-
JBEAP-31095 (8.1.z) Upgrade jboss-eap-installation-manager (prospero) to 1.3.8.Final
-
- New
-