Comment 5 for bug 920408

I'm doing progress here but i really need help to fix this. Now i think i found a way to easily reproduce this error.

My cluster (that is CC and SC) was named as 192.168.1.1 (name and IP), i saw that name mistake and deregister it and register it again with the name of cc-t300. The problems with euca-describe-volumes started at this point. Now i figured out why: i had some volumes created when the name of the cluster was still 192.168.1.1, and in the StorageUtil.java we have this:

public static edu.ucsb.eucalyptus.msgs.Volume getVolumeReply( Map<String, AttachedVolume> attachedVolumes, Volume v ) throws EucalyptusCloudException {
    StorageControllerConfiguration scConfig = Configuration.getStorageControllerConfiguration( v.getCluster( ) );

It means that the method gets the name of the Cluster looking to the volume, all they. But the volume has an old name of Cluster (192.168.1.1), and method getStorageControllerConfiguration can't communicate with it, throwing an exception and stopping the euca-describe-volumes.

So guys, if you wanna reproduce the error just register a cluster (and a storage) with the name clusterA, create some volumes, then deregister sc and cluster, and register again with the name clusterB, then do euca-describe-volumes and you will see the errors message on cloud-debug.log

I can get here on my own, but i really need help to get this fixed from here.

Thanks