Bug 1536655

Summary: Could not fetch contents for ... docker/services/ceph-ansible/ceph-mgr.yaml when deploying rhcs3
Product: Red Hat OpenStack Reporter: John Fulton <johfulto>
Component: openstack-tripleo-heat-templatesAssignee: John Fulton <johfulto>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: high Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: gfidente, jomurphy, jschluet, mburns, rhel-osp-director-maint, scohen
Target Milestone: betaKeywords: AutomationBlocker, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180122224016.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:42:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description John Fulton 2018-01-19 20:42:29 UTC
During deployment w/ ceph using storage-environment.yaml, the following error causes the deployment to fail: 

Waiting for messages on queue 'tripleo' with no timeout.
Could not fetch contents for file:///tmp/tripleoclient-PlqIP9/docker/services/ceph-ansible/ceph-mgr.yaml
Started Mistral Workflow tripleo.validations.v1.check_pre_deployment_validations. Execution ID: ec59185c-d99a-4cf6-95ee-b66c7b789f3c
Removing the current plan files
Uploading new plan files
Started Mistral Workflow tripleo.plan_management.v1.update_deployment_plan. Execution ID: 514545e5-717f-4d32-9453-d201067b90a9
Plan updated.
Processing templates in the directory /tmp/tripleoclient-PlqIP9/tripleo-heat-templates

Comment 6 Yogev Rabl 2018-05-16 14:13:23 UTC
verified on openstack-tripleo-heat-templates-8.0.2-17.el7ost.noarch

Comment 8 errata-xmlrpc 2018-06-27 13:42:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.