mail archive of the rauc mailing list
 help / color / mirror / Atom feed
* [RAUC] Custom Installation
@ 2017-07-12 11:21 Kilimci, Caglar
  2017-07-31 13:44 ` Enrico Joerns
  0 siblings, 1 reply; 3+ messages in thread
From: Kilimci, Caglar @ 2017-07-12 11:21 UTC (permalink / raw)
  To: rauc

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RAUC] Custom Installation
  2017-07-12 11:21 [RAUC] Custom Installation Kilimci, Caglar
@ 2017-07-31 13:44 ` Enrico Joerns
  2017-08-01 12:54   ` [RAUC] [External] " Kilimci, Caglar
  0 siblings, 1 reply; 3+ messages in thread
From: Enrico Joerns @ 2017-07-31 13:44 UTC (permalink / raw)
  To: Kilimci, Caglar; +Cc: rauc

Hi Caglar,

On 07/12/2017 01:21 PM, Kilimci, Caglar wrote:
> 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'.

hm, it looks as if you have a system.conf that does not have any slots 
defined, yet. Is that true? RAUC is not designed for this very special 
case it seems and I am not sure if it should support this.

> 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.

Well, this can truely be a bit confusing, but I thing everything is fine 
for now.


* [handler]
  This section is for the Bundle *Manifest* and its only purpose is to 
define a full-custom installation behavior (something that should be 
used for debugging or system fixing, only)

* [handlers]
  This section is for the *System Configuration* and allows to specify 
some handler scripts that can be called during the default installation 
routine, for example as pre- or post-install handlers.

Finally, the similar mechanism as [handlers] exists for Bundle 
*Manifests*, too. Here they are referred to as [hooks] (to not confuse 
too much with then [handler] section).


Hope that pointed it out a bit more clearly?


Best regards

Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
RAUC mailing list

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RAUC] [External] Re:  Custom Installation
  2017-07-31 13:44 ` Enrico Joerns
@ 2017-08-01 12:54   ` Kilimci, Caglar
  0 siblings, 0 replies; 3+ messages in thread
From: Kilimci, Caglar @ 2017-08-01 12:54 UTC (permalink / raw)
  To: Enrico Joerns; +Cc: rauc

Hi Enrico,

Thank you for your reply.

>> 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'.
>
>hm, it looks as if you have a system.conf that does not have any slots defined, yet. Is that true?

Actually there are 2 stots. Here is the system.conf:
root@phyboard-regor-am335x-1:~# cat /etc/rauc/system.conf
[system]
compatible=Phytec
bootloader=barebox

[keyring]
path=ca.cert.pem

[slot.rootfs.0]
device=/dev/mmcblk0p2
type=ext4
bootname=system1

[slot.rootfs.1]
device=/dev/mmcblk0p3
type=ext4
bootname=system2


>RAUC is not designed for this very special case it seems and I am not sure if it should support this.
It would be so good and introduce new functiality. As an example, a deployment server for updates is already requirement. With this functionality, this deployment server can deploy a custom script, too. In addition, there is not so much development involved because RAUC already has "this" function.

>> 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.
>
>Well, this can truely be a bit confusing, but I thing everything is fine for now.
>
>
>* [handler]
>  This section is for the Bundle *Manifest* and its only purpose is to
>define a full-custom installation behavior (something that should be
>used for debugging or system fixing, only)
>
>* [handlers]
>  This section is for the *System Configuration* and allows to specify
>some handler scripts that can be called during the default installation
>routine, for example as pre- or post-install handlers.
>
>Finally, the similar mechanism as [handlers] exists for Bundle
>*Manifests*, too. Here they are referred to as [hooks] (to not confuse
>too much with then [handler] section).
>
>
>Hope that pointed it out a bit more clearly?

Yes, thank you.

Best Regards,
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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-08-01 12:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-12 11:21 [RAUC] Custom Installation Kilimci, Caglar
2017-07-31 13:44 ` Enrico Joerns
2017-08-01 12:54   ` [RAUC] [External] " Kilimci, Caglar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox