CentOS/Pike - resolvconf - No file was found when using with_first_found.

Bug #1711349 reported by Jesse Pretorius
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Kevin Carter

Bug Description

Environment:
CentOS Linux release 7.3.1611
OSA integrated repo SHA: b7a0dedbf564b082dbbda2a19c5285dc8807c031 (current head of master)

Failure:
TASK [resolvconf : Gather variables for each operating system] ***************************************************************************************************
Thursday 17 August 2017 10:51:57 +0000 (0:00:00.015) 0:22:00.769 *******
fatal: [aio1_repo_container-a9788d01]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}

This hard stops the build, failing it.

Procedure to replicate:
Build CentOS7 instance with 8 vCPU, 8 GB RAM
cd /opt
git clone https://github.com/openstack/openstack-ansible.git
cd openstack-ansible
export ANSIBLE_ROLE_FETCH_MODE="git-clone"
./scripts/bootstrap-ansible.sh
./scripts/bootstrap-aio.sh
cd playbooks/
openstack-ansible setup-hosts.yml setup-infrastructure.yml setup-openstack.yml

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :
Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

I will try to run Pike on my machine using vagrant, see what it gives.

Changed in openstack-ansible:
assignee: nobody → Jean-Philippe Evrard (jean-philippe-evrard)
assignee: Jean-Philippe Evrard (jean-philippe-evrard) → nobody
Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Triaged with the gate periodic upgrade jobs logs: Confirmed.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → High
Changed in openstack-ansible:
assignee: nobody → Kevin Carter (kevin-carter)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499691

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/499711

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible (stable/pike)

Reviewed: https://review.openstack.org/499711
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=1ec85b293571ffdd3a4805fa9dd4e95eb155b801
Submitter: Jenkins
Branch: stable/pike

commit 1ec85b293571ffdd3a4805fa9dd4e95eb155b801
Author: Jean-Philippe Evrard <email address hidden>
Date: Thu Aug 31 16:34:26 2017 +0000

    Revert "Modify unbound to JIT install clients"

    This reverts commit b3c670faeba53eb00212deb1e197499959c40561.

    Change-Id: I038d6962013536a4724c4c30882d0020fc11f722
    Closes-Bug: #1711349

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible (stable/pike)

Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: stable/pike
Review: https://review.openstack.org/499691

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 16.0.0.0rc2

This issue was fixed in the openstack/openstack-ansible 16.0.0.0rc2 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible (master)

Change abandoned by Kevin Carter (cloudnull) (<email address hidden>) on branch: master
Review: https://review.openstack.org/493739
Reason: a different direction was already applied to the code base.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

I think this issue has now been resolved for both master (Queens) and Pike.

Changed in openstack-ansible:
status: In Progress → Fix Released
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.