Limit the number of Active pnor versions

- We need to limit the number of pnor versions because
  pnor chip has limited space. If we run out of space
  and the user tries another pnor code update then the
  update will fail.
- Currently we can only hold two images on pnor at this
  point. As we continue to decrease the size of pnor image
  we will increment the number of active pnor chips we can
  hold.
- This check will need to be removed once we have complete
  issue #1402 which will automatically monitor the flash
  usage and delete any image accordingly.

Resolves openbmc/openbmc#2155

Change-Id: Id62ba8554fba1ddb78286f70b0c3482a7beb8a6b
Signed-off-by: Saqib Khan <khansa@us.ibm.com>

1 files changed, 1 insertions, 0 deletions

diff --git a/activation.cpp b/activation.cpp
index 55ce08ee9..3f16b7b15 100755
--- a/activation.cpp
+++ b/activation.cpp
@@ -115,6 +115,7 @@ auto Activation::activation(Activations value) ->
 
     if (value == softwareServer::Activation::Activations::Activating)
     {
+        parent.freeSpace();
         softwareServer::Activation::activation(value);
 
         if (squashfsLoaded == false && rwVolumesCreated == false)