Limit Is Not Always Used

[Luke Short]

Description
===========
Train deployment on RHEL 8.2 using the new limit argument does not always get passed to Ansible. This only affects Train (not >= Ussuri or <= Stein).

Steps to reproduce
==================
- `openstack overcloud deploy --limit overcloud-controller-0`

Expected result
===============
The deployment is run in the background with `ansible-playbook --limit overcloud-controller-0`.

Actual result
=============
The limit command is not passed.

Environment
===========
- Train
- RHEL 8.2
- Splitstack

Logs & Configs
==============
BugZilla with more details: https://bugzilla.redhat.com/show_bug.cgi?id=1840159

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/730426
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=f161bfb049b23b53706e6950f71aaaadf4687131
Submitter: Zuul
Branch: stable/train

commit f161bfb049b23b53706e6950f71aaaadf4687131
Author: Luke Short <email address hidden>
Date: Fri May 22 20:48:45 2020 -0400

    [Train-Only] Fix mixing nodes and limit_hosts.

    This corrects a behavior where in some cases the --limit is not
    passed to the ansible-playbook command during config_download_deploy.

    Change-Id: Ie5b8d41abacb071f528d4f9220bff3532ed0ab2f
    Closes-Bug: #1880977
    Signed-off-by: Luke Short <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 11.5.0 release.