uvt-kvm wait for vivid or xenial VMs doesn't work on a trusty host

Bug #1614488 reported by Will Bryant
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
uvtool (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

uvt-kvm wait works correctly on a xenial host. But on a trusty host, it never returns when creating vivid or xenial VMs:

will@host:~$ date
Thu Aug 18 22:44:27 NZST 2016
will@host:~$ sudo uvt-kvm create --cpu 8 --memory 2048 --disk 8 --ssh-public-key-file ~will/.ssh/authorized_keys waitdemo arch=amd64 release=trusty
will@host:~$ uvt-kvm wait --insecure waitdemo
Warning: Permanently added '192.168.122.215' (ECDSA) to the list of known hosts.
will@host:~$ sudo uvt-kvm destroy waitdemo
will@host:~$
will@host:~$ date
Thu Aug 18 22:44:40 NZST 2016
will@host:~$ sudo uvt-kvm create --cpu 8 --memory 2048 --disk 8 --ssh-public-key-file ~will/.ssh/authorized_keys waitdemo arch=amd64 release=utopic
will@host:~$ uvt-kvm wait --insecure waitdemo
Warning: Permanently added '192.168.122.185' (ECDSA) to the list of known hosts.
will@host:~$ sudo uvt-kvm destroy waitdemo
will@host:~$
will@host:~$ date
Thu Aug 18 22:44:54 NZST 2016
will@host:~$ sudo uvt-kvm create --cpu 8 --memory 2048 --disk 8 --ssh-public-key-file ~will/.ssh/authorized_keys waitdemo arch=amd64 release=vivid
will@host:~$ uvt-kvm wait --insecure waitdemo
Warning: Permanently added '192.168.122.3' (ECDSA) to the list of known hosts.

... no output ...

^CTraceback (most recent call last):
  File "/usr/bin/uvt-kvm", line 35, in <module>
    uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 709, in main_cli_wrapper
    main(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 704, in main
    args.func(parser, args)
  File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 637, in main_wait
    main_wait_remote(parser, args)
  File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 605, in main_wait_remote
    private_key_file=args.ssh_private_key_file,
  File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 489, in ssh
    ssh_call, preexec_fn=subprocess_setup, close_fds=True, stdin=stdin
  File "/usr/lib/python2.7/subprocess.py", line 535, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 522, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/subprocess.py", line 1376, in wait
    pid, sts = _eintr_retry_call(os.waitpid, self.pid, 0)
  File "/usr/lib/python2.7/subprocess.py", line 476, in _eintr_retry_call
    return func(*args)
KeyboardInterrupt

Revision history for this message
Will Bryant (willbryant) wrote :

Note that even though uvt-kvm wait does not return, uvt-ssh does work:

will@host:~$ uvt-kvm ssh --insecure waitdemo
Warning: Permanently added '192.168.122.3' (ECDSA) to the list of known hosts.
Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-49-generic x86_64)

description: updated
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Went over old subscribed bugs and found that this clearly should be targetted against uvtool.

affects: vm-builder (Ubuntu) → uvtool (Ubuntu)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Also I must say I use that rather regularly from ppa:uvtool-dev/master working fine.
I don't know about the support in general, but rbasak might know easily.

Revision history for this message
Robie Basak (racb) wrote :

What version of the uvtool package was being used on Trusty? 0~bzr92-0ubuntu1 or 0~bzr92-0ubuntu1.1? If so, it's because Vivid moved to systemd, and the uvtool on Trusty, being in the past, couldn't be expected to know about it. This was fixed in commit 82136d9 which could be backported to older releases I suppose. But it is fixed in the development release, so is an SRU bug for Trusty only if anything.

If someone affected wants to drive an SRU for Trusty, feel free.

Changed in uvtool (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.