systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

Bug #1707267 reported by Seth Forshee on 2017-07-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
High
Dimitri John Ledkov
Seth Forshee (sforshee) wrote :

autopkgtest [11:09:53]: test boot-smoke: [-----------------------
...
checking that there are no running jobs
running jobs after remaining timeout -1:
 61 apt-daily-upgrade.timer start waiting
209 systemd-hostnamed.service start running
 64 NetworkManager-wait-online.service start running
 59 timers.target start waiting
 63 network-online.target start waiting
 62 apt-daily.timer start waiting
autopkgtest [11:10:53]: test boot-smoke: -----------------------]
autopkgtest [11:10:53]: test boot-smoke: - - - - - - - - - - results - - - - - - - - - -
boot-smoke FAIL non-zero exit status 1

tags: added: kernel-adt-failure
Dimitri John Ledkov (xnox) wrote :

This has been noted. Also we have similar reports that ubuntu starts degraded in containers by default on all arches in artful at the moment.

This is seen on s390x, because unlike other arches, the ADT tests use container confinement instead of kvm confinement.

Actions to take:
1) make all kvm arches execute the tests twice, with VM and nested container confinement
2) fix degraded boots in containers

This particular regression, at the moment, is not considered to be architecture specific.

Changed in systemd (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Dimitri John Ledkov (xnox)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers