tripleoclient: heat-native can't be disabled

[Emilien Macchi]

When deploying an Undercloud, heat_native can be False, it'll still be enable. The option is broken.
Also, the documentation of the option is wrong and doesn't help the operator to figure out what the option does.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/606100
Reason: gate is blocked, we need https://review.openstack.org/#/c/607952/. will restore when that lands

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/606100
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=e5a960e88ee8efd2cb213290976029be5b39ea97
Submitter: Zuul
Branch: master

commit e5a960e88ee8efd2cb213290976029be5b39ea97
Author: Emilien Macchi <email address hidden>
Date: Fri Sep 28 10:37:19 2018 -0400

    Allow to actually disable heat-native

    The way heat-native was implemented, we couldn't disable it.
    And when disabled, it was not working.

    - operators can now pass: --heat-native=False or configure
      heat_native=False in undercloud.conf, then heat native will actually be
      disabled.
    - 'latest' tag doesn't exist for centos-binary-heat-all so we default
      to current-tripleo with is a safe default for us.
    - when the heat_all container is done, it returns 137 (kill -9) which is
      good but we don't want to fail on that.

    Change-Id: I092b6dea5a77fc2691c7af5517a76172f8866bd7
    Closes-Bug: #1795000

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 11.1.0 release.