I figured out the problem. I was looking at the web interface, under configuration in the Storage Controller section, the IP address there was my public IP address and the ethernet device was my public ethernet interface. When I changed the IP address to my private IP address and private IP address, and I created a brand new volume (the old volume would not work) this is what happened:
euca-create-volume -s 1 -z AUUEC VOLUME vol-32EA04B0 1 creating 2009-10-23T14:41:47.375Z euca-attach-volume -i i-500E09A7 -d /de v/sdb vol-32EA04B0 euca-describe-volumes VOLUME vol-32EA04B0 1 AUUEC in-use 2009-10-23T14:41:47.375Z ATTACHMENT vol-32EA04B0 i-500E09A7 /dev/sdb 2009-10-23T14:42:10.274Z Then I could go in my instance, see the volume, fdisk it, create a partition, format it , mount it and create/delete files on it. I am happy! However, the question now becomes - why did the Storage Controller register itself on my public IP and public interface as opposed to my private IP and private interface? -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
