Bug 1779503 - OSP16 | Legacy Telemetry | Overcloud deployment with legacy telemetry fails because the template is in the wrong place,
Summary: OSP16 | Legacy Telemetry | Overcloud deployment with legacy telemetry fails b...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 16.0 (Train on RHEL 8.1)
Assignee: Ryan McCabe
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 05:39 UTC by Leonid Natapov
Modified: 2020-02-06 14:43 UTC (History)
3 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.3.1-0.20191211120232.5ca908c.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-06 14:43:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 697104 0 'None' MERGED Move the legacy telemetry environment template to correct location 2020-09-30 07:50:20 UTC
Red Hat Product Errata RHEA-2020:0283 0 None None None 2020-02-06 14:43:56 UTC

Description Leonid Natapov 2019-12-04 05:39:34 UTC 
OSP16 | Legacy Telemetry | Overcloud deployment with legacy telemetry fails because the template is in the wrong place. We need to
move the legacy telemetry environment template to correct location

rename from deployment/deprecated/telemetry/enable-legacy-telemetry.yaml
rename to environments/enable-legacy-telemetry.yaml


W/A: Manually move the template to the right place.
Comment 6 Leonid Natapov 2019-12-16 10:51:49 UTC 
Verified. Template is in the environment directory now.
Comment 9 errata-xmlrpc 2020-02-06 14:43:39 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-2020:0283
Note You need to log in before you can comment on or make changes to this bug.