Detailed bug description:
I am using on opnfv installation and FUEL shows a very weird behaviour.
In the nodes tab, if you have multiple nodes with the same NICS but different configuration in the VLANS, fuel does inform you that these nodes are different.
Therefore when you select multiple nodes, it will apply changes to all the NICS according the node which is first in the list without you knowing about it. Then if you click go to node list,it will prompt saying that it made changes which the user cannot see.
This behaviour seems very weird to me.
Steps to reproduce:
Create env with multiple nodes .
Pick a node with 2 nics (f.e)and make the first nic PXE+public and all the rest in the other NIC and make this a controller.
Pick another node with 2 NICS and make first nic PXE only and all the other vnics to the other nic and make this also a controller.
Now in the list you can select both of the them and click configure interfaces.
Click back to node list.
---Get confused.---
Expected results:
I would expect that at least a warning would be given here that the nodes are not the same
Actual result:
Total confusion
Reproducibility:
Always
Description of the environment:
OPNFV pharos installation with 5 ARM boards.
Detailed bug description:
I am using on opnfv installation and FUEL shows a very weird behaviour.
In the nodes tab, if you have multiple nodes with the same NICS but different configuration in the VLANS, fuel does inform you that these nodes are different.
Therefore when you select multiple nodes, it will apply changes to all the NICS according the node which is first in the list without you knowing about it. Then if you click go to node list,it will prompt saying that it made changes which the user cannot see.
This behaviour seems very weird to me.
Steps to reproduce:
Create env with multiple nodes .
Pick a node with 2 nics (f.e)and make the first nic PXE+public and all the rest in the other NIC and make this a controller.
Pick another node with 2 NICS and make first nic PXE only and all the other vnics to the other nic and make this also a controller.
Now in the list you can select both of the them and click configure interfaces.
Click back to node list.
---Get confused.---
Expected results:
I would expect that at least a warning would be given here that the nodes are not the same
Actual result:
Total confusion
Reproducibility:
Always
Description of the environment:
OPNFV pharos installation with 5 ARM boards.