[negative][UX] Very unclear message in UI after network settings were changed

[Nastya Urlapova]

If user want change network settings in cases of deployment failure, so he/she will see very unclear message, exmp.:
New IP ranges for network 'public'(2) do not cover already allocated IPs.
Cancel ChangesSave Settings

Scenario:
1. create cluster with default settings
2. add one node
3. deployment must fail - very important step, in my case I've set incorrect range for public net
4. as user I want change public range, and I've put correct ranges
5. if I'll try save settings, I get
>>>
New IP ranges for network 'public'(2) do not cover already allocated IPs.

How I should understand that I cannot change net settings from that message, and what I should to do for fix?

9.0 mos #352

Note. The same error can be observed after successful deployment if user wants to change network parameters so that they do not cover IPs of deployed entities.

[Julia Aranovich (jkirnosova)]

The message comes from Nailgun response. We need a help of network guys to understand what's the issue here and whether we need to change UI (add an appropriate validation, etc.)?

[Peter Zhurba (pzhurba)]

What is wrong?
You add node it obtain setting then you try change it to other which not cover current.

As i can see problem is

Fuel doesn't update default parameters after changing default setting.

[Nastya Urlapova (aurlapova)]

@Peter, if user was mistaken, he/she will not able apply right settings + steps that user should to do are unclear - reset node, or just upload defaults?

[Aleksey Kasatkin (alekseyk-ru)]

I'd propose to improve the message and include nodes/VIPs that are not covered with new settings. What should user do ... it depends on what he wants to archive and/or what entities are not covered with new settings. I don't think the list of options should be a part of error message. It is more likely to be addressed in the documentation.

[Peter Zhurba (pzhurba)]

@Nastya

There is no way to update some parameters configuring by default.

As I understand there is only common hack:

   Remove node from cluster and add it back or push load defaults on node page.

The same happens if you after reset env increase memory size for nodes.

[Aleksandr Didenko (adidenko)]

> I'd propose to improve the message and include nodes/VIPs that are not covered with new settings.

I'm afraid that it won't help in this particular case.
For me personally, existing error message is clear enough and any additional info is not needed.
And for users who don't know how to proceed with existing message, additional information with exact list of nodes won't help.

> I don't think the list of options should be a part of error message. It is more likely to be addressed in the documentation.

+1. I also think that the best option is do describe this situation in our documentation.

[Nastya Urlapova (aurlapova)]

@Alex, I cannot agree here with you,I think message is absolutely unclear, and we can put a small instruction or ref to doc as minimum.

[Aleksandr Didenko (adidenko)]

Forwarding this bug to docs team. Additional info:

In case user gets error like this:

New IP ranges for network 'public'(2) do not cover already allocated IPs.

User should check new network ranges and either adjust them to cover all allocated IPs, or reset the env and then update network ranges. In order to check allocated IPs user can login to any node and check IPs in /etc/astute.yaml ('network_metadata[nodes]' list). If only few nodes do not fit into new network ranges, then it's possible to delete them from environment, update network ranges, and re-add deleted nodes back.

[Aleksey Kasatkin (alekseyk-ru)]

> In order to check allocated IPs ...

as an option, user can download interfaces info for nodes via CLI and find IPs there.

[Aleksey Kasatkin (alekseyk-ru)]

User should also check that VIP addresses conform to new IP ranges.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/317403

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/323230

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/317403
Committed: https://git.openstack.org/cgit/openstack/fuel-docs/commit/?id=1675f2548acb786654fb0f00f29c0d78ea9c7934
Submitter: Jenkins
Branch: master

commit 1675f2548acb786654fb0f00f29c0d78ea9c7934
Author: OlgaGusarenko <email address hidden>
Date: Tue May 17 14:17:17 2016 +0300

    [UG] Network IP ranges reconfiguration after deployment

    * Adds the Troubleshooting section
    * Adds the soultion for the error that Fuel displays if the new
      ranges do not cover the IP addresses already allocated to nodes
      during the deployment

    Change-Id: Id58759b30288c2648aab6a302307a5033649e776
    Closes-bug: #1581080

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/323230
Committed: https://git.openstack.org/cgit/openstack/fuel-docs/commit/?id=a1b443da4822673efeafff0cb1f495e2c8004060
Submitter: Jenkins
Branch: stable/mitaka

commit a1b443da4822673efeafff0cb1f495e2c8004060
Author: OlgaGusarenko <email address hidden>
Date: Tue May 17 14:17:17 2016 +0300

    [UG] Network IP ranges reconfiguration after deployment

    * Adds the Troubleshooting section
    * Adds the soultion for the error that Fuel displays if the new
      ranges do not cover the IP addresses already allocated to nodes
      during the deployment

    Change-Id: Id58759b30288c2648aab6a302307a5033649e776
    Closes-bug: #1581080

[Nastya Urlapova (aurlapova)]

http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/troubleshooting/network.html