Bug 974592
| Summary: | rhq storage not discovered / not auto-imported by server | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||
| Component: | Core Server | Assignee: | RHQ Project Maintainer <rhq-maint> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | JON 3.2 | CC: | jsanda, jshaughn, mfoley | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-06-19 13:52:35 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 | ||||||
| Attachments: |
|
||||||
|
Description
Armine Hovsepyan
2013-06-14 14:07:42 UTC
Assuming this is a regression it must be recent as I am not seeing anything like this locally... Yes, this is a regression - was not visible for previous builds. Before stopping in reproduction step 3, are you sure the agent was connected and completed its discovery? I am not sure. Please move it to ON_QA if a retest is needed. I have not been able to reproduce this behavior, so I moving back to ON_QA to be retested. Hi Jay, Please get the screen-shots of agent before migration (http://d.pr/i/3qgw) with rhq storage pugin screen-shot (http://d.pr/i/I7sQ). Env details will paste privately. Regards, Armine H. I successfully upgraded from RHQ 4.5.1 to RHQ 4.8.0-SNAPSHOT. After the upgrade the Storage node was discovered and auto-imported, and the alert template was injected and applied. This was on Windows. There were some bug fixes applied to get my upgrade working successfully although none had to do with the actual auto-import. I did solve two issues that were non-windows related. First, I added the --storage-config option to the upgrade command; this allows the upgrade from pre-48 to specify initial non-default values for storage props (which I needed). Second, I solved a problem with the agent upgrade if the agent was in the default location (no --from-agent-dir being specified). If you are still seeing bad behavior perhaps we can go through the steps together. Let me know.
As an aside, the fixes I added are all in master as of:
commit 72f114cb01f3286696be68912280906b1954febe
Author: Jay Shaughnessy <jshaughn>
Date: Tue Jun 18 15:59:02 2013 -0400
Fix upgrade issues
- fix agent upgrade of existing agent in the default location
(i.e. no --from-agent-dir specified)
- On Windows, ensure exit codes are passed back from the storage installer
and rhqctl scripts. The former is very important as otherwise errors
in the storage installer do not prevent an attempt to upgrade/install the
server.
Tried for Linux upgrade fom 4.5 to 4.8 - the same issue is present. please get screen-shot attached. Created attachment 762883 [details]
storage_node_autoImport
upgrade from 4.5.1 to 48 worked fine -> http://d.pr/i/UAmm. Previous upgrade was on 4.5snapshot which didn't work. Conclution made - upgrade only from rhq-> rhq and jon->jon and not use snapshot versions. Closing bug as wontfix since the scenarios issue appears are not supported. |