Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Feature request MAR-120 Enable Ansible pipelining in Molecule configuration and document requirements for becoming an unprivileged user
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Go to the next issue (open or closed)
Go to the next open issue
There are no more issues in that direction.
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targetted for
    2.0.0
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    2 hours
  • Time spent
    1 hour
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description

Since Ansible 2.x introduces safer handling when deploying Python scripts/modules in combination with become/become_user, it is necessary to introduce changes to both Molecule configuration and to document this requirement somewhere.

The "problem" is that some of the roles utilise become/become_user combination, and in case the SSH connection is not established via root user, failures will happen due to Ansible being unable to change ownership of copied-over module/Python scripts (see above link for more details).

The following should be done:

  • Update all Molecule configurations to include the following snippet:

    ansible:
      ansiblecfg_ssh_connection:
        pipelining: True
  • Document the use of become/become_user combo in roles and make the user aware of implications and possible solutions (by at least linking to the official project explanation).

  • Usage instructions should be updated to mention this explicitly somewhere at the top, as well as to include pipelining configuration in ansible.cfg.

Todos (0 / 0)
There are no comments