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/guid.hpp b/command/guid.hpp
index 60a76a5..3bd8597 100644
--- a/command/guid.hpp
+++ b/command/guid.hpp
@@ -20,19 +20,11 @@
* @return If UUID is successfully read from the Chassis DBUS object, then the
* GUID is returned, else a canned GUID is returned
*/
-Guid getSystemGUID();
+const Guid& getSystemGUID();
/**
* @brief Register the callback to update the cache when the GUID changes
*/
void registerGUIDChangeCallback();
-void getUIDObjectInfo();
} // namespace command
-
-namespace cache
-{
-
-extern command::Guid guid;
-
-} // namespace cache