update_engine: Added more logging and debugging for rollback checking
To help troubleshoot issues similar to http://crbug.com/356975 I added
more logging in DBus methods of update_engine to trace various stages
of determining available boot partitions, etc.
Also added two more DBus methods - to get the suggested rollback
partition name (and switched CanRollback to use this method) and
the list of availavle kernel partitions along with the 'bootable'
flag for each.
Changed update_engine_client to show the name of avaiable rollback
partition with --can_rollback and also added --show_kernels to
output list of available kernel partitions and whether each partition
is bootable or not.
BUG=None
TEST=Unit tests pass
Change-Id: Ib7f92a6460c578953ea1ba9b23bd0669acb0e22f
Reviewed-on: https://chromium-review.googlesource.com/191949
Reviewed-by: Alex Vakulenko <avakulenko@chromium.org>
Tested-by: Alex Vakulenko <avakulenko@chromium.org>
Commit-Queue: Alex Vakulenko <avakulenko@chromium.org>
diff --git a/update_engine.xml b/update_engine.xml
index 3891374..b99f345 100644
--- a/update_engine.xml
+++ b/update_engine.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8" ?>
+<?xml version="1.0" encoding="utf-8" ?>
<!-- COPYRIGHT HERE
dbus-binding-tool -mode=glib-server -prefix=update_engine update_engine.xml
> glib_server.h
@@ -81,5 +81,11 @@
<method name="GetPrevVersion">
<arg type="s" name="prev_version" direction="out" />
</method>
+ <method name="GetKernelDevices">
+ <arg type="s" name="kernel_devices" direction="out" />
+ </method>
+ <method name="GetRollbackPartition">
+ <arg type="s" name="rollback_partition_name" direction="out" />
+ </method>
</interface>
</node>