Bug 1027892 - Unable to fetch storage nodes when >1 nodes failed to connect to cluster
Summary: Unable to fetch storage nodes when >1 nodes failed to connect to cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER07
: JON 3.2.0
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 1027740
Blocks: 1012435
TreeView+ depends on / blocked
 
Reported: 2013-11-07 13:15 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:02 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:42:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Comment 1 John Sanda 2013-11-13 01:15:27 UTC 
Changes have been pushed to master. After some further testing and review in master I will cherry-pick the changes to the release branch. See bug 1027740 for details.
Comment 2 John Sanda 2013-11-14 19:11:03 UTC 
Changes have been committed to the release/jon3.2.x branch.

commit hashes:
2d1ba2cd4
3e699425
1a1afd5802
5a9ce1e6
cdaab06e
ef89ef122b
49028b166a
3cbd029d6821
Comment 3 Simeon Pinder 2013-11-19 15:48:31 UTC 
Moving to ON_QA as available for testing with new brew build.
Comment 4 John Sanda 2013-11-20 12:06:34 UTC 
I am moving this back to ASSIGNED because of a bug in one of my commits. The code changes introduced by commit 49028b166a will produce a ClassCastException when there are unacked alerts. I will have the fix ready soon.
Comment 5 John Sanda 2013-11-20 16:56:00 UTC 
Fix for the unacked alert count query has been committed to release/jon3.2.x branch.

commit hash: c9eda2b506
Comment 6 Simeon Pinder 2013-11-22 04:44:58 UTC 
Moving to ER07 target milestone and MODIFIED as initially rejected by QE because of bad ER6 build but put into varied states(MODIFIED & ASSIGNED).
Comment 7 Simeon Pinder 2013-11-22 05:01:46 UTC 
Moving to ON_QA as available to test in ER7 and later brew builds.
Note You need to log in before you can comment on or make changes to this bug.