Bug 1533468

Summary: capabilities-map.yaml references wrong environment files for ceph services
Product: Red Hat OpenStack Reporter: jliberma <jliberma>
Component: openstack-tripleo-heat-templatesAssignee: Giulio Fidente <gfidente>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: aschultz, gfidente, jomurphy, jschluet, mburns, rhel-osp-director-maint
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.9-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-28 17:16:42 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:
Embargoed:

Description jliberma@redhat.com 2018-01-11 12:38:21 UTC 
Description of problem:

With OSP 12 Ceph is installed via ceph-ansible templates in environments/ceph-ansible.

capabilities-map.yaml references the legacy templates in puppet/services

Version-Release number of selected component (if applicable):

openstack-tripleo-heat-templates-7.0.3-18.el7ost.noarch

How reproducible:

$ grep -r ceph-radosgw.yaml *
capabilities-map.yaml:          - file: environments/ceph-radosgw.yaml

$ cat environments/ceph-radosgw.yaml 
resource_registry:
  OS::TripleO::Services::CephRgw: ../puppet/services/ceph-rgw.yaml
  OS::TripleO::Services::SwiftProxy: OS::Heat::None
  OS::TripleO::Services::SwiftStorage: OS::Heat::None
  OS::TripleO::Services::SwiftRingBuilder: OS::Heat::None

$ ls docker/services/ceph-ansible/ceph-rgw.yaml
docker/services/ceph-ansible/ceph-rgw.yaml


Additional info: The capabilities map should be pointed to the docker template in Pike.
Comment 5 Yogev Rabl 2018-03-16 14:40:25 UTC 
Verified on openstack-tripleo-heat-templates-7.0.9-6.el7ost.noarch
Comment 8 errata-xmlrpc 2018-03-28 17:16:42 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.

https://access.redhat.com/errata/RHSA-2018:0602