Bug 1149687
Summary: | Storage Node's cluster status is DOWN when cluster maintenance is scheduled | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | John Sanda <jsanda> | ||||
Component: | Core Server, UI, Storage Node | Assignee: | Jirka Kremser <jkremser> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Armine Hovsepyan <ahovsepy> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | JON 3.3.0 | CC: | ahovsepy, jsanda, lzoubek, mfoley | ||||
Target Milestone: | ER05 | ||||||
Target Release: | JON 3.3.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-12-11 14:00:23 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: | |||||||
Attachments: |
|
Description
John Sanda
2014-10-06 13:14:47 UTC
I wasn't able to reproduce. But from looking into the code I found following: UI displays the same text as StorageNode.getStatus() returns. The implementation of this method [1] relies on the operationMode field. It returns Status.NORMAL iff operationMode == OperationMode.NORMAL. I guess running the 'add maintenance' operation sets the field to OperationMode.ADD_MAINTENANCE and the getStatus() returns correctly DOWN. Perhaps we should consider the ADD_MAINTENANCE operationMode also as NORMAL cluster status. In other words: if (operationMode == OperationMode.NORMAL || operationMode == OperationMode.ADD_MAINTENANCE) { return Status.NORMAL; } [1]: https://github.com/rhq-project/rhq/blob/master/modules/core/domain/src/main/java/org/rhq/core/domain/cloud/StorageNode.java#L241:L265 note: 'add maintenance' operation is run for new nodes where it makes sense not to set the cluster state to NORMAL until it is successfully finished. On the other hand, it can be run also explicitly whenever user runs the operation and it is strange to see it in UI that storage node is DOWN only because of the logic mentioned in my previous comment. I produced by running StorageNodeManager.runClusterMaintenance() from the CLI, not by running the add maintenance resource operation. branch: master link: https://github.com/rhq-project/rhq/commit/112bd1d85 time: 2014-10-13 18:00:52 +0200 commit: 112bd1d8586aba237a91d5008c1bd36c10aeff90 author: Jirka Kremser - jkremser message: [BZ 1149687] - Storage Node's cluster status is DOWN when cluster maintenance is scheduled - considering the MAINTENANCE operation mode as NORMAL cluster status. branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/68519e5c2 time: 2014-10-14 15:18:21 +0200 commit: 68519e5c2ac8370dd1e1e17a50747c03f7f09e4b author: Jirka Kremser - jkremser message: [BZ 1149687] - Storage Node's cluster status is DOWN when cluster maintenance is scheduled - considering the MAINTENANCE operation mode as NORMAL cluster status. (cherry picked from commit 112bd1d8586aba237a91d5008c1bd36c10aeff90) Signed-off-by: Libor Zoubek <lzoubek> Moving to ON_QA as available to test with the latest brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=394734 Created attachment 949892 [details]
cluster_state_runMaintenance
verified in JON 3.3 ER05 screenshot attached (checked during and after runClusterMaintenance ) |