[dhparam] Incorrect facts set when dhparam__deploy_state is 'absent'
Open
Nobody has claimed this yet.
bug
tag: Ansible facts
tag: good first issue
tag: PKI
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
The role sets incorrect local facts when dhparam__deploy_state is set to 'absent'.
Steps to reproduce:
- Set
dhparam__deploy_stateto 'absent'. - Run dhparam playbook.
$ cat /etc/ansible/facts.d/dhparam.fact
Actual results:
{
"bits": [
"3072",
"2048"
],
"default": "/etc/pki/dhparam/set0",
"default_length": "3072",
"enabled": "true",
"set_prefix": "set",
"sets": [
0
],
"set0": "/etc/pki/dhparam/set0",
"hooks": "/etc/pki/dhparam/hooks.d",
"library": "openssl",
"path": "/etc/pki/dhparam",
"params": "/etc/pki/dhparam/params"
}
Expected results:
{
"enabled": "false"
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the dhparam role or playbook and trace how dhparam__deploy_state controls the local facts written to /etc/ansible/facts.d/dhparam.fact. Reproduce the absent-state run, then verify that the fact file contains only enabled: false as shown in the expected results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100