Bug 1506781
Summary: | ansible 2.4 broke ansible-pull | ||
---|---|---|---|
Product: | Red Hat Ansible Engine | Reporter: | Orion Poplawski <orion> |
Component: | ansible | Assignee: | Pavel Cahyna <pcahyna> |
Status: | CLOSED ERRATA | QA Contact: | Leos Pol <lpol> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | kdreyer, ovasik |
Target Milestone: | --- | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ansible-2.4.2.0-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-01-25 12:58:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1527004 | ||
Bug Blocks: |
Description
Orion Poplawski
2017-10-26 17:50:40 UTC
Broken in a number of other ways it seems as it appears to fail to do a git pull to update a checked out repo. Will be solved by a rebase to 2.4.2.0. Do you have an idea when the rebase to 2.4.2.0 could take place and the new version would be available? (In reply to Joerg K from comment #4) > Do you have an idea when the rebase to 2.4.2.0 could take place and the new > version would be available? I am working on it, it is tracked in bz1527004 (In reply to Pavel Cahyna from comment #5) > I am working on it, it is tracked in bz1527004 Thanks for the notice. ansible-2.4.2.0-1.el7.noarch 1. create local git repo 2. add ansible.cfg, inventory, simple playbook 3. commit repo 4. ansible-pull -U <repo> <playbook> ansible-pull pulls the repo and executes playbook 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-2018:0203 |