Bug 1004731
| Summary: | rhqctl upgrade on windows doesn't work correctly | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Armine Hovsepyan <ahovsepy> |
| Component: | Installer | Assignee: | Jay Shaughnessy <jshaughn> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.9 | CC: | hrupp, jshaughn, mfoley |
| Target Milestone: | --- | ||
| Target Release: | RHQ 4.9 | ||
| Hardware: | x86_64 | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-24 19:09:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 951619 | ||
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. verified. Upgrade from 4.5 to 4.9 worked with build:48a76fe Bulk closing of RHQ 4.9 verified items |
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