Hi Connor,
thanks for checking this issue.
we have changed the test to boot $RELEASE on $RELEASE (used to be Xenial
on all the other releases, and therefore X on T is affected by this bug)
Base on this we can say it's no longer an issue for the test itself.
It's still a issue for the tool, but I
Hey Sam,
Trusty's HWE kvm smoke tests appear to have passed on amd64 but looks
like it's hiccuping on a couple of other arches. I don't know how useful
that information is here for this bug though. Given that Trusty is ESM,
is this SRU-able still?
--
You received this bug notification because
** Tags added: ubuntu-kvm-smoke-test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will never return on Trusty with a future guest
using systemd such as Xenial
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will never return on Trusty with a future
Stalled, I will check on the current status for the KVM smoke test, the
behaviour seem a bit different now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will
Hey Sam, we still working this?
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will never
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The best way to work on this would be to use the following commmands:
apt-get source uvtool=0~bzr92-0ubuntu1.1
cd uvtool-0\~bzr92
dch -i
This will correctly increment the changelog to 0~bzr92-0ubuntu1.2 and
you can add your changelog entry there. It looks like you may have
reversed your debdiff
Hi Robie,
The 0~bzr92-0ubuntu1.1 is the latest version that I can get from Trusty
repository (another one is 0~bzr92-0ubuntu1). So it's a bit confusing
here, I got the package with apt-get source command, should I use
something else for this specific fix in Trusty?
(And another question just out
The debdiff is reversed (which a sponsor could work around) but is also
based on 0~bzr92-0ubuntu1.1 which is already published.
I think you'd be better served getting help from other Ubuntu developers
from a public channel, such as #ubuntu-devel. Then you won't get blocked
on me in preparing an
** Attachment removed: "fix-wait-debdiff"
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1732883/+attachment/5042252/+files/fix-wait-debdiff
** Attachment added: "fix-wait-debdiff"
** Attachment added: "fix-wait-debdiff"
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1732883/+attachment/5042252/+files/fix-wait-debdiff
** Patch removed: "fix-remote-wait-trusty"
** Description changed:
== 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
** Description changed:
== 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.
+ * When running a newer guest (which uses systemd) on Trusty,
Patch created with quilt command.
** Attachment added: "fix-remote-wait-trusty"
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1732883/+attachment/5019116/+files/fix-remote-wait-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
== SRU Justification ==
- [Impact]
+ [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 +
** Description changed:
+ == 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
** Changed in: uvtool (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will never return on Trusty with a
Hi Robie,
thanks for the hint, I will try to fix this in Trusty!
** Changed in: uvtool (Ubuntu Trusty)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
