| Age | Commit message (Collapse) | Author |
|---|
|
Update engine will provide this install indication for signal listeners
(specifically dlcservice) and status requesters to indicate whether
update engine is in the process of installing or updating. With this,
dlcservice will can be altered to not probe update engine for status
during a DLC uninstall.
The update engine client is also updated when getting the status from
update engine by using KeyValueStore printouts now.
Old output:
[0725/202915.815630:INFO:update_engine_client.cc(501)] Querying Update
Engine status...
LAST_CHECKED_TIME=1564102396
PROGRESS=1.000000
CURRENT_OP=UPDATE_STATUS_IDLE
NEW_VERSION=12354.0.2019_07_19_1136
NEW_SIZE=792
New output:
[0726/173804.558077:INFO:update_engine_client.cc(490)] Querying Update
Engine status...
CURRENT_OPERATION=UPDATE_STATUS_IDLE
IS_INSTALL=false
LAST_CHECKED_TIME=1564187860
NEW_SIZE=792
NEW_VERSION=12369.0.2019_07_26_0904
PROGRESS=1.0
BUG=chromium:871340
TEST=FEATURES="test" emerge-$BOARD update_engine update_engine-client system_api
TEST=/usr/bin/update_engine_client --status
Cq-Depend: chromium:1717661
Change-Id: Iaacea27e0fc0711200ec81fdebb7fef45f94af43
|
|
update_engine.proto
The current mechanism for interchaning the current operation of
update_engine is quite old and very fragile to changes. Currently, each
client defines its own set of operations, writes their own string to
enum conversion logic, etc. We need to unify all these clients to use
just one set of well defined operations.
This CL uses the new enum Operation from the protobuf instead of
transferring a string to identify the current operation of the
update_engine.
BUG=chromium:977320
TEST=precq
Cq-Depend: chromium:1690424
Change-Id: I4d3a2a142c169cf6c972fe58d1d8d936d2349eed
Reviewed-on: https://chromium-review.googlesource.com/1690683
Tested-by: Amin Hassani <ahassani@chromium.org>
Commit-Ready: Amin Hassani <ahassani@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Xiaochu Liu <xiaochu@chromium.org>
Reviewed-by: Sen Jiang <senj@chromium.org>
Reviewed-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-by: Ben Chan <benchan@google.com>
|
|
This codepath is not used anymore.
Bug: None
Test: `make checkbuild`.
Change-Id: I0f7f22d63cb2c3fbfabcda25763160e2470ef2c5
|
|
The new WeaveServiceInterface abstracs the registration and interaction
with weave whenever present. The compilation and usage of weave is
based on the BRILLO_USE_WEAVE flag.
When enabled, update_engine registers the "_updater" component with
methods to force-check for an update and change channels.
Bug: 24386758
Bug: 24386768
Test: Deployed on edison, weave commands and state available online.
Change-Id: Ic49111772e123b8a2b1971da92fe65785f186ccd
|
|
This patch splits from the main libupdate_engine code the part that
is strictly used to download and apply a payload into a new static
library, moving the code to subdirectories. The new library is divided
in two subdirectories: common/ and payload_consumer/, and should not
depend on other update_engine files outside those two subdirectories.
The main difference between those two is that the common/ tools are more
generic and not tied to the payload consumer process, but otherwise they
are both compiled together.
There are still dependencies from the new libpayload_consumer library
into the main directory files and DBus generated files. Those will be
addressed in follow up CLs.
Bug: 25197634
Test: FEATURES=test emerge-link update_engine; `mm` on Brillo.
Change-Id: Id8d0204ea573627e6e26ca9ea17b9592ca95bc23
|
|
This is useful for decyphering the statuses returned over
the DBus interface.
Bug: 24547247
Test: mmm system/update_engine; emerge-panther update_engine
Change-Id: Ifce74450209a7e7cb632c2fee7b54364ffaf3ff5
|
|
This allows us to easily share it between the update_engine proper
and a forthcoming client library.
Bug: 24547247
Test: mmm system/update_engine; emerge-panther update_engine
Change-Id: I8c0db7a0f95dd6368bfc886f1b0d1a9d2efb461f
|
