ansible / awx-facts-playbooks Goto Github PK

Repository containing playbooks to support fact scanning in Ansible Tower and AWX.

Python 72.56% PowerShell 27.44%

awx-facts-playbooks's Introduction

Ansible

Ansible is a radically simple IT automation system. It handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. Ansible makes complex changes like zero-downtime rolling updates with load balancers easy. More information on the Ansible website.

Design Principles

Have an extremely simple setup process with a minimal learning curve.
Manage machines quickly and in parallel.
Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon.
Describe infrastructure in a language that is both machine and human friendly.
Focus on security and easy auditability/review/rewriting of content.
Manage new remote machines instantly, without bootstrapping any software.
Allow module development in any dynamic language, not just Python.
Be usable as non-root.
Be the easiest IT automation system to use, ever.

Use Ansible

You can install a released version of Ansible with pip or a package manager. See our installation guide for details on installing Ansible on a variety of platforms.

Power users and developers can run the devel branch, which has the latest features and fixes, directly. Although it is reasonably stable, you are more likely to encounter breaking changes when running the devel branch. We recommend getting involved in the Ansible community if you want to run the devel branch.

Get Involved

Read Community Information for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
Join a Working Group, an organized community devoted to a specific technology domain or platform.
Submit a proposed code update through a pull request to the devel branch.
Talk to us before making larger changes to avoid duplicate efforts. This not only helps everyone know what is going on, but it also helps save time and effort if we decide some changes are needed.
For a list of email lists, IRC channels and Working Groups, see the Communication page

Coding Guidelines

We document our Coding Guidelines in the Developer Guide. We particularly suggest you review:

Branch Info

The devel branch corresponds to the release actively under development.
The stable-2.X branches correspond to stable releases.
Create a branch based on devel and set up a dev environment if you want to open a PR.
See the Ansible release and maintenance page for information about active branches.

Roadmap

Based on team and community feedback, an initial roadmap will be published for a major or minor version (ex: 2.7, 2.8). The Ansible Roadmap page details what is planned and how to influence the roadmap.

Authors

Ansible was created by Michael DeHaan and has contributions from over 5000 users (and growing). Thanks everyone!

Ansible is sponsored by Red Hat, Inc.

License

GNU General Public License v3.0 or later

See COPYING to see the full text.

awx-facts-playbooks's People

Contributors

Stargazers

Watchers

awx-facts-playbooks's Issues

AWX does not work

I cannot seem to get this task working on the newest opensource awx 1.0.4

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/var/lib/awx/projects/_11__ansible_playbook/scan_facts.yml': line 7, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
    - name: "Scan packages (Unix/Linux)"
      ^ here
The error appears to have been in '/var/lib/awx/projects/_11__ansible_playbook/scan_facts.yml': line 7, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
    - name: "Scan packages (Unix/Linux)"
      ^ here
exception type: <class 'ansible.errors.AnsibleParserError'>
exception: no action detected in task. This often indicates a misspelled module name, or incorrect module path.
The error appears to have been in '/var/lib/awx/projects/_11__ansible_playbook/scan_facts.yml': line 7, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
    - name: "Scan packages (Unix/Linux)"
      ^ here

error while running playbook

hello,

got this error

The offending line appears to be:


    - name: "Scan packages (Unix/Linux)"
      ^ here


The error appears to have been in '/var/lib/awx/projects/_9__scan_project/scan_facts.yml': line 7, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


    - name: "Scan packages (Unix/Linux)"
      ^ here

Change Path to machine-id for INSIGHTS_SYSTEM_ID_FILE

The machine-id no longer points to /etc/redhat-access-insights/machine-id

This should be changed to /etc/machine-id

RHEL8

ls -al /etc/redhat-access-insights/machine-id
ls: cannot access '/etc/redhat-access-insights/machine-id': No such file or directory

RHEL7

ls -al /etc/redhat-access-insights/machine-id
ls: cannot access '/etc/redhat-access-insights/machine-id': No such file or directory

Scan Facts Playbook Hangs Indefinitely Due to tset Command

Issue

Some environments hang indefinitely due to missing terminal in Tower when running these facts playbooks.

Replication

Run a playbook against a host with the oracle oem agent in Tower/AWX
Wait for the job to complete

Expected

Job finishes

Observed

Job hangs indefinitely

PID Trace on the host:

  ├─sshd -D [email protected],[email protected],aes256-ctr,aes256-cbc,[email protected],aes128-ctr,[email protected],hmac-sha1-et
  │   ├─sshd
  │   │   └─sshd
  │   │       └─sh -c...
  │   │           └─sudo -H -S -n -u root /bin/sh -c ...
  │   │               └─sh -c echo BECOME-SUCCESS-hfyjvwruwzozgfynbrxxybrukfqgskft ; /usr/bin/python /tmp/ansible-tmp-1632758464.7292757-686745-170612301098636/AnsiballZ_scan_services.py
  │   │                   └─python /tmp/ansible-tmp-1632758464.7292757-686745-170612301098636/AnsiballZ_scan_services.py
  │   │                       └─service /sbin/service gcstartup status
  │   │                           └─gcstartup /etc/init.d/gcstartup status
  │   │                               └─su - storacle -c /dba/software/oem/agent_13.5.0.0.0/install/unix/scripts/agentstup status /dba/software/oem/agent_inst storacle &
  │   │                                   └─ksh -c /dba/software/oem/agent_13.5.0.0.0/install/unix/scripts/agentstup status /dba/software/oem/agent_inst storacle &
  │   │                                       └─tset -s -Q

Additional Information

Running the ad-hoc command tset -s -Q targeting the same host results in the ad-hoc job hanging indefinitely as well.

Workaround for scan_facts.yml, adding TERM environment variable in PLAY:

- hosts: all
  environment:
    TERM: 'xterm'
  vars:
    scan_use_checksum: false
    scan_use_recursive: false
  tasks:
[...]