This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2742
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
** Branch linked: lp:eucalyptus
** Branch linked: lp:eucalyptus/2.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a volume to a pending instance claims
** Changed in: eucalyptus
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a volume to a pending instance claims
Thanks Luca: assigning it to milestone 2.0.4.
** Changed in: eucalyptus
Milestone: None = 2.0.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a
Ah, my bad, since it's a patch to handlers_kvm.c, Xen code path is not
affected. I've confirmed that 'qemu' setting works with older Ubuntu
releases, too. So, we'll be happy to take this as is.
Luca - are you OK with signing off the ownership of the patch to us?
--
You received this bug
Sure.
Thanks for your help
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a volume to a pending instance claims success, but never
attaches.
To manage
Luca - thanks for the patch! Looks like your solution is the right one
for KVM. I'd like to ensure that volume attachments continue to work on
Xen (driver name 'phy' is Xen-specific, which used to be ignored by QEMU
until recently). So a bit of extra logic may be necessary to
differentiate XML
This seems to be due to a incompatibility between eucalyptus-nc and
libvirt
When attaching a disk (/dev/sdX or /dev/vdX), this is the output on the
node controller:
[Thu Nov 24 23:33:56 2011][000571][EUCAINFO ] doAttachVolume() invoked
(id=i-416607C2 vol=vol-5A24063B
Obviously, I meant qemu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a volume to a pending instance claims success, but never
attaches.
To manage
As I suspected, the incorrect disk driver for kvm was the issue.
I've attached a patch in the debian patch format, that lets me successfully
attach disks.
** Patch added: 31-handlers_kvm.patch
** Branch linked: lp:~invernizzi/eucalyptus/fix-676819
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676819
Title:
Attaching a volume to a pending instance claims success, but
The attachment 31-handlers_kvm.patch of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
** Changed in: eucalyptus
Assignee: (unassigned) = Dmitrii Zagorodnov (dmitrii)
--
Attaching a volume to a pending instance claims success, but never attaches.
https://bugs.launchpad.net/bugs/676819
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
Attaching a volume to a pending instance claims success (via
euca2ools, and the API) but never attaches to the instance. This may be
a KVM only issue.
As its pretty easy to reproduce, I haven't attached much in the way of
detail - let me know if you need any
14 matches
Mail list logo
