Skip to main content

Ansible issues


  1. is not a valid attribute for a Play
    When ever you get the above error firstly crosscheck that the ansible attribute you have mentioned is correct. If it is correct then the issue probably is that you have created tasks as follows:
    ---
    - vars_prompt:
    - name: "var1"
    prompt: "Please pass variable"
    private: no

    - fail: msg="var1 is not passed or blank"
    when: var1 is undefined or ( var1 is defined and storeid == "" )

    when it should be as follows:
    ---
    vars_prompt:
    - name: "var1"
    prompt: "Please pass variable"
    private: no

    tasks:
    - fail: msg="var1 is not passed or blank"
    when: var1 is undefined or ( var1 is defined and storeid == "" )

    the example referenced is just a task. It is not a valid playbook because it is missings a hosts declaration and the module call is not under a tasks section.

  2. ERROR! conflicting action statements: fail, command
    I get this error if I have a task as follows:
    - name: deploy
    win_get_url:
    url: 'http://server_ip/builds/build.zip'
    dest: 'D:\build.zip'
    win_unzip:
    src: D:\build.zip
    dest: D:\You cannot have multiple actions listed inside a single task like this. Instead you need to do this:
        - name: deploy get url
    win_get_url:
    url: 'http://server_ip/builds/build.zip'
    dest: 'D:\build.zip'
    - name: deploy unzip
    win_unzip:
    src: D:\build.zip
    dest: D:\


  3. Ansible task to check API status
    Here I am checking ES cluster health:
    [code]
    - name: Get ES cluster health
    uri:
    url: http://{{inventory_hostname}}:9200/_cluster/health
    return_content: yes
    register: cluster_status

    - set_fact:
    es_cluster_health: "{{ cluster_status.content | from_json }}"

    - fail: msg="ES cluster not healthy"
    when: "es_cluster_health.status != 'yellow'"

    [/code]

    You can compare the status with any string you want. Here I am comparing it with string "yellow"

Comments

Popular posts from this blog

How to grep the output of cURL?

curl writes the output to stderr, so redirect that and also suppress the progress: curl - v -- silent https :// google . com / 2 >& 1 | grep expire The reason why  curl  writes the information to stderr is so you can do: curl <url> | someprgram  without that information clobbering the input of  someprogram It is possible to use  --stderr -  as parameter, to redirect the output from stderr (default) to stdout. With this option you also should use  --silent  to suppress the progress bar. $ curl - v -- silent https :// google . com / -- stderr - | grep expire * expire date : 2015 - 09 - 01 00 : 00 : 00 GMT  

Salt stack issues

The function “state.apply” is running as PID Restart salt-minion with command:  service salt-minion restart No matching sls found for ‘init’ in env ‘base’ Add top.sls file in the directory where your main sls file is present. Create the file as follows: 1 2 3 base: 'web*' : - apache If the sls is present in a subdirectory elasticsearch/init.sls then write the top.sls as: 1 2 3 base: '*' : - elasticsearch.init How to execute saltstack-formulas create file  /srv/pillar/top.sls  with content: base : ' * ' : - salt create file  /srv/pillar/salt.sls  with content: salt : master : worker_threads : 2 fileserver_backend : - roots - git gitfs_remotes : - git://github.com/saltstack-formulas/epel-formula.git - git://github.com/saltstack-formulas/git-formula.git - git://github.com/saltstack-formulas/nano-formula.git - git://github.com/saltstack-f...

Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. Configuration files describe to Terraform the components needed to run a single application or your entire datacenter. Terraform generates an execution plan describing what it will do to reach the desired state, and then executes it to build the described infrastructure. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied. The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS entries, SaaS features, etc. The key features of Terraform are: Infrastructure as Code : Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and...