commit | a6963590773d4dea762571695e7c47d830aba5d7 | [log] [tgz] |
---|---|---|
author | Adriana Kobylak <anoo@us.ibm.com> | Fri Sep 07 14:13:29 2018 -0500 |
committer | Adriana Kobylak <anoo@us.ibm.com> | Wed Sep 19 11:34:29 2018 -0500 |
tree | 1cbd720fe1c248a8e38ef3ff2938ef4f21906d3e | |
parent | 1e648729a516d298a3eb1b9b0e88513cee48c7d8 [diff] |
Fix being able to activate a Failed version When an activation fails, the version is marked as Failed. On a subsequent activation, the bmc updater core dumps due to 2 issues during the freeSpace call: 1. The Failed activation doesn't have a Priority object, so default its priority to a large value. 2. If the subsequent activation is to the same version id, then freeSpace should not do an erase on it, because that removes the activations object that it's trying to activate. Tested: Verified that doing an activation after a version was marked as Failed did not core dump the updater anymore. Change-Id: Iba36497b53738e00283cfec55e8c666f943cd5d5 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture
To build this package, do the following steps: 1. ./bootstrap.sh 2. ./configure ${CONFIGURE_FLAGS} 3. make To clean the repository run `./bootstrap.sh clean`.