scenario jobs in stable/queens are broken with ansible file issues: could not locate file in lookup: Controller/step_config.pp

Bug #1784078 reported by Alex Schultz
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

Likely related to https://review.openstack.org/#/c/582429/

http://logs.openstack.org/24/567224/70/check/tripleo-ci-centos-7-scenario001-multinode-oooq-container/d262838/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz#_2018-07-27_19_21_31

2018-07-27 19:21:31 | overcloud.AllNodesDeploySteps.ControllerDeployment_Step1.0:
2018-07-27 19:21:31 | resource_type: OS::Heat::StructuredDeployment
2018-07-27 19:21:31 | physical_resource_id: a50eda30-9517-49b6-be6b-24f3f4d42773
2018-07-27 19:21:31 | status: CREATE_FAILED
2018-07-27 19:21:31 | status_reason: |
2018-07-27 19:21:31 | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with nonHeat Stack create failed.
2018-07-27 19:21:31 | Heat Stack create failed.
2018-07-27 19:21:31 | -zero status code: 2
2018-07-27 19:21:31 | deploy_stdout: |
2018-07-27 19:21:31 | ...
2018-07-27 19:21:31 | TASK [Create /var/lib/tripleo-config directory] ********************************
2018-07-27 19:21:31 | changed: [localhost]
2018-07-27 19:21:31 |
2018-07-27 19:21:31 | TASK [Write the puppet step_config manifest] ***********************************
2018-07-27 19:21:31 | fatal: [localhost]: FAILED! => {"failed": true, "msg": "An unhandled exception occurred while running the lookup plugin 'file'. Error was a <class 'ansible.errors.AnsibleError'>, original message: could not locate file in lookup: Controller/step_config.pp"}
2018-07-27 19:21:31 | to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/048659c6-5821-4407-be10-3fa21ea71d1f_playbook.retry
2018-07-27 19:21:31 |
2018-07-27 19:21:31 | PLAY RECAP *********************************************************************
2018-07-27 19:21:31 | localhost : ok=2 changed=1 unreachable=0 failed=1
2018-07-27 19:21:31 |
2018-07-27 19:21:31 | (truncated, view all with --long)
2018-07-27 19:21:31 | deploy_stderr: |
2018-07-27 19:21:31 | [WARNING]: Unable to find 'Controller/step_config.pp' in expected paths.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/586714

summary: - scenario jobs in stable/queens are broken with ansible file issues
+ scenario jobs in stable/queens are broken with ansible file issues:
+ could not locate file in lookup: Controller/step_config.pp
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/queens)

Reviewed: https://review.openstack.org/586714
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d3c791e8f7ca84ce7d96e7cdddc43b976dc44e3a
Submitter: Zuul
Branch: stable/queens

commit d3c791e8f7ca84ce7d96e7cdddc43b976dc44e3a
Author: Alex Schultz <email address hidden>
Date: Fri Jul 27 21:48:01 2018 +0000

    Revert "Optimized Ansible tasks in deplay-steps-tasks.yaml"

    This reverts commit b8065e6709766a681d9988fff6894360b3c47052.

    This appears to have broken all the scenarios.

    Change-Id: I158de05fdc4874c579c97c82f820641061b426c6
    Closes-Bug: #1784078

tags: added: in-stable-queens
Revision history for this message
wes hayutin (weshayutin) wrote :

Looks fixed as scenario001 is working in the latest no-op checks
https://review.openstack.org/#/c/567224

Revision history for this message
wes hayutin (weshayutin) wrote :
Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
wes hayutin (weshayutin) wrote :

Job is at 87% pass rate in check.. pretty good for check
100% pass rate in gate

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 8.0.5

This issue was fixed in the openstack/tripleo-heat-templates 8.0.5 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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