Started by an SCM changeOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmaster00002148152148151.0642464240221239642364233311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip17371f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/master1f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cihttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/3311/artifacthttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/changeshttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/3311/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/3311/testReportfalse#3311214815173257update-osmo-ci-on-slaves #33113311falsefalse331158351SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/3311/ansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/util/known_hostseditansible/hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithosmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/002217753177531.00003311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#33111775313341update-osmo-ci-on-slaves » build4-deb12build-ansible #33113311falsefalse331158356SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=build4-deb12build-ansible/3311/build4-deb12build-ansibleansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/util/known_hostseditansible/hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/002217107171071.00113311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#33111710712541update-osmo-ci-on-slaves » build5-deb12build-ansible #33113311falsefalse331158357SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=build5-deb12build-ansible/3311/build5-deb12build-ansibleansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/hostseditansible/util/known_hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/0000473647361.00003311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip17371f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/master1f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#331147364646update-osmo-ci-on-slaves » gtp0-deb10fr #33113311falsefalse331158352SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=gtp0-deb10fr/3311/gtp0-deb10fransible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/util/known_hostseditansible/hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/000039946399461.0018183311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#33113994627667update-osmo-ci-on-slaves » lx2-raspbian12build-ansible #33113311falsefalse331158354SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=lx2-raspbian12build-ansible/3311/lx2-raspbian12build-ansibleansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/hostseditansible/util/known_hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/00002135942135941.00003311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#3311213594171900update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-1 #33113311falsefalse331158353SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=rpi4-raspbian12build-ansible-1/3311/rpi4-raspbian12build-ansible-1ansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/hostseditansible/util/known_hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/00111004261004261.00113311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#331110042672139update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-2 #33113311falsefalse331158358SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=rpi4-raspbian12build-ansible-2/3311/rpi4-raspbian12build-ansible-2ansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/util/known_hostseditansible/hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/001158544585441.00003311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wipbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#33115854443363update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-3 #33113311falsefalse331158359SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=rpi4-raspbian12build-ansible-3/3311/rpi4-raspbian12build-ansible-3ansible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/hostseditansible/util/known_hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver SmithOSMO_BRANCH_CImasterOSMO_BRANCH_DOCKER_PLAYGROUNDmasterStarted by upstream project "update-osmo-ci-on-slaves" build number 3,3113311update-osmo-ci-on-slavesjob/update-osmo-ci-on-slaves/0011823882381.0029293311bc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/master308015a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip15a6a0248248eff25d376c44fd8da52e9e93156215a6a0248248eff25d376c44fd8da52e9e931562refs/remotes/origin/osmith/wip17371f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/master1f34184198d4ed07b30d8cdc96f6d0930843c5ed1f34184198d4ed07b30d8cdc96f6d0930843c5edrefs/remotes/origin/masterbc7c2b443e4f1ee792e43d9571d83ac552363ebabc7c2b443e4f1ee792e43d9571d83ac552363ebaorigin/masterhttps://gerrit.osmocom.org/osmo-cifalse#331182386542update-osmo-ci-on-slaves » simtester #33113311falsefalse331158355SUCCESS1773409747322https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves/label=simtester/3311/simtesteransible/roles/osmocom-obs-worker/tasks/obs.ymlansible/roles/osmocom-obs-worker/files/mount-securityfs.service47062c991a436b88d54244f668c69588a682bd731773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible: osmocom-obs-worker: add mount-securityfs.service Fix errors in lxc-start related to not having securityfs available: [ 14s] booting lxc... [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1132 If you really want to start this container, set [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1133 lxc.apparmor.allow_incomplete = 1 [ 14s] lxc-start: obsbuild:root_6: lsm/apparmor.c: apparmor_prepare: 1134 in your container configuration file [ 14s] lxc-start: obsbuild:root_6: start.c: lxc_init: 879 Failed to initialize LSM [ 14s] lxc-start: obsbuild:root_6: start.c: __lxc_start: 2008 Failed to initialize container "obsbuild:root_6" [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 306 The container failed to start [ 14s] lxc-start: obsbuild:root_6: tools/lxc_start.c: main: 312 Additional information can be obtained by setting the --logfile and --logpriority options [ 14s] '/var/cache/obs/worker/root_6/.build/_exitcode' not found or symlink Usually systemd would mount the securityfs automatically as I understand it, but it doesn't work anymore without this service in our use case where osmocom-obs-worker runs inside an LXC itself. This is probably related to upgrading the opensuse version for the osmocom-obs-worker containers. Change-Id: I0c708815440c67340531548361deb326c864aefe 2026-03-13 13:46:44 +000047062c991a436b88d54244f668c69588a682bd73ansible: osmocom-obs-worker: add mount-securityfs.serviceeditansible/roles/osmocom-obs-worker/tasks/obs.ymladdansible/roles/osmocom-obs-worker/files/mount-securityfs.serviceansible/util/known_hostsansible/hostsbc7c2b443e4f1ee792e43d9571d83ac552363eba1773409604000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deansible/hosts: update lx2-1-obs-aarch64-1 ip This machine is not available under the listed IPv6 anymore, but can be reached through the VPN. Adjust the IP. Change-Id: I77f72d7ad72d9b3ac745756cc5a082bd39dabdc5 2026-03-13 13:46:44 +0000bc7c2b443e4f1ee792e43d9571d83ac552363ebaansible/hosts: update lx2-1-obs-aarch64-1 ipeditansible/hostseditansible/util/known_hostsgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith