Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build

Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build

[Shrikant Bobade]

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

Hi All,

Please have a look, using isar master branch I am trying to build 
"mc:qemuarm-buster:isar-image-base",
To enable selinux support added selinux policy package 
https://packages.debian.org/buster/selinux-policy-default 
but getting "Value too large for defined data type error" during  build.

Build Details:  https://github.com/ilbers/isar "master" branch
Build Host: Buster Debian 10
Machine Name: qemuarm

Below are my local.conf contents.
DISTRO ??= "debian-buster"
MACHINE ??= "qemuarm"
DISTRO_ARCH ??= "armhf"

# selinx policy packages
IMAGE_PREINSTALL_append = " \
    .
    .
    selinux-policy-default               \
"

Error log:
Setting up selinux-policy-default (2:2.20190201-2) ...
Updating selinux default policy (this step might take a 
moment)...libsemanage.semanage_direct_list_all: Error while scanning 
directory /var/lib/selinux/default/active/modules. (Value too large for 
defined data type).
/usr/sbin/semodule:  Failed on full!
Could not read the contents of /var/lib/selinux/default/active: Value too 
large for defined data type
libsemanage.semanage_make_sandbox: Could not copy files to sandbox 
/var/lib/selinux/default/tmp. (Value too large for defined data type).
/usr/sbin/semodule:  Failed on /usr/share/selinux/default/abrt.pp.bz2!
 failed.
dpkg: error processing package selinux-policy-default (--configure):
 installed selinux-policy-default package post-installation script 
subprocess returned error exit status 1


Debugging further, meanwhile I would like to check if anyone else also 
faced similar issue
Any pointers will be a great help!. This issue only reproducible on non 
amd64.


Thanks
Shrikant Bobade


[-- Attachment #1.2: Type: text/html, Size: 2224 bytes --]

Re: Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build

[Jan Kiszka]

On 28.01.20 14:41, Shrikant Bobade wrote:
> Hi All,
> 
> Please have a look, using isar master branch I am trying to build 
> "mc:qemuarm-buster:isar-image-base",
> To enable selinux support added selinux policy package 
> https://packages.debian.org/buster/selinux-policy-default
> but getting "Value too large for defined data type error" during  build.
> 
> Build Details:  https://github.com/ilbers/isar "master" branch
> Build Host: Buster Debian 10
> Machine Name: qemuarm
> 
> Below are my local.conf contents.
> DISTRO ??= "debian-buster"
> MACHINE ??= "qemuarm"
> DISTRO_ARCH ??= "armhf"
> 
> # selinx policy packages
> IMAGE_PREINSTALL_append = " \
>      .
>      .
>      selinux-policy-default               \
> "
> 
> Error log:
> Setting up selinux-policy-default (2:2.20190201-2) ...
> Updating selinux default policy (this step might take a 
> moment)...libsemanage.semanage_direct_list_all: Error while scanning 
> directory /var/lib/selinux/default/active/modules. (Value too large for 
> defined data type).
> /usr/sbin/semodule:  Failed on full!
> Could not read the contents of /var/lib/selinux/default/active: Value 
> too large for defined data type
> libsemanage.semanage_make_sandbox: Could not copy files to sandbox 
> /var/lib/selinux/default/tmp. (Value too large for defined data type).
> /usr/sbin/semodule:  Failed on /usr/share/selinux/default/abrt.pp.bz2!
>   failed.
> dpkg: error processing package selinux-policy-default (--configure):
>   installed selinux-policy-default package post-installation script 
> subprocess returned error exit status 1
> 
> 
> Debugging further, meanwhile I would like to check if anyone else also 
> faced similar issue
> Any pointers will be a great help!. This issue only reproducible on non 
> amd64.
> 

I've reproduced here as well. Maybe it's an issue of the qemu-user 
environment, and that's why we don't see it on x86.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: Regarding IMAGE_PREINSTALL of package "selinux-policy-default" fails on buster qemuarm build

[Shrikant Bobade]

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



On Wednesday, 29 January 2020 03:41:05 UTC+5:30, Jan Kiszka wrote:
>
> On 28.01.20 14:41, Shrikant Bobade wrote: 
> > Hi All, 
> > 
> > Please have a look, using isar master branch I am trying to build 
> > "mc:qemuarm-buster:isar-image-base", 
> > To enable selinux support added selinux policy package 
> > https://packages.debian.org/buster/selinux-policy-default 
> > but getting "Value too large for defined data type error" during  build. 
> > 
> > Build Details:  https://github.com/ilbers/isar "master" branch 
> > Build Host: Buster Debian 10 
> > Machine Name: qemuarm 
> > 
> > Below are my local.conf contents. 
> > DISTRO ??= "debian-buster" 
> > MACHINE ??= "qemuarm" 
> > DISTRO_ARCH ??= "armhf" 
> > 
> > # selinx policy packages 
> > IMAGE_PREINSTALL_append = " \ 
> >      . 
> >      . 
> >      selinux-policy-default               \ 
> > " 
> > 
> > Error log: 
> > Setting up selinux-policy-default (2:2.20190201-2) ... 
> > Updating selinux default policy (this step might take a 
> > moment)...libsemanage.semanage_direct_list_all: Error while scanning 
> > directory /var/lib/selinux/default/active/modules. (Value too large for 
> > defined data type). 
> > /usr/sbin/semodule:  Failed on full! 
> > Could not read the contents of /var/lib/selinux/default/active: Value 
> > too large for defined data type 
> > libsemanage.semanage_make_sandbox: Could not copy files to sandbox 
> > /var/lib/selinux/default/tmp. (Value too large for defined data type). 
> > /usr/sbin/semodule:  Failed on /usr/share/selinux/default/abrt.pp.bz2! 
> >   failed. 
> > dpkg: error processing package selinux-policy-default (--configure): 
> >   installed selinux-policy-default package post-installation script 
> > subprocess returned error exit status 1 
> > 
> > 
> > Debugging further, meanwhile I would like to check if anyone else also 
> > faced similar issue 
> > Any pointers will be a great help!. This issue only reproducible on non 
> > amd64. 
> > 
>
> I've reproduced here as well. Maybe it's an issue of the qemu-user 
> environment, and that's why we don't see it on x86. 
>

Thanks for checking and pointers.!

-Best Regards
Shrikant


> Jan 
>
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE 
> Corporate Competence Center Embedded Linux 
>

[-- Attachment #1.2: Type: text/html, Size: 4047 bytes --]