Bug 1004731 - rhqctl upgrade on windows doesn't work correctly
Summary: rhqctl upgrade on windows doesn't work correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.9
Hardware: x86_64
OS: Windows
urgent
urgent
Target Milestone: ---
: RHQ 4.9
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 951619
TreeView+ depends on / blocked
 
Reported: 2013-09-05 11:22 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-24 19:09:29 UTC
Embargoed:


Attachments (Terms of Use)

Description Armine Hovsepyan 2013-09-05 11:22:26 UTC
Description of problem:
rhqctl upgrade on windows doesn't work correctly

Version-Release number of selected component (if applicable):
rhq 48f882b

How reproducible:
always

Steps to Reproduce:
1. install rhq 4.5.1 
2. upgrade to 4.9 running rhqctl.bar upgrade --from-server-dir ${server_dir_4.5.1}
3. stop/start all services with rhqct.bat stop/start operation


Actual results:
after step2.
Thw following excepiton in server.log:
Could not find the remoting servlet invoker: ----  need to wait for remoting to be initialized later
Storage node stays in installed mode
storage node is not discovered, not auto-inventoried into server-gui
server is not available
operation manual discovery fails with timeout

after step3.

The following warning in server.log
 [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-7) {CommandProcessor.failed-authentication}Command failed to be authenticated!  This command will be ignored and not processed

Storage node stays in installed mode
storage node is not discovered, not auto-inventoried into server-gui
server is not available
operation manual discovery fails with timeout


Expected results:
server, storage and agent installed and started correctly
storage node is auto-inventoried into server-gui
storage goes through installation process and stay in normal mode


Additional info:
OS: windows 2008
DB: both oracle and postgresql

screen-shots -> http://d.pr/i/tHO7
http://d.pr/i/ctRB

Comment 1 Jay Shaughnessy 2013-09-06 19:34:22 UTC
I believe the problem here was the one fixed in master commit:

8f4561e80356cc723e288f60bf22a304a941e892

That problem caused the failure of the rhq.ear deployment.  The exceptions mentioned above are do to an agent trying to hit the server when the comm layer is down, it can typically be ignored and shouldn't happen many times if the rhq.ear actually deploys successfully.

Additionally, there have been a few other fixes regarding windows path handling. This is master commit:

c767213d562442c1c511cf2f610e14bdcc3244ba


Given these commits I have successfully performed a 4.5.1 -> 4.9.0-SNAPSHOT upgrade, as well as a 4.8.0 -> 4.9.0-SNAPSHOT upgrade.

Please retest given a new build.

Comment 2 Armine Hovsepyan 2013-09-09 10:30:49 UTC
verified.

Upgrade from 4.5 to 4.9 worked with build:48a76fe

Comment 3 Heiko W. Rupp 2013-09-24 19:09:29 UTC
Bulk closing of RHQ 4.9 verified items


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