Experimental features are not available if user add 'advanced' in astute.yaml

[Tatyanka]

Steps:
1. Deploy master node and bootsrap 3 slaves
2. Add advanced into feature_group into /etc/fuel/astute.yaml
3. Restart nailgun container
4. Try to assign virt + compute role for node (UI/api)

Expected:
According to https://bugs.launchpad.net/fuel/+bug/1526448 experimental mode should be enables and virst role should be accessible

Actual:
virt role in UI in not available, api fails with 404 not found

As soon as user enables this mode in version yaml - all works as expected - I can add virt role to compute/ Put vm config and spawn it

[root@nailgun ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - advanced
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "361"
  build_id: "361"
  fuel-nailgun_sha: "53c72a9600158bea873eec2af1322a716e079ea0"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "7463551bc74841d1049869aaee777634fb0e5149"
  fuel-nailgun-agent_sha: "92ebd5ade6fab60897761bfa084aefc320bff246"
  astute_sha: "c7ca63a49216744e0bfdfff5cb527556aad2e2a5"
  fuel-library_sha: "ba8063d34ff6419bddf2a82b1de1f37108d96082"
  fuel-ostf_sha: "889ddb0f1a4fa5f839fd4ea0c0017a3c181aa0c1"
  fuel-mirror_sha: "8adb10618bb72bb36bb018386d329b494b036573"
  fuelmenu_sha: "824f6d3ebdc10daf2f7195c82a8ca66da5abee99"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "9f0ba4577915ce1e77f5dc9c639a5ef66ca45896"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "07d5f1c3e1b352cb713852a3a96022ddb8fe2676"
[root@nailgun ~]#

[Matthew Mosesohn (raytrac3r)]

Raising to high. We need the ability to enable experimental features.

[Matthew Mosesohn (raytrac3r)]

Probably a duplicate of https://launchpad.net/bugs/1526874 which was just closed. Waiting on new iso to confirm if this is fixed already.

[Vladimir Kozhukalov (kozhukalov)]

astute.yaml is a deployment config. So if you modify feature_groups in astute.yaml you then need to re-deploy nailgun (i.e. restart docker container with re-deployment). Otherwise you can modify /etc/nailgun/settings.yaml inside nailgun container and restart nailgun itself.

[Tatyanka (tatyana-leontovich)]

yep we restarted it (see step 3 )

[Dmitry Pyzhov (dpyzhov)]

Tatyana will check if this bug is a duplicate for bug #1526874 or not