Bug 995386 - QUIT in Post-Install step makes EAP malformed (Reopened)
QUIT in Post-Install step makes EAP malformed (Reopened)
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: CR1
: 6.0.0
Assigned To: Thomas Hauser
Pavol Srna
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2013-08-09 04:44 EDT by Pavol Srna
Modified: 2018-03-29 17:51 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If the user quits the installer during the post-installation step, and then tries to re-run the installer an error message appears stating that "product.conf file is either malformed or does not exist." This is because EAP becomes malformed, so you cannot use the same EAP directory for the reinstallation. Or If you force exit the install during the post installations steps while installing FSW on an previously installed EAP, you may end up with a broken EAP installation. Work around is to install into a different location or clean up your installation and start over.
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screen-2 (115.97 KB, image/png)
2013-09-18 05:13 EDT, Pavol Srna
no flags Details
Processing page (122.84 KB, image/png)
2014-01-10 09:46 EST, Tomáš Sedmík
no flags Details
InstallationLog.txt (9.33 KB, text/plain)
2014-01-23 08:23 EST, Pavol Srna
no flags Details

  None (edit)
Description Pavol Srna 2013-08-09 04:44:01 EDT
Steps to Reproduce:
1. Run soa installer, fill in all necessary fields
2. On the Post-Install installer step quit the installation
3. Re-run soa installer
4. User cannot reinstall to the same eap folder as in step 1. EAP is malformed.

Expected results:

User can re-install.
Comment 2 Pavol Srna 2013-08-10 14:16:16 EDT
Let's have these scenarios:

* install soa using the installer - (success)
* re-run the installer (select the same install folder), finish installation. (success)

* install soa using the installer, on the very last page ('Creating Shortcuts') hit on quit and confirm. (success)
* re-run the installer (select the same install folder), hit 'next'. Now there is an error dialog saying: product.conf file is either malformed or does not exist. (fail)

User should be able to reinstall soa in scenario b).
Comment 3 Thomas Hauser 2013-08-15 12:09:29 EDT
The installer now backs up files that will be modified. Current list is:


If the installation is cancelled early, the new files are deleted and the backups restored. If it is not, the backups are deleted upon installer completion. 

Relevant commit:  d07fd58ac39f38c5db4766086f04abeaebad38bd
Comment 4 Pavol Srna 2013-09-18 05:13:23 EDT
Created attachment 799227 [details]
Comment 5 Pavol Srna 2013-09-18 05:14:27 EDT
I still hit the issue:

a) after hitting on quit I cannot start EAP anymore
b) after hittin on quit I cannot reinstall soa to the same folder
Comment 6 Pavol Srna 2013-09-18 05:22:13 EDT
Error: missing product.conf file
Comment 7 Thomas Hauser 2013-09-20 15:28:17 EDT
This was fixed, but some changes in IzPack unfortunately destroyed the functionality. It cannot be put into beta, but will be available for builds after that.
Comment 11 Pavol Srna 2013-10-23 05:52:55 EDT
Verified in ER4 build.
Comment 12 Tomáš Sedmík 2014-01-07 08:38:30 EST
Steps to Reproduce:
1. Run soa installer, fill in all necessary fields
2. On the Post-Install installer step quit the installation
3. Re-run soa installer
4. User cannot reinstall to the same eap folder as in step 1. EAP is malformed.

(see attachment)
Comment 13 Thomas Hauser 2014-01-10 09:33:24 EST
Hello Tomas,

I'm having trouble reproducing this issue. I'll continue trying today but none of f my attempts result in malformed EAP; some do, however, result in failed installs.
Comment 14 Tomáš Sedmík 2014-01-10 09:46:30 EST
Created attachment 848217 [details]
Processing page

Hello Thomas,

I'm quitting the installation during "processing" (see attachment). Re-run SOA installer ends with described error.
Comment 15 Thomas Hauser 2014-01-10 18:06:42 EST
The backup / restoration process has been modified to backup the user's entire EAP installation. This will then either be discarded or put back upon installer failure / cancellation.
Comment 16 Pavol Srna 2014-01-15 06:55:14 EST
I still see some problems. 

If I attempt to quit the installation during "processing" on step 13, then there is java process not terminated properly on installer finish which prevents user to re-run the installation unless he 'pkill java' in terminal.

`ps ax | grep java` gives:

21365 pts/0    Sl     0:03 /usr/lib/jvm/java-7-oracle/bin/java -D[Standalone] -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djava.security.manager -Djava.security.policy=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/bin/security.policy -Drtgov.security.policy=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/bin/rtgov.policy -Dorg.jboss.boot.log.file=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone/log/server.log -Dlogging.configuration=file:/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone/configuration/logging.properties -jar /home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/jboss-modules.jar -mp /home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1 -Djboss.server.base.dir=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone --admin-only --server-config=standalone.xml
Comment 18 Francisco Canas 2014-01-15 10:38:24 EST
Hi Pavol,

I am having trouble reproducing the problem described in your last comment (16). Is this something you can reproduce every try, or only happens intermittently? Is there a particular job during the "processing" step where you quit to reproduce this error?

Comment 19 Francisco Canas 2014-01-15 11:09:42 EST
Please disregard my previous comment. 

I was able to reproduce this error by quitting the installation during processing precisely after the command to start up the server is first sent, but before the server has had time to display it's started code.

I've modified the Installer to track this intermediate 'starting' state, and to run the shutdown command during cleanup if the server was in this state when the user quit.

See commit:
Comment 21 Francisco Canas 2014-01-22 10:02:37 EST
Hi Pavol,

Can you give a bit more info on how to reproduce this issue? Which job number is the processing panel at when you hit quit? Or perhaps attach the InstallationLog.txt file. 

Also, some info about your OS and environment.

Comment 22 Pavol Srna 2014-01-23 08:22:11 EST
Hi Francisco,

the trick is to quit the installation in the right step. If I hit on quit during the postinstallation phase in step 14/110 then the java process is not terminated.

I recently tried on RHEL6 and openJDK7.
Comment 23 Pavol Srna 2014-01-23 08:23:24 EST
Created attachment 854377 [details]
Comment 24 Thomas Hauser 2014-02-25 11:11:50 EST
The installer now backs up the entire jboss-eap-6.1 directory that already existed on the user's system, and restores that after pressing the quit button.

Note You need to log in before you can comment on or make changes to this bug.