When you make an error in the ConfigMap Create form and click on 'Create' button, the button remains stuck on loading/spinning phase and is unclickable even after changing the contents of the form (e.g. removing all of the files to meet the size limit criteria, or errors from unexpected format of CM Name). Ultimately forcing the user to refresh the form and fill all of the data again.

Steps to reproduce:

Actual results:

Error shows up, but the Create button keeps spinning and being disabled.

Expected results:

Error to still show up, but the Create button should not be stuck on loading state, we should allow the user to make a correction without a refresh.