Bug 1012263
| Summary: | jon server process cannot be stopped by rhqctl after failed server install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||
| Component: | Installer | Assignee: | RHQ Project Maintainer <rhq-maint> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | JON 3.2 | CC: | hrupp, jshaughn, mfoley, myarboro | ||||
| Target Milestone: | ER03 | ||||||
| Target Release: | JON 3.2.0 | ||||||
| Hardware: | sparc64 | ||||||
| OS: | Solaris | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: | |||||||
| Attachments: |
|
||||||
I believe this was fixed in master in commit e7f55. Although, I think that may have been in ER1, I'm not sure. Regardless, the new revert-failed-install logic, and to a degree, the default stopping of services by the install command, probably solve this problem. Moving to modified for ER3. Moving to ON_QA for testing. verified (no testing is needed) - server processes are not started if install failed. |
Created attachment 803252 [details] solaris-server_process.png Description of problem: jon server process cannot be stopped by rhqctl after failed server install Version-Release number of selected component (if applicable): JON 3.2 ER1 How reproducible: always Steps to Reproduce: 1. install and start storage with agent 2. install server so that it fails 3. run rhqctl stop --server 4. run rhqctl stop Actual results: After step3. Log shows server is not installed After step4. Storage and agent processes stopped, server stop ignored, rhq-server.pid visible, java process is active. Expected results: rhq-server.pid should be removed, server process should be stopped Additional info: screen-shot attached