There are several environment can be in production fuel. Sometimes we can break settings of another environment while it is being deployed.
Steps to reproduce:. 1. Prepare FueL environment 2. Configure network settings 3. Start deployment. 4. Go to tab "Networks" 5. Check that "Network Settings" blocked 6. ssh root@<IP-fuel> 7. [root@nailgun ~]# fuel network-group list 8. [root@nailgun ~]# fuel network-group --set --network <id_public> --cidr <CIDR> --gateway <Gateway>
Actual result: Network group id=<id_public> has been updated. Network settings do not protected.
Expected result: "Network Settings" protected
http://srv41-bud.infra.mirantis.net/fuelweb-iso/fuel-9.0-70-2016-03-16_15-05-59.iso.torrent http://srv41-bud.infra.mirantis.net/fuelweb-iso/fuel-9.0-68-2016-03-16_08-00-00.iso.torrent
There are several environment can be in production fuel. Sometimes we can break settings of another environment while it is being deployed.
Steps to reproduce:.
1. Prepare FueL environment
2. Configure network settings
3. Start deployment.
4. Go to tab "Networks"
5. Check that "Network Settings" blocked
6. ssh root@<IP-fuel>
7. [root@nailgun ~]# fuel network-group list
8. [root@nailgun ~]# fuel network-group --set --network <id_public> --cidr <CIDR> --gateway <Gateway>
Actual result:
Network group id=<id_public> has been updated.
Network settings do not protected.
Expected result:
"Network Settings" protected
http:// srv41-bud. infra.mirantis. net/fuelweb- iso/fuel- 9.0-70- 2016-03- 16_15-05- 59.iso. torrent srv41-bud. infra.mirantis. net/fuelweb- iso/fuel- 9.0-68- 2016-03- 16_08-00- 00.iso. torrent
http://