UI allow 2 untagged networks on one phys. interface

[Sergey Vasilenko]

I do not known how I do it, but I can assign 2 networks (management and storage) to one phys. interface.
Screenshots attached, VMs snapshoted.

Centos, fuel-3.2.1-82-2013-12-02_19-17-26.iso

[Sergey Vasilenko (xenolog)]

And another question (see first screenshot) -- are you shoure that many ranges will works with Quantum?

[Aleksey Kasatkin (alekseyk-ru)]

Big number of ranges can be used in nailgun only - for assigning of IPs. But one CIDR only is given to orchestrator. All IP ranges must fit into one CIDR.

[Aleksey Kasatkin (alekseyk-ru)]

It was discussion in chat on this thing. It's not a bug.
This situation can be reproduced with the following:
1. Create cluster.
2. Add one node to cluster (public, management and storage networks use the same NIC and public is untagged by default).
3. Make one of the networks untagged (e.g. Storage) and save configuration.
4. Go to node interfaces configuration page, you will see that public and storage are untagged and they use the same NIC.

It doesn't affect functionality as untagged intersection is checked before Deployment and before running verification of networking.
Now warning is shown to the user on node interfaces configuration page when he has such a situation (see the picture below) - it was done for v.4.0 (see https://mirantis.jira.com/browse/PRD-2273).
It doesn't make sense to prohibit change of tagged network to untagged when some node has such a collision because it'll be hard to make custom configuration using UI. Full configuration consistency is not required at the time of its tuning (at least in this case).

Another problem - "can't download diag.snapshots" - is reported here: https://bugs.launchpad.net/fuel/+bug/1258436.