Limit Is Not Always Used
Bug #1880977 reported by
Luke Short
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Luke Short |
Bug Description
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-
Expected result
===============
The deployment is run in the background with `ansible-playbook --limit overcloud-
Actual result
=============
The limit command is not passed.
Environment
===========
- Train
- RHEL 8.2
- Splitstack
Logs & Configs
==============
BugZilla with more details: https:/
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/730426 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=f161bfb049b 23b53706e6950f7 1aaaadf4687131
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit f161bfb049b23b5 3706e6950f71aaa adf4687131
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 download_ deploy.
passed to the ansible-playbook command during config_
Change-Id: Ie5b8d41abacb07 1f528d4f9220bff 3532ed0ab2f
Closes-Bug: #1880977
Signed-off-by: Luke Short <email address hidden>