Bug 1818901 - DEFAULT_FORKS is the wrong Ansible variable name to define the forks number
Summary: DEFAULT_FORKS is the wrong Ansible variable name to define the forks number
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z12
: 13.0 (Queens)
Assignee: Francesco Pantano
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-30 16:36 UTC by Francesco Pantano
Modified: 2023-09-07 22:37 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-common-8.7.1-19.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-24 11:33:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1869764 0 None None None 2020-03-30 16:51:20 UTC
OpenStack gerrit 716020 0 None MERGED Fix ANSIBLE_FORKS env variable in ceph-ansible workbook 2021-02-03 22:32:43 UTC
OpenStack gerrit 716022 0 None MERGED Fix ANSIBLE_FORKS env variable in ceph-ansible workbook 2021-02-03 22:32:43 UTC
Red Hat Product Errata RHBA-2020:2718 0 None None None 2020-06-24 11:33:46 UTC

Description Francesco Pantano 2020-03-30 16:36:32 UTC
Description of problem:

According to [1] the correct name of the environment variable used to override the 
ansible forks integer is ANSIBLE_FORKS.
The workbook [2] is not using the right default, so we can't take advantage of this
setting.

[1] https://docs.ansible.com/ansible/2.6/reference_appendices/config.html#default-forks
[2] https://github.com/openstack/tripleo-common/blob/stable/queens/workbooks/ceph-ansible.yaml#L22

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 14 errata-xmlrpc 2020-06-24 11:33:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2718


Note You need to log in before you can comment on or make changes to this bug.