Hi Akshay, This has been released for Ocata.
** Changed in: cloud-archive/ocata
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kvm do
Hi Corey, when will this fix be released for ocata?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kvm doesnt restart after node reboot
To manage notifications about this bug go
** Tags removed: verification-ocata-needed verification-pike-needed
** Tags added: verification-ocata-done verification-pike-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kv
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.6
---
qemu (1:2.8+dfsg-3ubuntu2.6) zesty; urgency=medium
* fix enablement of qemu-kvm service (LP: #1720397)
- rename d/qemu-kvm.service to d/qemu-system-common.qemu-kvm.service
- d/rules: add proper enablement deb
Regression testing with OpenStack tempest for Ocata has completed
successfully.
xenial-ocata proposed stable charms:
==
Totals
==
Ran: 102 tests in 1742.1837 sec.
- Passed: 93
- Skipped: 9
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3~cloud0
---
qemu (1:2.10+dfsg-0ubuntu3~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.10+dfsg-0ubuntu3) artful; urgency=medium
.
* fix enablement of qemu-kvm service (L
OpenStack regression tests have passed successfully for xenial-pike-
proposed with this package.
pike-proposed with next charms:
==
Totals
==
Ran: 102 tests in 1904.7099 sec.
- Passed: 93
- Skipped: 9
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each
Hello Ernie, or anyone else affected,
Accepted qemu into pike-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-rep
Verified on Zesty, here the console log as reference:
# apt update
Hit:1 http://archive.ubuntu.com/ubuntu zesty InRelease
Get:2 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB]
Get:3 http://archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB]
Get:4 http://ar
Hello Ernie, or anyone else affected,
Accepted qemu into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.8+dfsg-
3ubuntu2.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Per tests in c#17 and some regression checks being good, so uploading.
Ok, I see it in zesty-unapproved - ready for SRU review now.
** Changed in: qemu (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Artful)
Assignee: ChristianEhrhardt (paelzer) => (unassig
Prep done, tested from ppa working as intended on Zesty as well.
# systemctl status qemu-kvm
● qemu-kvm.service - QEMU KVM preparation - module, ksm, hugepages
Loaded: loaded (/lib/systemd/system/qemu-kvm.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
root@zesty-test:~#
For the Zesty fix I need to integrate two rounds of security updates
first, but I'm working on the SRU prep now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kvm doesnt restart
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3
---
qemu (1:2.10+dfsg-0ubuntu3) artful; urgency=medium
* fix enablement of qemu-kvm service (LP: #1720397)
- rename d/qemu-kvm.service to d/qemu-system-common.qemu-kvm.service
- d/rules: add proper enablement debh
Hi Michael,
yeah manually enabling it is a workaround, but to let the maintainer scrtipts
do it right on install is still the preferred way to do it.
But all looks good on the way to get it into artful, regression tests, dep8
tests, ...
Might just be blocked a bit by the release week freeze, but
To add to my comment above, if service nova-compute restart doesn't
work, a node reboot does. The issue is that upon initial install there
is no qemu-kvm.service enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I solved this problem by:
juju ssh nova-compute/0(one of my bad nodes)
sudo systemctl enable qemu-kvm.service
sudo service qemu-kvm restart
sudo service nova-compute restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
In the meantime also regression checks on the ppa completed.
Given the nature of the change nothing was expected, but better to confirm and
it was ok not showing new issues.
That said uploading to Artful-proposed for evaluation of the release
team if we want to push as-is, 0-day update or whateve
I was testing the fix from a ppa:
With debug enabled this looks much better now.
Install:
Setting up qemu-system-common (1:2.10+dfsg-0ubuntu3~ppa2) ...
(deb-systemd-helper DEBUG) is purge = no
(deb-systemd-helper DEBUG) action = unmask, scriptname = qemu-kvm.service,
service_path = /lib/systemd
This issue qualified for the following of the Final Freeze mail:
I'll be adding a SRU Template to make things clear.
2) Bug fixes that would be suitable for post-release SRUs, which we
may choose to accept, reject, or shunt to -updates for 0-day SRUs
on a case-by-base basis.
** Description
** Also affects: qemu (Ubuntu Artful)
Importance: Medium
Status: Triaged
** Also affects: qemu (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Artful)
Assignee: (unassigned) =
On upgrades before Artful/Pike this file was not properly cleaned.
So maybe then they kept the old config with the sysV wrapper in those upgrade
cases until cleaned up?
Anyway - I checked releases X to A and found that:
X - only sysv - ok
Y - only sysv - ok
Z - systemd service, disabled - bug
A -
Added a Cloud Archive Task since that is affected as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kvm doesnt restart after node reboot
To manage notifications about this
Hmm, indeed.
This might have been broken by the transition to a systemd service:
In newer versions that is:
$ service qemu-kvm status
● qemu-kvm.service - QEMU KVM preparation - module, ksm, hugepages
Loaded: loaded (/lib/systemd/system/qemu-kvm.service; disabled; vendor
preset: enabled)
Ac
ubuntu@trusty-cicada:~$ service qemu-kvm status
● qemu-kvm.service - QEMU KVM preparation - module, ksm, hugepages
Loaded: loaded (/lib/systemd/system/qemu-kvm.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
--
You received this bug notification because you are a member
Should have said, Empty directories under /var/log/libvirt/*
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Title:
qemu-kvm does
Nothing under /var/log/libvirt/*
Attached syslog.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1720397/+attachment/4960668/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I am going to mark this as incomplete, but once you upload additional
logs please feel free to move this to new, and the next server team
member will see the update and review.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
** Changed in: qemu (Ubuntu)
Importance: Undecided => M
Thank you for taking the time to file a bug report.
Can you provide the logs under /var/log/libvirt/*, as well as any
relevant logs to help triage this issue further?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
29 matches
Mail list logo