Can not recover a clusetr in warning status by senlin-dashboard

Bug #1742091 reported by lidong on 2018-01-09
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin-dashboard
Undecided
lidong

Bug Description

when i shut down a instance related to a node in a cluster ,i found that the status of the node became error,the status of the cluster became warning after checking cluster. I wanted to recover the cluster ,but i failed by senlin-dashboard.

And i found that below:
in this file:.../senlin-dashboard/blob/master/senlin_dashboard/cluster/clusters/tables.py
line 91: return datum.status == "ERROR" in func allowed(self, request, datum).
and i changed it : return datum.status == "ERROR" or datum.status == "WARNING"
and i recovered the cluster ,the instance which i shut down was active ,running again.And the node、the cluster related were active again.

lidong (lidong007) on 2018-01-09
no longer affects: senlin
Changed in senlin-dashboard:
assignee: nobody → lidong (lidong007)

Fix proposed to branch: master
Review: https://review.openstack.org/532136

Changed in senlin-dashboard:
status: New → In Progress
lidong (lidong007) on 2018-01-09
description: updated
description: updated
lidong (lidong007) on 2018-01-10
description: updated
lidong (lidong007) on 2018-01-10
description: updated
description: updated

Reviewed: https://review.openstack.org/532136
Committed: https://git.openstack.org/cgit/openstack/senlin-dashboard/commit/?id=9df131cb02ca5267a09f2c488cccf24eca2c76da
Submitter: Zuul
Branch: master

commit 9df131cb02ca5267a09f2c488cccf24eca2c76da
Author: lidong <email address hidden>
Date: Tue Jan 9 17:49:15 2018 +0800

    Can not recover a clusetr in warning status by senlin-dashboard

    Change-Id: Id92daaf63912c441287836074a62741267ecfcd5
    Closes-Bug: #1742091

Changed in senlin-dashboard:
status: In Progress → Fix Released

This issue was fixed in the openstack/senlin-dashboard 0.8.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers