Fuel Noop run results in unusable environment

[Sam Stoelinga]

Version found: MOS 9.0

Description: Running fuel2 env redeploy --noop results in an environment which becomes totally unusable, you can not even delete the environment.

Steps to reproduce:
1. Install MOS 9.0
2. Create a new env with 1 controller + 1 compute node + Cinder LVM
3. Update Fuel master to MOS 9.1 according to https://docs.mirantis.com/openstack/fuel/fuel-master/operations/update-from-9-to-9-1.html
$ vim /etc/yum.repos.d/mos-updates.repo
Change baseurl to
baseurl=http://mirror.fuel-infra.org/mos-repos/centos/mos9.0-centos7/snapshots/proposed-2016-10-02-090322/x86_64/
$ yum clean all
$ yum install python-cudet
$ update-prepare prepare master
$ update-prepare prepare env
$ fuel2 env redeploy --noop
4. Wait for the noop to complete by checking fuel tasks
5. Notice that it never completes
6. Try to stop the noop task with
$ fuel stop --env 1
7. Try to delete env
$ fuel delete --env 1

Current result:
Stopping doesn't stop. Deleting doesn't delete, removing nodes doesn't work either. The whole env is unusable.

Expected result:
Each action to work and complete on a clean env.

Impact:
High: Not able to update to latest version following workflow recommended in docs.

[Vitaly Sedelnik (vsedelnik)]

Sam, I was unable to reproduce this issue. Please provide an env so we could look into it.

[Sam Stoelinga (sammiestoel)]

Wasn't able to reproduce either. Tried again on a 3 controller env and --noop tasks succeeded.

[Alexander Kurenyshev (akurenyshev)]

Closing as there was no a reproduce within a month.Feel free to reopen the bug if it appears again