seccomp tests fail in tumbleweed on 2020-03-05 and 20.04

Bug #1866183 reported by Zygmunt Krynicki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Fix Released
Critical
Michael Vogt
snapd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

A recent build of snapd in openSUSE tumbleweed uncovered test suite failures.
Those may be related to a kernel or seccomp update and need investigation.

[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:799: snapSeccompSuite.TestCompatArchWorks
[ 354s]
[ 354s] main_test.go:832:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "read" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:367: snapSeccompSuite.TestCompile
[ 354s]
[ 354s] main_test.go:476:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "read" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:485: snapSeccompSuite.TestCompileSocket
[ 354s]
[ 354s] main_test.go:504:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "socket AF_UNIX" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:684: snapSeccompSuite.TestRestrictionsWorkingArgsClone
[ 354s]
[ 354s] main_test.go:705:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "setns - CLONE_NEWIPC" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:710: snapSeccompSuite.TestRestrictionsWorkingArgsMknod
[ 354s]
[ 354s] main_test.go:729:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "mknod - S_IFREG" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:656: snapSeccompSuite.TestRestrictionsWorkingArgsPrctl
[ 354s]
[ 354s] main_test.go:661:
[ 354s] s.runBpf(c, seccompWhitelist, bpfInputGood, Allow)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "prctl PR_CAP_AMBIENT" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:734: snapSeccompSuite.TestRestrictionsWorkingArgsPrio
[ 354s]
[ 354s] main_test.go:749:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "setpriority PRIO_PROCESS" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:642: snapSeccompSuite.TestRestrictionsWorkingArgsQuotactl
[ 354s]
[ 354s] main_test.go:647:
[ 354s] s.runBpf(c, seccompWhitelist, bpfInputGood, Allow)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "quotactl Q_QUOTAON" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:607: snapSeccompSuite.TestRestrictionsWorkingArgsSocket
[ 354s]
[ 354s] main_test.go:617:
[ 354s] s.runBpf(c, seccompWhitelist, bpfInputGood, Allow)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "socket AF_UNIX" (failed to run "exit status 127")
[ 354s]
[ 354s]
[ 354s] ----------------------------------------------------------------------
[ 354s] FAIL: main_test.go:754: snapSeccompSuite.TestRestrictionsWorkingArgsTermios
[ 354s]
[ 354s] main_test.go:765:
[ 354s] s.runBpf(c, t.seccompWhitelist, t.bpfInput, t.expected)
[ 354s] main_test.go:334:
[ 354s] c.Fatalf("unexpected error for %q (failed to run %q)", seccompWhitelist, err)
[ 354s] ... Error: unexpected error for "ioctl - TIOCSTI" (failed to run "exit status 127")

Revision history for this message
Samuele Pedroni (pedronis) wrote :

this is now happening on 20.04 as well

Changed in snapd:
importance: Undecided → Critical
assignee: nobody → Michael Vogt (mvo)
Changed in snapd:
status: New → Confirmed
summary: - seccomp tests fail in tumbleweed on 2020-03-05
+ seccomp tests fail in tumbleweed on 2020-03-05 and 20.04
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This was fixed by https://github.com/snapcore/snapd/pull/8266 but we didn't uncover the root cause.

Changed in snapd:
status: Confirmed → Fix Committed
milestone: none → 2.44
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Snapd 2.44 has been released, marking as the bug as such.

Changed in snapd:
status: Fix Committed → Fix Released
Changed in snapd (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.