Details
Description
It seems the JS for this section is prioritizing the fact that the node was going to be failed over above the fact that the node is no longer available.
I'm not sure what the server-side logic relationship is in this situation, but hopefully it's just a matter of re-prioritizing some conditions in the UI JS.
I'm not sure what the server-side logic relationship is in this situation, but hopefully it's just a matter of re-prioritizing some conditions in the UI JS.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Gerrit Reviews
Benjamin Young
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | Screen shot 2012-02-03 at 10.19.02 AM.png [ 12185 ] |
Benjamin Young
made changes -
| Attachment | Screen shot 2012-02-03 at 10.19.07 AM.png [ 12186 ] |
Farshid Ghods
made changes -
| Labels | customer |
Aleksey Kondratenko
made changes -
| Assignee | Aleksey Kondratenko [ alkondratenko ] | Pavel Blagodov [ pavel ] |
Pavel Blagodov
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Pavel Blagodov
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |