[Bug 452185] Re: can't access SC volumes in a UEC instance
Kendall Price
kpauburn at gmail.com
Fri Oct 23 14:50:23 BST 2009
Here's my whole process, using the latest Karmic RC and the RC UEC
images:
This is how I packaged the RC images :
nimbusadmin at nimbus:~$ euca-bundle-image -i karmic-uec-amd64-vmlinuz-virtual --k
ernel true
Checking image
Tarring image
Encrypting image
Splitting image...
Part: karmic-uec-amd64-vmlinuz-virtual.part.0
Generating manifest
nimbusadmin at nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6
4-vmlinuz-virtual.manifest.xml
Checking bucket: uecrckernel
Creating bucket: uecrckernel
Uploading manifest file
Uploading part: karmic-uec-amd64-vmlinuz-virtual.part.0
Uploaded image as uecrckernel/karmic-uec-amd64-vmlinuz-virtual.manifest.xml
nimbusadmin at nimbus:~$ euca-register uecrckernel/karmic-uec-amd64-vmlinuz-virtua
l.manifest.xml
IMAGE eki-A8AB1882
nimbusadmin at nimbus:~$ euca-bundle-image -i karmic-uec-amd64-initrd-virtual --ra
mdisk true
Checking image
Tarring image
Encrypting image
Splitting image...
Part: karmic-uec-amd64-initrd-virtual.part.0
Generating manifest
nimbusadmin at nimbus:~$ euca-upload-bundle -b uecrcramdisk -m /tmp/karmic-uec-amd
64-initrd-virtual.manifest.xml
Checking bucket: uecrcramdisk
Creating bucket: uecrcramdisk
Uploading manifest file
Uploading part: karmic-uec-amd64-initrd-virtual.part.0
Uploaded image as uecrcramdisk/karmic-uec-amd64-initrd-virtual.manifest.xml
nimbusadmin at nimbus:~$ euca-register uecrcramdisk/karmic-uec-amd64-initrd-virtua
l.manifest.xml
IMAGE eri-A52B1860
nimbusadmin at nimbus:~$ euca-bundle-image -i karmic-uec-amd64.img --kernel eki-A8
AB1882 --ramdisk eri-A52B1860
Checking image
Tarring image
Encrypting image
Splitting image...
Part: karmic-uec-amd64.img.part.0
Part: karmic-uec-amd64.img.part.1
Part: karmic-uec-amd64.img.part.2
Part: karmic-uec-amd64.img.part.3
Part: karmic-uec-amd64.img.part.4
Part: karmic-uec-amd64.img.part.5
Part: karmic-uec-amd64.img.part.6
Part: karmic-uec-amd64.img.part.7
Part: karmic-uec-amd64.img.part.8
Part: karmic-uec-amd64.img.part.9
Part: karmic-uec-amd64.img.part.10
Part: karmic-uec-amd64.img.part.11
Part: karmic-uec-amd64.img.part.12
Part: karmic-uec-amd64.img.part.13
Part: karmic-uec-amd64.img.part.14
Part: karmic-uec-amd64.img.part.15
Part: karmic-uec-amd64.img.part.16
Part: karmic-uec-amd64.img.part.17
Generating manifest
nimbusadmin at nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/image.manifest.
xml
Invalid manifest
nimbusadmin at nimbus:~$ euca-upload-bundle -b uecrckernel -m /tmp/karmic-uec-amd6
4.img.manifest.xml
Checking bucket: uecrckernel
Uploading manifest file
Uploading part: karmic-uec-amd64.img.part.0
Uploading part: karmic-uec-amd64.img.part.1
Uploading part: karmic-uec-amd64.img.part.2
Uploading part: karmic-uec-amd64.img.part.3
Uploading part: karmic-uec-amd64.img.part.4
Uploading part: karmic-uec-amd64.img.part.5
Uploading part: karmic-uec-amd64.img.part.6
Uploading part: karmic-uec-amd64.img.part.7
Uploading part: karmic-uec-amd64.img.part.8
Uploading part: karmic-uec-amd64.img.part.9
Uploading part: karmic-uec-amd64.img.part.10
Uploading part: karmic-uec-amd64.img.part.11
Uploading part: karmic-uec-amd64.img.part.12
Uploading part: karmic-uec-amd64.img.part.13
Uploading part: karmic-uec-amd64.img.part.14
Uploading part: karmic-uec-amd64.img.part.15
Uploading part: karmic-uec-amd64.img.part.16
Uploading part: karmic-uec-amd64.img.part.17
Uploaded image as uecrckernel/karmic-uec-amd64.img.manifest.xml
nimbusadmin at nimbus:~$ euca-register uecrckernel/karmic-uec-amd64.img.manifest.x
ml
IMAGE emi-76171375
Here's where I fired up the instance:
euca-run-instances -k auueckey emi-76171375 -t c1.medium
Here's what it looks like now:
RESERVATION r-3221069D admin default
INSTANCE i-4F8E099C emi-76171375 131.204.2.112 172.19.1.2
running auueckey 0 c1.medium 2009-10-23T12:50:06.685Z
AUUEC eki-A8AB1882 eri-A52B1860
Here I create my volume:
euca-create-volume -s 1 -z AUUEC
VOLUME vol-329904A4 1 creating 2009-10-23T12:53:53.061Z
euca-describe-volumes
VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53:53.061Z
Here I attach the volume:
euca-attach-volume -i i-4F8E099C -d sdb vol-329904A4
VOLUME vol-329904A4
But:
euca-describe-volumes
VOLUME vol-329904A4 1 AUUEC available 2009-10-23T12:53
In cc.log it says:
[Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] bad input params to vnetAttachTunnels()
[Fri Oct 23 07:56:11 2009][001486][EUCADEBUG ] failed to attach tunnels for vlan 10 during maintainNetworkState()
[Fri Oct 23 07:56:11 2009][001486][EUCAERROR ] network state maintainance failed
--
can't access SC volumes in a UEC instance
https://bugs.launchpad.net/bugs/452185
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
More information about the Ubuntu-server-bugs
mailing list