|<< Back to previous view|
[GLASSFISH-18274] [Regression] Custom Install. Installation flow has changed after selecting "Configure again". Errors in port conflict are reported in Domain Info screen. Created: 30/Jan/12 Updated: 07/Feb/12 Resolved: 07/Feb/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Oracle Enterprise Linux (OEL)6. JDK1.7.0_02. GF 3.1.2 build19 (ogs-unix.sh). Firefox browser 3.6.25. Install option "Custom Install".
|Participants:||Alex Pineda, Joe Di Pol and scatari|
The test scenario based on the "Custom" Install option to first install a "Server domain" and afterwards, to add a "standalone instance server" or a "clustered server instance". In GF 3.1.2 build16 and prior versions (3.1.1, 3.1), the process was done, after creating the domain, by selecting the "configure again" option and selecting the option of standalone or the clustered server instance, however, in GF 3.1.2 build19 (probably present since build17), the flow has changed and the "Domain Info" screen is displayed which has the options for port, user admin, password, etc.. If one selects "Next", the system complaints of a port conflict and highlights the Admin Port and Admin User. This is clearly a regression and probably a side effect of the recent Security remediation requirements.
A workaround, which we could document is to instruct the user, not to select "Next" in the Domain Info screen, but rather select the "Back" button which then puts the user in the "Configuration" screen and allows them to proceed forward with their selection (of "standalone server" or "clustered server" instances).
|Comment by Joe Di Pol [ 31/Jan/12 10:31 PM ]|
I did some experimentation and saw two basic bugs:
In all cases:
Select Custom Installation
Select Create a server domain
Bug: This takes you to the "Domain Info" screen, not back to the Configuration screen
Select Create a stand alone server instance
|Comment by scatari [ 07/Feb/12 02:12 AM ]|
• What is the impact on the customer of the bug?
Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
• What is the cost/risk of fixing the bug?