Bug 1500844 - [RFE] Update process to trigger ceph-ansible to accommodate change in Heat's role in OSPd
Summary: [RFE] Update process to trigger ceph-ansible to accommodate change in Heat's...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M1
: 14.0 (Rocky)
Assignee: Giulio Fidente
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On: 1476904
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-11 15:11 UTC by John Fulton
Modified: 2019-01-11 11:48 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180710202746.d2994ca.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:48:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 546966 0 None None None 2018-02-28 10:49:24 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:48:38 UTC

Description John Fulton 2017-10-11 15:11:49 UTC
As per BZ 1476904 [1] Heat's role in OSPd may change. If so, rather than trigger ceph-ansible using Heat > Mistral > Ansible, it could be triggered by Ansible directly. When this happens in OSPd overall, the Ceph integration team will have to adjust their integration of ceph-ansible with OSPd.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1476904

Comment 2 Red Hat Bugzilla Rules Engine 2017-10-13 12:39:54 UTC
This bugzilla has been removed from the release and needs to be reviewed for Triaging and release planning for an appropriate Target Milestone.

Comment 8 Giulio Fidente 2018-05-03 09:44:41 UTC
Support for NodeDataLookup seems to be the last remaining functionality to migrate.

Comment 10 Yogev Rabl 2018-11-13 19:43:07 UTC
Verified

Comment 14 errata-xmlrpc 2019-01-11 11:48:07 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-2019:0045


Note You need to log in before you can comment on or make changes to this bug.