Comment 4 for bug 1305550

Jay,
My point above was that we don't give an end user any way to "know" what valid retype combinations are. So having them just "guess" and then if they guess incorrectly putting their volume in an unusable state (error) seems like a bad end user experience. Keep in mind that the end user would have to contact an admin to troubleshoot what happened as well as reset the status on the volume to make it usable again. This seems like a really bad experience in my opinion.

Why not just set a special "new" status like "invalid-retype-request" that doesn't block it from being used going forward but still gives a reasonably informative status? Then clear this on any subsequent calls.. it would basically be treated just as "available".