group: os-apply-config hook scripts are logged as missing

[Dan Prince]

In TripleO the legacy group: os-apply-config has been used in the past for a variety of software deployments to provide configuration metadata. This worked because os-apply-config was executed during each iteration of os-refresh-config.

The 55-heat-config script identifies these groups as an ERROR message however even though they functionally work fine. This can be confusing to the end users who misidentify this as the actual cause of deployment failures.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/501456
Committed: https://git.openstack.org/cgit/openstack/heat-agents/commit/?id=1179f411deffdb7316ad16cd56ef2ae2595d116a
Submitter: Jenkins
Branch: master

commit 1179f411deffdb7316ad16cd56ef2ae2595d116a
Author: Dan Prince <email address hidden>
Date: Wed Sep 6 17:30:01 2017 -0400

    whitelist os-apply-config group in 55-heat-config

    This patch whitelists the os-apply-config 'group' from getting logged
    as an error message because there is no hook script. This is a legacy
    group used in TripleO for several things.

    Change-Id: If128d8e707548815defc72212c59ad53348b5adf
    Closes-bug: #1715497

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat-agents 1.5.0 release.