[Bug 1732883] [NEW] uvt-kvm wait command will never return on Trusty with a future guest using systemd such as Xenial

Launchpad Bug Tracker 1732883 at bugs.launchpad.net
Wed Jan 24 13:06:54 UTC 2018


You have been subscribed to a public bug by Po-Hsu Lin (cypressyew):

== SRU Justification ==

[Impact]
* When running a newer guest (which uses systemd) on Trusty, the `uvt-kvm wait` command will never return as the tool is not aware of the newer runlevel 5 for systemd.

[Test Case]
Steps:
 1. Install Trusty + X-hwe kernel
 2. sudo apt-get install uvtool -y
 3. ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
 4. sudo uvt-simplestreams-libvirt sync release=xenial arch=amd64
 5. sudo uvt-kvm create test-kvm release=xenial arch=amd64
 6. sudo uvt-kvm wait test-kvm --insecure

Result:
 * Step no 6. will never return. Even you can already ssh into that KVM

[Regression potential]
* This patch only adds compatibility for Trusty users, and limited to the uvt-kvm wait command on Trusty, therefore the risk for causing a regression is low.
* This patch has been tested on Trusty, with positive test result.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121~14.04.1
ProcVersionSignature: User Name 4.4.0-98.121~14.04.1-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Fri Nov 17 10:13:10 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: uvtool (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: uvtool (Ubuntu Trusty)
     Importance: Low
     Assignee: Po-Hsu Lin (cypressyew)
         Status: In Progress


** Tags: amd64 apport-bug trusty uec-images
-- 
uvt-kvm wait command will never return on Trusty with a future guest using systemd such as Xenial
https://bugs.launchpad.net/bugs/1732883
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list