[Murano]Page with env components is in infinite reload state after deployment of a few apps

[Anastasia Kuznetsova]

Step to reproduce:
1. Log in Web UI
2. Import a few application packages to the catalog (e.g. Docker apps)
3. Navigate to "Murano" > "Application Catalog" > "Environments"
4. Create environment and add _a few_ applications to it
5. Send environment to deploy and _stay_ on page with environment components

Observed result:
After finish of deployment (successful or not) page is in reload page (in Chrome user doesn't see favicon of the page, just load sign) and after clicking on any button happens nothing, all is hanging, user has to sign out and sign in again to continue work.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/182290

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/182369

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/182290
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=8aa77dbf43868620ed4e04554f578fa9c7d743f1
Submitter: Jenkins
Branch: master

commit 8aa77dbf43868620ed4e04554f578fa9c7d743f1
Author: Kirill Zaitsev <email address hidden>
Date: Tue May 12 16:23:38 2015 +0300

    Environments: reload page after all the environments have been updated

    Before murano had an overriden datatable script in
    horizon.tables+reload.js. This script was copy-pasted for a single
    single line edit. This is actually not required, because horion
    datatables fire a "update" trigger after row updates,
    which is enough for the purpose of updating the page.

    Before any row in the ready/deploy_failure would trigger a reload.
    With this patch only an update trigger is set for the services table
    instead of overriding whole datatable js routine. The page is
    reloaded only after there are no rows with 'status_unknown', i.e.
    when every app either deployed or failed to deploy.

    Change-Id: I254538cb776d2dee422be0363a736a5a9c1c9e2b
    Closes-Bug: #1454221

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/182369
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=7480d700527741da27c03ef4ca44d8cf00ffca6e
Submitter: Jenkins
Branch: stable/kilo

commit 7480d700527741da27c03ef4ca44d8cf00ffca6e
Author: Kirill Zaitsev <email address hidden>
Date: Tue May 12 16:23:38 2015 +0300

    Environments: reload page after all the environments have been updated

    Before murano had an overriden datatable script in
    horizon.tables+reload.js. This script was copy-pasted for a single
    single line edit. This is actually not required, because horion
    datatables fire a "update" trigger after row updates,
    which is enough for the purpose of updating the page.

    Before any row in the ready/deploy_failure would trigger a reload.
    With this patch only an update trigger is set for the services table
    instead of overriding whole datatable js routine. The page is
    reloaded only after there are no rows with 'status_unknown', i.e.
    when every app either deployed or failed to deploy.

    Change-Id: I254538cb776d2dee422be0363a736a5a9c1c9e2b
    Closes-Bug: #1454221

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/185057

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/185057
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=275b545e5a9a48bdb08afa68f8c3e0520afe02c4
Submitter: Jenkins
Branch: master

commit 275b545e5a9a48bdb08afa68f8c3e0520afe02c4
Author: Kirill Zaitsev <email address hidden>
Date: Fri May 22 18:58:18 2015 +0300

    Call location.reload only once at successfull env deployment

    Before it was possible, that in some configurations table update events
    would stack and reload would be called multiple times.
    This change introduces a global js variable, that would prevent
    location.reload from being called more than once.

    Change-Id: Idb332e56b764d494a51de74398e7098c68561c61
    Related-Bug: #1454221

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/kilo
Review: https://review.openstack.org/198890

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/198890
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=6aba78cac65ecdfeda5ef93dd8c0010a4a8c8a03
Submitter: Jenkins
Branch: stable/kilo

commit 6aba78cac65ecdfeda5ef93dd8c0010a4a8c8a03
Author: Kirill Zaitsev <email address hidden>
Date: Fri May 22 18:58:18 2015 +0300

    Call location.reload only once at successfull env deployment

    Before it was possible, that in some configurations table update events
    would stack and reload would be called multiple times.
    This change introduces a global js variable, that would prevent
    location.reload from being called more than once.

    Change-Id: Idb332e56b764d494a51de74398e7098c68561c61
    Related-Bug: #1454221

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/murano-dashboard 2015.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano-dashboard 2015.1.1 release.