Skip to content

TEST-01-BASIC started suddenly failing in an unprivileged nspawn container on Arch Linux #13177

Description

@mrc0mmand

systemd version the issue has been seen with

latest master

Used distribution

Arch Linux

For some reason past ~8 runs consistently failed with:

Child 17 (systemd-sysctl) died (code=exited, status=1/FAILURE)
systemd-sysctl.service: Child 17 belongs to systemd-sysctl.service.
systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
systemd-sysctl.service: Failed with result 'exit-code'.
systemd-sysctl.service: Changed start -> failed
systemd-sysctl.service: Job 15 systemd-sysctl.service/start finished, result=failed
[FAILED] Failed to start Apply Kernel Variables.
See 'systemctl status systemd-sysctl.service' for details.
systemd-sysctl.service: Unit entered failed state.
systemd-sysctl.service: Consumed 6ms CPU time.

Full log: https://ci.centos.org/job/systemd-ci-build/745/artifact//artifacts_all/artifacts_Nuy3FU/vagrant-logs.aXu/vagrant-arch-testsuite.bow/TEST-01-BASIC_FAIL.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    priorityStuff that should enter master quickly, since it fixes a major bug, unbreaks CI or stalls other workregression ⚠️A bug in something that used to work correctly and broke through some recent committests

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions