Postinsts question

Postinsts question

[Vuille, Martin (Martin)]

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

We are running with our rootfs mounted read-only.
Consequently, any postinsts that get deferred to first boot fail.

Is there a way to fail the build for any postinsts that can't
be performed during the build and have to be deferred?

MV

[-- Attachment #2: Type: text/html, Size: 2293 bytes --]

Re: Postinsts question

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

On 8 November 2016 at 23:23, Vuille, Martin (Martin) <vmartin@avaya.com>
wrote:

> Is there a way to fail the build for any postinsts that can’t
>
> be performed during the build and have to be deferred?
>
>
Sadly not that I'm aware of currently.  If you're using a sufficiently
recent release (and by that I mean 2.2 / morty) then there is integrated
support for image QA tests (added in oe-core c9bef2ec if you want to
backport it) which lets you write an image QA function that could verify
that there are no delayed postinsts present in the image.

This would be a sensible addition for read-only rootfs, would you mind
filing a bug?

Ross

[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

Re: Postinsts question

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]



On 11/8/16 3:23 PM, Vuille, Martin (Martin) wrote:
> We are running with our rootfs mounted read-only.
> 
> Consequently, any postinsts that get deferred to first boot fail.
> 
>  
> 
> Is there a way to fail the build for any postinsts that can’t
> 
> be performed during the build and have to be deferred?

I hope you are using "read-only-rootfs" in IMAGE_FEATURES

> 
>  
> 
> MV
> 
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: Postinsts question

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

On 8 November 2016 at 23:23, Vuille, Martin (Martin) <vmartin@avaya.com>
wrote:

> We are running with our rootfs mounted read-only.
>
> Consequently, any postinsts that get deferred to first boot fail.
>
>
>
> Is there a way to fail the build for any postinsts that can’t
>
> be performed during the build and have to be deferred?
>
>
I was looking at some other selftests today and a test suggested that this
already happens, and it's true.

If you add 'read-only-rootfs' to IMAGE_FEATURES then delayed postists are
fatal:

ERROR: core-image-sato-base-1.0-r0 do_rootfs: The following packages could
not be configured offline and rootfs is read-only: ['postinst-test-delayed']
ERROR: core-image-sato-base-1.0-r0 do_rootfs: Function failed: do_rootfs

Ross

[-- Attachment #2: Type: text/html, Size: 1782 bytes --]

Re: Postinsts question

[Vuille, Martin (Martin)]

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Thanks Ross, Khem

It looks like we aren’t setting ‘read-only-rootfs’

Our images and init are very customized, so we missed that.
Will look into it.

Regards,
MV

From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: November 09, 2016 08:19
To: Vuille, Martin (Martin)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Postinsts question


On 8 November 2016 at 23:23, Vuille, Martin (Martin) <vmartin@avaya.com<mailto:vmartin@avaya.com>> wrote:
We are running with our rootfs mounted read-only.
Consequently, any postinsts that get deferred to first boot fail.

Is there a way to fail the build for any postinsts that can’t
be performed during the build and have to be deferred?

I was looking at some other selftests today and a test suggested that this already happens, and it's true.

If you add 'read-only-rootfs' to IMAGE_FEATURES then delayed postists are fatal:

ERROR: core-image-sato-base-1.0-r0 do_rootfs: The following packages could not be configured offline and rootfs is read-only: ['postinst-test-delayed']
ERROR: core-image-sato-base-1.0-r0 do_rootfs: Function failed: do_rootfs

Ross

[-- Attachment #2: Type: text/html, Size: 6069 bytes --]