Source: vagrant-libvirt Version: 0.12.2-1 Severity: important User: debian...@lists.debian.org Usertags: isolation-machine
Dear maintainer(s),Your package has an autopkgtest, great. I recently added support for isolation-machine tests on ci.debian.net for amd64 and added your package to the list to use that. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing, but because machine-isolation support by ci.debian.net is new I have not marked this bug as serious (yet).
More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html https://ci.debian.net/packages/v/vagrant-libvirt/testing/amd64/44891491/ 64s autopkgtest [06:08:05]: test basics: [----------------------- 64s + export VAGRANT_DEFAULT_PROVIDER=libvirt 64s + debian-distro-info --stable 64s + release=bookworm 64s + box=debian/bookworm64 64s + [ -z /tmp/autopkgtest.TYXTpk/autopkgtest_tmp ] 64s + vagrant plugin list 65s vagrant-libvirt (0.12.2, system) 65s + vagrant global-status 65s id name provider state directory 65s -------------------------------------------------------------------- 65s There are no active Vagrant environments on this computer! Or, 65s you haven't destroyed and recreated Vagrant environments that were 65s started with an older version of Vagrant. 65s + vagrant box list 65s + grep debian/bookworm64.*libvirt 66s + vagrant box add --force --provider=libvirt debian/bookworm64 67s ==> box: Loading metadata for box 'debian/bookworm64' 67s box: URL: https://vagrantcloud.com/debian/bookworm6467s ==> box: Adding box 'debian/bookworm64' (v12.20240212.1) for provider: libvirt 67s box: Downloading: https://vagrantcloud.com/debian/boxes/bookworm64/versions/12.20240212.1/providers/libvirt/unknown/vagrant.box
77s [KProgress: 0% (Rate: 0*/s, Estimated time remaining: --:--:--) [KProgress: 9% (Rate: 24.9M/s, Estimated time remaining: 0:00:11) [KProgress: 25% (Rate: 51.6M/s, Estimated time remaining: 0:00:06) [KProgress: 44% (Rate: 55.9M/s, Estimated time remaining: 0:00:04) [KProgress: 66% (Rate: 61.6M/s, Estimated time remaining: 0:00:02) [KProgress: 95% (Rate: 69.8M/s, Estimated time remaining: --:--:--)[K==> box: Successfully added box 'debian/bookworm64' (v12.20240212.1) for 'libvirt'!
77s + cd /tmp/autopkgtest.TYXTpk/autopkgtest_tmp 77s + mkdir testvm 77s + cd testvm 77s + trap cleanup INT TERM EXIT 77s + vagrant init debian/bookworm64 78s A `Vagrantfile` has been placed in this directory. You are now 78s ready to `vagrant up` your first virtual environment! Please read 78s the comments in the Vagrantfile as well as documentation on 78s `vagrantup.com` for more information on using Vagrant. 78s + vagrant up --no-provision 78s Bringing machine 'default' up with 'libvirt' provider... 79s It appears your machine doesn't support NFS, or there is not an 79s adapter to enable NFS on this machine for Vagrant. Please verify 79s that `nfsd` is installed on your machine, and try again. If you're 79s on Windows, NFS isn't supported. If the problem persists, please 79s contact Vagrant support. 79s + cleanup 79s + vagrant halt 80s It appears your machine doesn't support NFS, or there is not an 80s adapter to enable NFS on this machine for Vagrant. Please verify 80s that `nfsd` is installed on your machine, and try again. If you're 80s on Windows, NFS isn't supported. If the problem persists, please 80s contact Vagrant support. 81s autopkgtest [06:08:22]: test basics: -----------------------]
OpenPGP_signature.asc
Description: OpenPGP digital signature
