subscription to policy:table init to empty

[Eric K]

Subscription to an existing policy:table incorrectly initiates the content to empty. Recovers after next periodic sync, but gives incorrect results in the mean time.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/436259

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/436259
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=2d07e9297e414a754ed82c81c92f248e584b20ae
Submitter: Jenkins
Branch: stable/newton

commit 2d07e9297e414a754ed82c81c92f248e584b20ae
Author: Eric K <email address hidden>
Date: Wed Feb 1 14:11:44 2017 -0800

    Do not init data on subscribe for unresponsive service

    The initializing to empty causes agnostic to delete policy facts
    when the service is a regular policy. This change forgoes the
    initialization. Does not affect evaluation because when there is no
    data, evaluation defaults to False/empty.

    Closes-Bug: 1666325
    Change-Id: I879b73eab8a6a083a9fb47bef09abe5ee398f949
    (cherry picked from commit 03c9dddec5be22f88effa25d8ce0001f63907e3f)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/congress 4.0.1 release.