Update Control Map clarification

General Discussions
1

Can I continue deployment pause, that was initiated from mender UI, on device?

I am setting pause after Download in the Mender UI, and while device in pause I am sending (one time) map with continue action, but it is being ignored

Here is the log from mender-client

2021-12-09 13:21:20 +0000 UTC info: Running Mender client version: 3.1.0
2021-12-09 13:21:21 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2021-12-09 13:21:21 +0000 UTC info: No public key was provided for authenticating the artifact
2021-12-09 13:21:23 +0000 UTC info: State transition: update-store [Download_Enter] -> update-after-store [Download_Leave]
2021-12-09 13:21:23 +0000 UTC info: State transition: update-after-store [Download_Leave] -> mender-update-control [none]
2021-12-09 13:21:23 +0000 UTC info: Executing script: Download_Leave_00
2021-12-09 13:21:23 +0000 UTC info: Collected output (stderr) while running script /etc/mender/scripts/Download_Leave_00
mender:artifact_name=6gb-rootfs-release: Download_Leave_00 was called!
mender:Returning  from /etc/mender/scripts/Download_Leave_00 state script

---------- end of script output
2021-12-09 13:21:23 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:23 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:23 +0000 UTC info: Next update refresh from the server in: 2.279867719s
2021-12-09 13:21:23 +0000 UTC info: Forced wake-up from sleep
2021-12-09 13:21:23 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control [none]
2021-12-09 13:21:23 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:23 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:23 +0000 UTC info: Next update refresh from the server in: 2.238452688s
2021-12-09 13:21:25 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control-refresh-maps [none]
2021-12-09 13:21:25 +0000 UTC info: Validating the Update Info: https://s3.amazonaws.com/hosted-mender-artifacts/61790d67aa213e9e2856f1e7/67cf4ff2-7374-40d9-904b-f4adc2f7e9aa?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAQWI25QR6NDALMYE2%2F20211209%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211209T132125Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=3cc663a9614352527f23cb673a87cf2810028ce9be8d6aaa8b9269c007559bd5 [name: heliboards-1.8; devices: [raspberrypi4]]
2021-12-09 13:21:25 +0000 UTC info: State transition: mender-update-control-refresh-maps [none] -> mender-update-control [none]
2021-12-09 13:21:25 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:25 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:25 +0000 UTC info: Next update refresh from the server in: 4.967974073s
2021-12-09 13:21:25 +0000 UTC info: Forced wake-up from sleep
2021-12-09 13:21:25 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control [none]
2021-12-09 13:21:25 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:25 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:26 +0000 UTC info: Next update refresh from the server in: 4.921869971s
2021-12-09 13:21:30 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control-refresh-maps [none]
2021-12-09 13:21:31 +0000 UTC info: Validating the Update Info: https://s3.amazonaws.com/hosted-mender-artifacts/61790d67aa213e9e2856f1e7/67cf4ff2-7374-40d9-904b-f4adc2f7e9aa?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAQWI25QR6NDALMYE2%2F20211209%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211209T132131Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&response-content-type=application%2Fvnd.mender-artifact&X-Amz-Signature=caccf2acb8d8e139ccb5652690f052510c1504e6367c8e536bd4149f85df02b0 [name: heliboards-1.8; devices: [raspberrypi4]]
2021-12-09 13:21:31 +0000 UTC info: State transition: mender-update-control-refresh-maps [none] -> mender-update-control [none]
2021-12-09 13:21:31 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:31 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:31 +0000 UTC info: Next update refresh from the server in: 4.96424849s
2021-12-09 13:21:31 +0000 UTC info: Forced wake-up from sleep
2021-12-09 13:21:31 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control [none]
2021-12-09 13:21:31 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:31 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:31 +0000 UTC info: Next update refresh from the server in: 4.927103386s
2021-12-09 13:21:33 +0000 UTC info: Received an update control map via D-Bus: {
	"priority": 10,
	"states": {
		"ArtifactInstall_Enter": {
			"action": "continue"
		},
		"ArtifactReboot_Enter": {
			"action": "continue"
		},
		"ArtifactCommit_Enter": {
			"action": "continue"
		}
	},
	"id": "01234567-89ab-cdef-0123-456789abcdef"
}
2021-12-09 13:21:33 +0000 UTC info: Forced wake-up from sleep
2021-12-09 13:21:33 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control [none]
2021-12-09 13:21:33 +0000 UTC info: Update Control: Pausing before entering update-install state
2021-12-09 13:21:33 +0000 UTC info: State transition: mender-update-control [none] -> mender-update-control-pause [none]
2021-12-09 13:21:33 +0000 UTC info: Next update refresh from the server in: 3.523702705s
2021-12-09 13:21:36 +0000 UTC info: State transition: mender-update-control-pause [none] -> mender-update-control-refresh-maps [none]
2

Yes, you can, but continue is the default action and has the lowest priority of all actions, regardless of the priority field. If you want to force it you have to use force_continue instead, in addition to priority.

1 Like
3

Also note that it’s not advisable to use the highest priority, using priority: 1 is enough, since the UI uses 0. The reason is that if you sometime in the future make a mistake in your device Update Control Map, you can then override that from the server with an even higher priority. This is not possible if you have already used the highest one.