Version 0.4.9 should work on ppc64le.
Upgrading the ubuntu package 0.4.9 to that OR including:
https://github.com/python-greenlet/greenlet/commit/9ad99fb5b9db916ca81bd3f5717c67e20384f7e0
; and
https://github.com/python-greenlet/greenlet/commit/4d0c450852a2b0cf6307cf6ca53dcdeea357cd48
should
Version 0.4.9 should work on ppc64le.
Upgrading the ubuntu package 0.4.9 to that OR including:
https://github.com/python-greenlet/greenlet/commit/9ad99fb5b9db916ca81bd3f5717c67e20384f7e0
; and
https://github.com/python-greenlet/greenlet/commit/4d0c450852a2b0cf6307cf6ca53dcdeea357cd48
should
@pboldin Thanks so much for doing that work.
I think we can now check the libvirt version and only raise the
exception if libvirt 1.2.17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398999
@pboldin Thanks so much for doing that work.
I think we can now check the libvirt version and only raise the
exception if libvirt 1.2.17
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
The Ubuntu package contains a patch from Uli that does the STACK_MAGIC
change (and more).
Rebuilding the python-greenlet package with -O1 passes the (greenlet)
test suite.
but nova (in my case nova-manage) still SEGVs
--
You received this bug notification because you are a member of Ubuntu
The Ubuntu package contains a patch from Uli that does the STACK_MAGIC
change (and more).
Rebuilding the python-greenlet package with -O1 passes the (greenlet)
test suite.
but nova (in my case nova-manage) still SEGVs
--
You received this bug notification because you are a member of Ubuntu
@james-page: Thanks! Forgive me for not understanding the process but
is it possible to get the fix in vivid as well?
I assume there will need to be some QA process around that. I'm happy
to verify any proposed builds.
--
You received this bug notification because you are a member of Ubuntu
@james-page: Thanks! Forgive me for not understanding the process but
is it possible to get the fix in vivid as well?
I assume there will need to be some QA process around that. I'm happy
to verify any proposed builds.
--
You received this bug notification because you are a member of Ubuntu
Trying to restate the problem a little morew clearly as after we've looked into
this the 'Bug Description' is really more of a symptom.
The current systemd sverice definition for rabbitmq-server completes
before the rabbit process is actually available. This means that
scripted
Trying to restate the problem a little morew clearly as after we've looked into
this the 'Bug Description' is really more of a symptom.
The current systemd sverice definition for rabbitmq-server completes
before the rabbit process is actually available. This means that
scripted
Update package to
1) include rabbitmq-server-wait: A helper script that uses the same environment
file as rabbitmq-server and waits until the server is up.
2) Call the new file from the systemd service.
This ensures that the server is available when systemctl start rabbitmq-
server exits.
**
Update package to
1) include rabbitmq-server-wait: A helper script that uses the same environment
file as rabbitmq-server and waits until the server is up.
2) Call the new file from the systemd service.
This ensures that the server is available when systemctl start rabbitmq-
server exits.
**
Looks like Fedora hit similar (but not identical) issues.
https://bugzilla.redhat.com/show_bug.cgi?id=1103524
The answer there was to patch systemd_notify support into rabbit.
** Bug watch added: Red Hat Bugzilla #1103524
https://bugzilla.redhat.com/show_bug.cgi?id=1103524
** Also affects:
Looks like Fedora hit similar (but not identical) issues.
https://bugzilla.redhat.com/show_bug.cgi?id=1103524
The answer there was to patch systemd_notify support into rabbit.
** Bug watch added: Red Hat Bugzilla #1103524
https://bugzilla.redhat.com/show_bug.cgi?id=1103524
** Also affects:
@vanderwl No problem I'm new to cloud archive as well.
So the URL I have is:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/kilo-staging/+index
and that shows (for me) that 4 hours ago the (kilo-staging) cloud-archive PPA
got the fixed libvirt.
So in theory We're done here. Matt
@vanderwl No problem I'm new to cloud archive as well.
So the URL I have is:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/kilo-staging/+index
and that shows (for me) that 4 hours ago the (kilo-staging) cloud-archive PPA
got the fixed libvirt.
So in theory We're done here. Matt
@vanderwl: The original report was against the trusty cloud-archive
repo.
If you look at: https://launchpad.net/ubuntu/+source/libvirt You can
see that the version in trusty is NOT affected by this issue.
Only vivid and the could archive PPA
--
You received this bug notification because you
@vanderwl: The original report was against the trusty cloud-archive
repo.
If you look at: https://launchpad.net/ubuntu/+source/libvirt You can
see that the version in trusty is NOT affected by this issue.
Only vivid and the could archive PPA
--
You received this bug notification because you
@j-rosenboom-j My fix for nova will never be accepted upstream. I
wont speak for the Ubuntu developers but I strongly suspect that they'll
be unwilling to diverge from upstream. Especially as they've already
shown the fix will land in vivid.
--
You received this bug notification because you
@j-rosenboom-j My fix for nova will never be accepted upstream. I
wont speak for the Ubuntu developers but I strongly suspect that they'll
be unwilling to diverge from upstream. Especially as they've already
shown the fix will land in vivid.
--
You received this bug notification because you
I can verify that installing 1.2.12-0ubuntu13 on vivid fixes the issue
for me.
Please forgive my ignorance but can that package be tagged into cloud-
archive once it's officially a vivid update?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
I can verify that installing 1.2.12-0ubuntu13 on vivid fixes the issue
for me.
Please forgive my ignorance but can that package be tagged into cloud-
archive once it's officially a vivid update?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
For the record. Applying this patch to the cloud-archive libvirt
package should fix the problem.
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a103bb105c0c189c3973311ff1826972b5bc6ad6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For the record. Applying this patch to the cloud-archive libvirt
package should fix the problem.
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a103bb105c0c189c3973311ff1826972b5bc6ad6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I was pointed at the v1.2.12-maint head in the libvirt git which contains this
fix already.
http://libvirt.org/git/?p=libvirt.git;a=shortlog;h=refs/heads/v1.2.12-maint
I suggest we close the nova issue with won't fix and get the correctly
backported patch into the libvirt package.
--
You
I was pointed at the v1.2.12-maint head in the libvirt git which contains this
fix already.
http://libvirt.org/git/?p=libvirt.git;a=shortlog;h=refs/heads/v1.2.12-maint
I suggest we close the nova issue with won't fix and get the correctly
backported patch into the libvirt package.
--
You
We're in discussions with the libvirt devs to work out if the fix is
correct and/or exposes a libvirt bug.
Once that discussion concludes there will the a nova patch posted (and
tagged for backport)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We're in discussions with the libvirt devs to work out if the fix is
correct and/or exposes a libvirt bug.
Once that discussion concludes there will the a nova patch posted (and
tagged for backport)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Summary of the libvirt discussion. current upstream works. the libvirt
team would like to identify the libvirt fixes required and get them
backported. to the maintenance releases.
With reference to:
https://launchpad.net/ubuntu/+source/libvirt ; and
Summary of the libvirt discussion. current upstream works. the libvirt
team would like to identify the libvirt fixes required and get them
backported. to the maintenance releases.
With reference to:
https://launchpad.net/ubuntu/+source/libvirt ; and
This patch (which hasn't gone anywhere near upstream yet)
Forces the libvirt driver in nova to avoid generating a cpuset and there
fore no longer generates the invalid domain XML.
Next steps are to discuss my findings with upstream libvirt and nova
developers to see if I'm correct of I've just
It seems that nova's libvirt driver is generating an invalid domain xml.
If I understand correctly specifyin a 'vcpu' node with a cpuset is
invlaid in TCG *unless* you also specify emulatorpin See:
https://libvirt.org/formatdomain.html#elementsCPUAllocation
--
You received this bug notification
It seems that nova's libvirt driver is generating an invalid domain xml.
If I understand correctly specifyin a 'vcpu' node with a cpuset is
invlaid in TCG *unless* you also specify emulatorpin See:
https://libvirt.org/formatdomain.html#elementsCPUAllocation
--
You received this bug notification
This patch (which hasn't gone anywhere near upstream yet)
Forces the libvirt driver in nova to avoid generating a cpuset and there
fore no longer generates the invalid domain XML.
Next steps are to discuss my findings with upstream libvirt and nova
developers to see if I'm correct of I've just
But that makes no sense. If you were changing
# While earlier versions could support NUMA reporting and
# NUMA placement, not until 1.2.7 was there the ability
# to pin guest nodes to host nodes, so mandate that. Without
# this the scheduler cannot make guaranteed decisions, as the
# guest
But that makes no sense. If you were changing
# While earlier versions could support NUMA reporting and
# NUMA placement, not until 1.2.7 was there the ability
# to pin guest nodes to host nodes, so mandate that. Without
# this the scheduler cannot make guaranteed decisions, as the
# guest
** Changed in: nova
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage notifications about
** Changed in: nova
Milestone: None = kilo-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage
** Changed in: cinder
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output
** Changed in: cinder
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
Patchg 0500-block-raw-posix-Try-both-FIEMAP-and-SEEK_HOLE.patch appears
to be part of a bigger re-write of the related code. and is ON TOP of
the patches already applied in this bug.
No doubt the rewirtten code is better but backporting it contains more risk
than the 2 simple fixes I already
Patchg 0500-block-raw-posix-Try-both-FIEMAP-and-SEEK_HOLE.patch appears
to be part of a bigger re-write of the related code. and is ON TOP of
the patches already applied in this bug.
No doubt the rewirtten code is better but backporting it contains more risk
than the 2 simple fixes I already
I'd elevate this to high so it matches nova and ubuntu but I don't have
permissions to do so.
** Changed in: cinder
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
I'm happy to tackle to also fix cinder with a version of the nova fix
(for consistency). I propose waiting until the nova fix lands
** Changed in: cinder
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server Team
I'm happy to tackle to also fix cinder with a version of the nova fix
(for consistency). I propose waiting until the nova fix lands
** Changed in: cinder
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'd elevate this to high so it matches nova and ubuntu but I don't have
permissions to do so.
** Changed in: cinder
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Chris,
Markus' rework will not reintroduce this bug as it completely removes all
fiemap code.
bug 129224 is a different issue, I'll comment on that bug.
You say: you encounter issues with upstream with ^extent and ext3
filesystems. Just to be clear: Are you saying that *this* bug is still
a
Chris,
I've read through 1292234 and I'll have a play with your reproducer locally and
see if I can gain any insight.
I'm sorry my fix didn't help 1292234, but glad you can't hit 1368815
with upstream, I was kinda having kittens here ;P
--
You received this bug notification because you are a
Hi Chris,
Markus' rework will not reintroduce this bug as it completely removes all
fiemap code.
bug 129224 is a different issue, I'll comment on that bug.
You say: you encounter issues with upstream with ^extent and ext3
filesystems. Just to be clear: Are you saying that *this* bug is still
a
Chris,
I've read through 1292234 and I'll have a play with your reproducer locally and
see if I can gain any insight.
I'm sorry my fix didn't help 1292234, but glad you can't hit 1368815
with upstream, I was kinda having kittens here ;P
--
You received this bug notification because you are a
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage
** Changed in: nova
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage
** Changed in: nova
Assignee: (unassigned) = Tony Breeds (o-tony)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832507
Title:
console.log grows indefinitely
To manage notifications about
Hi Serge,
Is there any chance these fixes will go into trusty?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
Awesome.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage notifications about this bug go to:
Hi Serge,
Is there any chance these fixes will go into trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage
Awesome.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage notifications about this bug go to:
FWIW the following 2 commits in qemu master resolve the issue for qemu-
img.
http://git.qemu.org/?p=qemu.git;a=commit;h=38c4d0aea3e1264c86e282d99560330adf2b6e25
http://git.qemu.org/?p=qemu.git;a=commit;h=7c15903789953ead14a417882657d52dc0c19a24
If possible they should be back ported to
FWIW the following 2 commits in qemu master resolve the issue for qemu-
img.
http://git.qemu.org/?p=qemu.git;a=commit;h=38c4d0aea3e1264c86e282d99560330adf2b6e25
http://git.qemu.org/?p=qemu.git;a=commit;h=7c15903789953ead14a417882657d52dc0c19a24
If possible they should be back ported to
openstack review at:
https://review.openstack.org/#/c/123957/
Qemu patches at:
http://patchwork.ozlabs.org/patch/393494/ ; and
http://patchwork.ozlabs.org/patch/393495/
** Changed in: nova
Assignee: (unassigned) = Tony Breeds (o-tony)
** Changed in: qemu
Status: New
openstack review at:
https://review.openstack.org/#/c/123957/
Qemu patches at:
http://patchwork.ozlabs.org/patch/393494/ ; and
http://patchwork.ozlabs.org/patch/393495/
** Changed in: nova
Assignee: (unassigned) = Tony Breeds (o-tony)
** Changed in: qemu
Status: New
62 matches
Mail list logo
