Fuel UI Lock network CIDR input field(s) after deployment

[Kyrylo Galanov]

Based on https://bugs.launchpad.net/fuel/+bug/1587897, it is impossible to change network CIDR on redeployment. This field should be disabled after the first deployment and enabled on cluster reset.

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Julia Aranovich (jkirnosova)]

Can not reproduce a locked CIDR in deployed environment on fake UI.
Could you please provide steps to reproduce, screenshots or maybe you have a live environment to research the issue?

[Julia Aranovich (jkirnosova)]

Related bug: https://bugs.launchpad.net/fuel/+bug/1587897

[Alexey Shtokolov (ashtokolov)]

The RC is that Neutron doesn't support the CIDR changes for floating networks.
So we should keep this field unlocked because the public network can be extended by new ranges.

[Julia Aranovich (jkirnosova)]

So, the reason of the deployment failure should be fixed in backend. Locking of UI fields is hacking in this case.
Will remove area-ui tag for now. Please revert back if UI changes will be required.