Bug #4163
Extra "refresh" needed in sunstone before available actions are updated
| Status: | Closed | Start date: | 11/17/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | duplicate | Pull request: | ||
| Affected Versions: | OpenNebula 4.14 |
Description
Quite often I have to click on the "refresh" button in sunstone when I want to perform an action (poweroff, release, shutdown, etc.) while the VM actually hasn't changed it's state for a while. So somehow sunstone is using old state or hasn't updated it's state. I'm able to reproduce, but not sure what exactly triggers this. Can't (yet) tell which circumstances trigger this behaviour.
Related issues
History
#1
Updated by Carlos Martín over 5 years ago
- Status changed from Pending to Closed
- Resolution set to duplicate
Hi,
This is probably the same bug as #4025. Sometimes a vm list refresh can return when the vm details are visible, and that enables/disables the buttons according to the selected vms in the hidden table, instead of the currently visible VM. It should be fixed in 4.14.2
#2
Updated by Carlos Martín over 5 years ago
- Duplicates Bug #4025: sunstone: VM actions greyed out in VM details added