[Bug 1845037] Re: autopkgtest package "lxd" test has started failing

Dan Streetman dan.streetman at canonical.com
Wed Sep 25 00:52:38 UTC 2019


** Description changed:

  [impact]
  
  the failure is seen in (at least) the "lxd" autopkgtest from the autopkgtest package itself, e.g.:
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/a/autopkgtest/20190923_160817_66dbe@/log.gz
  
  [test case]
  
  run the autopkgtests for the package 'autopkgtest', or check autopkgtest.ubuntu.com, e.g.:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/i386
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/i386
  
  note that this is failing only for disco and eoan, and note that the 'lxd' test is skipped for non-intel archs.  this does not appear to be failing on bionic:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/bionic/amd64
  
  [regression potential]
  
- TBD
+ this only redirects stdin from /dev/null, for the call to 'lxc launch'
+ inside autopkgtest-build-lxd; so the regression potential should be low.
+ Any regressions would almost certainly involve a failure during the call
+ to autopkgtest-build-lxd, during the creation of the lxd container.
  
  [other info]
  
  this is reproducable with the current packages from disco-updates using
- a local qemu vm for testing; it seems that some change in the lxd snap
- recently has caused this regression.
+ a local qemu vm for testing.
+ 
+ I put the 'importance' of this as low because this bug will only be
+ reproduced when calling autopkgtest-build-lxd from inside a here
+ document passed to a shell, or otherwise called with input queued on
+ stdin, which seems like an unusual way to call autopkgest-build-lxd.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1845037

Title:
  autopkgtest package "lxd" test has started failing

Status in autopkgtest package in Ubuntu:
  In Progress
Status in autopkgtest source package in Xenial:
  In Progress
Status in autopkgtest source package in Bionic:
  In Progress
Status in autopkgtest source package in Disco:
  In Progress
Status in autopkgtest source package in Eoan:
  In Progress

Bug description:
  [impact]

  the failure is seen in (at least) the "lxd" autopkgtest from the autopkgtest package itself, e.g.:
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/a/autopkgtest/20190923_160817_66dbe@/log.gz

  [test case]

  run the autopkgtests for the package 'autopkgtest', or check autopkgtest.ubuntu.com, e.g.:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/i386
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/i386

  note that this is failing only for disco and eoan, and note that the 'lxd' test is skipped for non-intel archs.  this does not appear to be failing on bionic:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/bionic/amd64

  [regression potential]

  this only redirects stdin from /dev/null, for the call to 'lxc launch'
  inside autopkgtest-build-lxd; so the regression potential should be
  low.  Any regressions would almost certainly involve a failure during
  the call to autopkgtest-build-lxd, during the creation of the lxd
  container.

  [other info]

  this is reproducable with the current packages from disco-updates
  using a local qemu vm for testing.

  I put the 'importance' of this as low because this bug will only be
  reproduced when calling autopkgtest-build-lxd from inside a here
  document passed to a shell, or otherwise called with input queued on
  stdin, which seems like an unusual way to call autopkgest-build-lxd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1845037/+subscriptions



More information about the foundations-bugs mailing list