Comment 2 for bug 1380805

I suspect it's something to do with NodeGroupDefineForm, which blindly overwrites the cluster_name if one is not supplied in the form data.

I'm still not sure why this form is getting invoked upon an upgrade, maybe it's something to do with the changed way in which clusters register in the region now.

Given that the model code for new() also does this defaulting of the name, I am going to remove this overriding behaviour from the form. The cluster_name can happily live as a blank field so I don't see the point of defaulting it and especially not overriding existing values.