Discard button is absent in case of failed deployment

[Volodymyr Shypyguzov]

Steps to reproduce:
1.Setup master node
2.Create a new env
3.Change some task to fail deploy, for example:
  echo 'fail("Emulate deployment failure after netconfig!")' >> /etc/puppet/modules/osnailyfacter /modular/netconfig/connectivity_tests.pp
4.Deploy environment
5.Make some changes on the Settings or Network tabs
6.Go to the Dashboard page and check Discard button (white cross above the Deploy Changes button). 7.Press it

Actual result: Discard button is not present
Expected result: Discard button is present and operational

In JS console log :

GET https://10.109.0.2:8443/api/clusters/2/attributes/deployed?_=1463995996878 404 Not Found 8ms
GET https://10.109.0.2:8443/api/clusters/2/network_configuration/deployed?_=1463995996879
404 Not Found 13ms

[Julia Aranovich (jkirnosova)]

Deployed environment configuration does not exist in backend, so UI doesn't have a configuration to reset and doesn't show this Discard button.
This is not Fuel UI issue.

[Volodymyr Shypyguzov (vshypyguzov)]

[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 376
cat /etc/fuel_build_number:
 376
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6346.noarch
 fuel-bootstrap-cli-9.0.0-1.mos281.noarch
 fuel-migrate-9.0.0-1.mos8376.noarch
 rubygem-astute-9.0.0-1.mos745.noarch
 fuel-misc-9.0.0-1.mos8376.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos136.noarch
 fuel-openstack-metadata-9.0.0-1.mos8693.noarch
 fuel-notify-9.0.0-1.mos8376.noarch
 nailgun-mcagents-9.0.0-1.mos745.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8693.noarch
 python-fuelclient-9.0.0-1.mos315.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6346.noarch
 fuel-utils-9.0.0-1.mos8376.noarch
 fuel-setup-9.0.0-1.mos6346.noarch
 fuel-library9.0-9.0.0-1.mos8376.noarch
 shotgun-9.0.0-1.mos88.noarch
 fuel-agent-9.0.0-1.mos281.noarch
 fuel-ui-9.0.0-1.mos2688.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 python-packetary-9.0.0-1.mos136.noarch
 fuel-nailgun-9.0.0-1.mos8693.noarch

[Ilya Kutukov (ikutukov)]

I have everything fine on the latest master build:

[Ilya Kutukov (ikutukov)]

Sorry, not latest, fuel-10.0-250-2016-05-20_17-00-59.iso

[Bulat Gaifullin (bulat.gaifullin)]

According the bug description, there is no successful deployment for cluster. that means the deployed configuration does not exists.

[Ilya Kutukov (ikutukov)]

In cluster "stopped" condition there are also no button for the build from current master.

[Julia Aranovich (jkirnosova)]

I think that we get 2 meanings of cluster "deployed" configuration.
The feature was designed to keep 1) cluster configuration that was successfully deployed.
But users think it should be 2) cluster configuration snapshot when starting the latest deployment.

It should be discussed.
Do we need to keep configuration which does not lead to successful deployment? I mean "failed" environment.

The case with "stopped" environment should also be reconsidered.

[Dmitry Pyzhov (dpyzhov)]

This looks like intended behaviour. Roman will raise discussion in openstack-dev about it. We'll move the bug back to 9.0 if we see that it is really High priority and can be solved quickly.

[Roman Prykhodchenko (romcheg)]

I've started a thread in os-dev to discuss this behavior http://lists.openstack.org/pipermail/openstack-dev/2016-May/095922.html

[Roman Prykhodchenko (romcheg)]

After some discussions on the mailing list and at the IRC channel a decision of changing this behavior was not made. Closing this bug as Invalid.