Comment 5 for bug 514198

Apparently there /was/ a known issue in eucalyptus 1.6 where if someone was to create the same key twice, eucalyptus would end up having a private key that no longer matches the public key. Could that be what happened here ?