[pike] Update CLI stops producing output

[Jiří Stránský]

Sometimes when a minor update takes too long, the CLI completely stops producing output, even though there's nothing wrong with the update actions.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/585380
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=6f15c96eb0d14a891fc0db3ede20b77622a4573b
Submitter: Zuul
Branch: stable/pike

commit 6f15c96eb0d14a891fc0db3ede20b77622a4573b
Author: Mathieu Bultel <email address hidden>
Date: Fri Apr 20 11:08:53 2018 +0200

    Use ansible_queue_name only for upgrade/update

    For upgrade and update nodes with ansible, we do not
    need to play with both queue: tripleo and upgrade queue.
    If we use both, we can have race where the both can have
    different status and we enter in an infinite loop while
    reading the socker.

    Change-Id: I484a3af4a830af3b97231558876d9a6c0a31e603
    Partial-Bug: #1783798
    (cherry picked from commit 61dfe32a2a72e5341575ecaa2762f889a2d30e46)
    (cherry picked from commit d11bc74b443648c05d4dfb22ffeff285e8926f8e)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/585386
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=94d33fc041881a00598985dd93914aa1c30eddff
Submitter: Zuul
Branch: stable/pike

commit 94d33fc041881a00598985dd93914aa1c30eddff
Author: Mathieu Bultel <email address hidden>
Date: Fri Apr 20 11:15:32 2018 +0200

    Use only update/upgrade ansible queue instead

    Related tripleo-common change:
    https://review.openstack.org/562995

    To avoid race between tripleo queue and ansible queue
    we need to use inly ansible queue for update and upgrade

    Change-Id: I39b5a1a154b10683ac0de85afd6bbadc3491192a
    Partial-Bug: #1783798
    (cherry picked from commit 3b197c09911997e0f7ff127deff892e064a58786)
    (cherry picked from commit 782ad7375cf17efe99332e4ac2d0a1a9a5cd1b39)