tree 38ddd5c638b19fee5fb0ac9fd34b1d247bb4472e
parent b8590f56389a9dfd1af6ae4f722cc2fed46de918
author Shawn McCarney <shawnmm@us.ibm.com> 1735950465 -0600
committer Shawn McCarney <shawnmm@us.ibm.com> 1736908229 -0600

Handle repeated activation requests

PSU code versions are represented on D-Bus as a combination of Version
and Activation objects.

When this application determines that one or more PSUs need a code
update, it sets the RequestedActivation property to Active on the
Activation object. This triggers the code update.

The code is updated on each PSU in sequential order. This process can
take several minutes depending on the PSU type and number of PSUs.

During this long code update process, it is possible for one of the
following to occur:
* New PSU information is found on D-Bus
* A new PSU is plugged in (hot-plug)

If the new PSU requires a code update, the application will again set
the RequestedActivation property to Active on the Activation object. If
a code update is already occurring, the property change is currently
ignored. That means that the new PSU will not be code updated.

Enhance the application so that the second code update request is not
ignored. If it is requested while another code update is already in
progress, then restart the code update process once the current one
completes.

Tested:
* Tested a repeated code update request occurring due to new PSU
  information found on D-Bus.
* Tested a repeated code update request occurring due to a new PSU
  being plugged in.
* Verified that code update cycle was repeated if a request was deferred
  and the previous code update was successful.
* Verified that code update cycle was not repeated if a request was
  deferred and the previous code update failed.
* See the complete test plan at
  https://gist.github.com/smccarney/424f92af23fc25c6c2b6f67ee54d8919

Change-Id: Ie73e3f83c68945f6c85c2747003c36637791a24b
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>