Bug 1476854

Summary: openstack-heat-templates: wrong path in deprecation note
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: openstack-tripleo-heat-templatesAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact: Derek <dcadzow>
Priority: medium    
Version: 12.0 (Pike)CC: apevec, aschultz, jomurphy, lhh, mburns, rhel-osp-director-maint, seb, srevivo, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170821194253.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:45:43 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 Alexander Chuzhoy 2017-07-31 15:28:54 UTC
openstack-heat-templates: wrong path in deprecation note

Environment:
openstack-tripleo-heat-templates-7.0.0-0.20170721174554.el7ost.noarch

The issue:

[root@undercloud-0 ~]# head -n4 /usr/share/openstack-tripleo-heat-templates/environments/puppet-ceph-external.yaml 
# ******************************************************************************
# DEPRECATED: Use tripleo-heat-templates/environments/storage/ceph-external.yaml
# instead.
# ******************************************************************************



The file to use instead doesn't exist (instead of ceph-external.yaml we have external-ceph.yaml):
[root@undercloud-0 ~]# ls /usr/share/openstack-tripleo-heat-templates/environments/storage|grep ceph
enable-ceph.yaml
external-ceph.yaml

Comment 3 Yogev Rabl 2017-11-08 16:25:44 UTC
Verified on openstack-tripleo-heat-templates-7.0.3-0.20171024200823.el7ost.noarch

Comment 6 errata-xmlrpc 2017-12-13 21:45:43 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/RHEA-2017:3462