[RAUC] Custom Installation

["Kilimci, Caglar" <caglar.kilimci@accenture.com>]

Hi all,

I have been using RAUC and it is fantastic.

Normally, my system has two root file systems and install other part and reboots. Nothing special, neither handlers nor hooks. But I have wondered, if I create a bundle that contains a script and runs that script instead of regular `rauc install` command. So I created one without any root fs but handler. But installation failed.

Here is my manifest file:
[update]
compatible=Phytec
version=caglar_v2
description=update-bundle
build=20170711235827

[handler]
filename=/usr/bin/custom_install.sh
args=install

Here is the output of install and log messages:
root@phyboard-regor-am335x-1:/update# rauc install caglar.raucb
trying to contact rauc service
rauc-Message: installing /update/caglar.raucb: installing

(rauc:756): rauc-WARNING **: rauc service disappeared

D-Bus error while installing `/update/caglar.raucb`
root@phyboard-regor-am335x-1:/update# Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.notice dbus[205]: [system] Activating via systemd: service name='de.pengutronix.rauc' unit='rauc.service'
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info systemd[1]: Starting Rauc Update Service...
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.notice dbus[205]: [system] Successfully activated service 'de.pengutronix.rauc'
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info systemd[1]: Started Rauc Update Service.
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: input bundle: /update/caglar.raucb
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: Active slot bootname: system2
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc-Message: Mounting bundle '/update/caglar.raucb' to '/run/rauc/bundle'
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc-Message: installing /update/caglar.raucb: started
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc-Message: installing /update/caglar.raucb: Checking and mounting bundle...
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc-Message: Reading bundle: /update/caglar.raucb
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc-Message: Verifying bundle...
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: **
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.info rauc[759]: rauc:ERROR:../git/src/install.c:294:determine_target_install_group: assertion failed (slotclasses->len > 0): (0 > 0)
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.notice systemd[1]: rauc.service: Main process exited, code=killed, status=6/ABRT
Jul 12 11:03:20 phyboard-regor-am335x-1 daemon.notice systemd[1]: rauc.service: Unit entered failed state.
Jul 12 11:03:21 phyboard-regor-am335x-1 daemon.warn systemd[1]: rauc.service: Failed with result 'signal'.

PS: By the way, documentation of handler [1] is out of date, I guess. Group name is changed from handlers to handler and does not accept key value of *install. If you explain more, I can update and send you pull request.

Thank you for your help.

[1] https://rauc.readthedocs.io/en/latest/using.html#system-based-customization-handlers

Sincerely,
Caglar Kilimci

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com

_______________________________________________
RAUC mailing list