commit 9b733bdc51d3f9abffa18863cad28b5dd9c92f6f
author Gunnar Mills <gmills@us.ibm.com> Fri Feb 23 21:16:20 2018 -0600
committer Gunnar Mills <gmills@us.ibm.com> Mon Mar 05 11:48:50 2018 -0600
tree 0c0e95469672db30dd17a3b21f3d05d68674b01d
parent 177b9e5d3fb402794651ae241d018585e72db70b

Determine "Functional" images by association

The functional, or running, images should be determined by looking
at the functional association, not by looking at priority 0.
An image could be functional but not priority 0, this happens
after activating a new image.

Get the functional images by looking at the endpoints of
/xyz/openbmc_project/software/functional.

Resolves openbmc/openbmc#2945

Tested: Verified the correct image is functional after activation
and during other times of code updating.
Change-Id: Ia5ad172b0874e634c0042576018b376b5260e31e
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

app/common/services/constants.js

diff --git a/app/common/services/constants.js b/app/common/services/constants.js
index c6d9a61..fd8204a 100644
--- a/app/common/services/constants.js
+++ b/app/common/services/constants.js
@@ -111,7 +111,8 @@
                 ],
                 SENSOR_SORT_ORDER_DEFAULT: 8,
                 FIRMWARE: {
-                  ACTIVATE_FIRMWARE: 'xyz.openbmc_project.Software.Activation.RequestedActivations.Active'
+                  ACTIVATE_FIRMWARE: 'xyz.openbmc_project.Software.Activation.RequestedActivations.Active',
+                  FUNCTIONAL_OBJPATH: '/xyz/openbmc_project/software/functional'
                 },
                 MESSAGES: {
                   SENSOR: {