cannot access .yaml on Ansible Controller

Bug #1834344 reported by Keith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned

Bug Description

I am fairly new to Ansible and would like your help!

I have 4 Debian Certificate files:

- Debian-6-certificates.yaml
- Debian-7-certificates.yaml
- Debian-8-certificates.yaml
- Debian-9-certificates.yaml

They are identical:

---
- name: Copy the proxy CA to /etc/ssl/certs/
  copy:
    src: library/{{ item }}.crt
    dest: /usr/local/share/ca-certificates/{{ item }}.crt
  with_items:
  - "{{ proxy_ca_certificate }}"
- name: Update system CA certificates
  command: update-ca-certificates --fresh
...
 - Debian-7-certificates.yaml
...

They are to be used with deploy-CA-proxy.yaml:

---
- hosts: buildservers
  remote_user: root

  tasks:
  - name: Detect OS and run appropriate tasks
    include_tasks: "{{ ansible_distribution }}-{{ ansible_distribution_major_version }}-certificates.yaml"
...

I want to merge Debian 6/7/8/9 with deploy-CA-proxy.yaml if this is possible. If possible, how do I go about doing it?

Ansible Version:

 ansible --version
ansible 2.8.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/kjames/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Apr 9 2019, 14:30:50) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

Ansible Controller:

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

What I have tried:

---
- hosts: buildservers
  remote_user: root

  tasks:
  - name: Detect OS and run appropriate tasks
    include_tasks: "{{ ansible_distribution }}-{{ ansible_distribution_major_version }}-certificates.yaml"
  - name: Copy the proxy CA to /etc/ssl/certs/
  copy:
    src: library/{{ item }}.crt
    dest: /usr/local/share/ca-certificates/{{ item }}.crt
  with_items:
  - "{{ proxy_ca_certificate }}"
- name: Update system CA certificates
  command: update-ca-certificates --fresh
...

Actual Output:
TASK [Detect OS and run appropriate tasks] ******************************************************************************************************
fatal: [wblrh7ex6402]: FAILED! => {"reason": "Could not find or access '/home/kjames/ds9/RedHat-7-certificates.yaml' on the Ansible Controller."}
fatal: [wbls12ex6401]: FAILED! => {"reason": "Could not find or access '/home/kjames/ds9/SLES-12-certificates.yaml' on the Ansible Controller."}
fatal: [wblu12ex6401]: FAILED! => {"reason": "Could not find or access '/home/kjames/ds9/Ubuntu-12-certificates.yaml' on the Ansible Controller."}
fatal: [wbldeb8ex6402]: FAILED! => {"reason": "Could not find or access '/home/kjames/ds9/Debian-8-certificates.yaml' on the Ansible Controller."}

PLAY RECAP ******************************************************************************************************
wbldeb8ex6402 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
wblrh7ex6402 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
wbls12ex6401 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
wblu12ex6401 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0

"I know I get this FAILURE because I don't havr the individual Debian-6-certificates.yaml, Debian-7-certificates.yaml, Debian-8-certificates.yaml, Debian-9-certificates.yaml on the Ansible Controller. I need to know how to configure the deploy-CA-proxy.yaml correctly with the Debian 6/7/8/9 files so I can have only the one deploy-CA-proxy.yaml."

Revision history for this message
Jonathan Rosser (jrosser) wrote :

This does not seem to be a bug related to openstack-ansible

Changed in openstack-ansible:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.