Endpoint orchestration-api-cfn not registered

[Richard Theis]

The fix for bug 1279577 now results in the orchestration-api-cfn endpoint not getting registered when openstack-orchestration::api-cfn is in a node's expanded run list (via os-orchestration role).

It may be preferred to model api registration similar to that provided by node['openstack']['compute']['enabled_apis'] instead of relying on run list expansion which may not be sufficient if the openstack-orchestration::api-cfn recipe is included via another recipe.

MRV - I created blueprint https://blueprints.launchpad.net/openstack-chef/+spec/identity-registration-cleanup to cover future changes for this.

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: master
Review: https://review.openstack.org/89410

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/89410
Committed: https://git.openstack.org/cgit/stackforge/cookbook-openstack-orchestration/commit/?id=63914207bfee3f397409c635a2eab5efb93837f2
Submitter: Jenkins
Branch: master

commit 63914207bfee3f397409c635a2eab5efb93837f2
Author: Mark Vanderwiel <email address hidden>
Date: Mon Apr 21 14:58:31 2014 -0500

    Revert bug fix 1279577

    https://review.openstack.org/73108
    The original change does not work for the case where the api-cfn recipe
    is included from within another recipe.
    This revert does not cause any harm, it justs registers
    api-cfn with identity unnecessarily.
    The real solution is probably a refactoring of the common identity recipe.
    Created blueprint identity-registration-cleanup for this future work.

    Change-Id: I43646182a7465cdddd55b1f840764ba1b147451e
    Closes-Bug: #1309123

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cookbook-openstack-orchestration ocata-eol release.