Red Hat Bugzilla – Bug 1465384
[RFE] Advanced installer to check whether ansible_become is properly defined
Last modified: 2017-07-12 10:07:33 EDT
> 3. What is the nature and description of the request?
Having ansible_become under [all:vars] causes issues during installation/upgrade due to local tasks being executed using sudo, e.g temporary directories created using sudo will make the installer to fail when trying to store files with an unprivileged user.
> 4. Why does the customer need this? (List the business requirements here)
As a cluster operator, I'd like to avoid situations where the installer fails due to misplaced options.
> 5. How would the customer like to achieve this? (List the functional requirements here)
Currently the installer already does some sanity checks, adding this one to those check would be enough.
> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Example scenario: During an upgrade, by mistake, the ansible_become has been misplaced under [all:vars]. The installer should fail with a sensible message.
> 10. List any affected packages or components.
AFAICT, we can tell programmatically whether an Ansible variable is defined or not, but not where it was defined.
If instead of asserting that ansible_become is not defined in [all:vars], would it be satisfying to assert that ansible_become is not defined for localhost?