Update System GUID handling to be more robust
If the service that owns the GUID has not yet started when
netipmid starts, netipmid was throwing an error and failing
to start. If the time difference was too great, it would fail
to re-start and then stay stopped. This makes the error
handling more robust so that the order is not so important.
Tested: started netipmid with and without the UUID service
running and restarted the service to ensure that
netipmid would stay running.
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
Change-Id: Id464330a2ba8416ff229fa258fff0ad7a1b8f51c
diff --git a/command/rakp34.cpp b/command/rakp34.cpp
index f14430e..7735d8d 100644
--- a/command/rakp34.cpp
+++ b/command/rakp34.cpp
@@ -244,7 +244,8 @@
std::advance(iter, sizeof(bmcSessionID));
// Managed System GUID
- std::copy_n(cache::guid.data(), cache::guid.size(), iter);
+ const Guid& guid = command::getSystemGUID();
+ std::copy_n(guid.data(), guid.size(), iter);
// Integrity Check Value
auto icv = authAlgo->generateICV(input);