[Kubernetes] Murano environment with k8s hangs on delete

[Victor Ryzhenkin]

Using latest k8s apps.

1. Deploy k8s cluster
2. Wait for result
3. Delete an environment

Expected:
App deleted successfully

Actual:
Stack successfully deleted, but environment hanging in DELETION status

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/233298

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/233297
Committed: https://git.openstack.org/cgit/openstack/murano-apps/commit/?id=dabb1ee6061858d456016511e1524af69ebc43db
Submitter: Jenkins
Branch: master

commit dabb1ee6061858d456016511e1524af69ebc43db
Author: Stan Lagun <email address hidden>
Date: Sat Oct 10 01:41:09 2015 +0300

    [Docker] Do not try to delete container on destroyed host

    When Environment get deleted both Docker/k8s host and
    Docker applications get deleted. So it is possible that host
    will try to delete container from an Instance that was already
    destroyed. Attempt to send commands to such instance
    will hang until timeout because there is no more agent
    exist on the other side.

    Change-Id: Ia6e8064ae50c24ce595ed08e446ed45b96b4a330
    Closes-Bug: #1504623
    Depends-On: I298f3f079a153ef87ed7213b7f1432c9e5e4b4b6

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/233298
Committed: https://git.openstack.org/cgit/openstack/murano-apps/commit/?id=dcf1f0672f2b1e1f70e4d8a93505ed084e7e9b65
Submitter: Jenkins
Branch: stable/liberty

commit dcf1f0672f2b1e1f70e4d8a93505ed084e7e9b65
Author: Stan Lagun <email address hidden>
Date: Sat Oct 10 01:41:09 2015 +0300

    [Docker] Do not try to delete container on destroyed host

    When Environment get deleted both Docker/k8s host and
    Docker applications get deleted. So it is possible that host
    will try to delete container from an Instance that was already
    destroyed. Attempt to send commands to such instance
    will hang until timeout because there is no more agent
    exist on the other side.

    Change-Id: Ia6e8064ae50c24ce595ed08e446ed45b96b4a330
    Closes-Bug: #1504623
    Depends-On: I298f3f079a153ef87ed7213b7f1432c9e5e4b4b6

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/320551
Committed: https://git.openstack.org/cgit/openstack/murano-apps/commit/?id=a1a0fcd6793112ecb29b34a855c159bfa6f23d8d
Submitter: Jenkins
Branch: stable/kilo

commit a1a0fcd6793112ecb29b34a855c159bfa6f23d8d
Author: Stan Lagun <email address hidden>
Date: Sat Oct 10 01:41:09 2015 +0300

    [Docker] Do not try to delete container on destroyed host

    When Environment get deleted both Docker/k8s host and
    Docker applications get deleted. So it is possible that host
    will try to delete container from an Instance that was already
    destroyed. Attempt to send commands to such instance
    will hang until timeout because there is no more agent
    exist on the other side.

    Change-Id: Ia6e8064ae50c24ce595ed08e446ed45b96b4a330
    Closes-Bug: #1504623
    Depends-On: I298f3f079a153ef87ed7213b7f1432c9e5e4b4b6
    (cherry picked from commit dcf1f0672f2b1e1f70e4d8a93505ed084e7e9b65)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano-apps 1.0.1 release.