Leo, Satoe is right, if you are re-opening, please move it back to ON_DEV or ASSIGNED. Drew, in terms of the empty state, look at the screenshot attachment. The is no power state value in the field. Leo, please confirm that is what you mean. Leo, please confirm happy path of all VMs in the same state, does the power button work correctly up and down (with a correct field value). And then confirm if we have an issue when multiple VMs get into separate power state thereby confusing the app (which would most likely be a separate BZ).
*** Bug 1405055 has been marked as a duplicate of this bug. ***
https://github.com/ManageIQ/manageiq/pull/13232
The PR from comment 9 is really a PR for the upstream BZ - https://bugzilla.redhat.com/show_bug.cgi?id=1394202
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/a5486c586099a8312e5ac8dddd4969b3980e5b99 commit a5486c586099a8312e5ac8dddd4969b3980e5b99 Author: Greg McCullough <gmccullo> AuthorDate: Mon Jan 23 16:59:02 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Mon Jan 23 18:15:34 2017 -0500 Merge pull request #13232 from syncrou/assume_when_all_nil_actions Allow a service power state to correctly handle nil actions (cherry picked from commit 656bbc8e32f9b2d8a64d2e998350fb6f73b75a14) https://bugzilla.redhat.com/show_bug.cgi?id=1402995 app/models/service.rb | 34 +++++++++++++++++---- spec/models/service_spec.rb | 74 +++++++++++++++++++++++++++++++++++++++------ 2 files changed, 92 insertions(+), 16 deletions(-)
It is the expected behavior - though - There is another PR - https://github.com/ManageIQ/manageiq-ui-service/pull/406 That once implemented (see: https://github.com/ManageIQ/manageiq-ui-service/pull/406#issuecomment-271744784) will speed up the power_status without requiring the extra reload (or navigation back into the service details page.)
Backport PR - https://github.com/ManageIQ/manageiq-ui-service/pull/493
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:0898