Comment 0 for bug 1337884

Revision history for this message
Egor Kotko (ykotko) wrote : Network verification is accessible via cli during provisioning and deployment.

{"build_id": "2014-07-04_13-44-50", "mirantis": "yes", "build_number": "97", "ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f", "nailgun_sha": "d01b4efc0fc4af9d0e316b9dfc7974f16975f822", "production": "docker", "api": "1.0", "fuelmain_sha": "e312e03dbe29d3436958f7ac024402b1c468e2e4", "astute_sha": "644d279970df3daa5f5a2d2ccf8b4d22d53386ff", "release": "5.0.1", "fuellib_sha": "8a7d86a033b82520abe611bc2c286a10eae42d93"}

Steps to reproduce:
1. Create environment
2. During provisioning/deployment execute:
#fuel network --env 1 --verify

Expected result:
command should be inaccessible during provisioning/deployment

Actual result :
command is accessible provisioning/deployment