designate-manage pool update fails intermittently

[Alex Schultz]

We're seeing intermittent failures with designate-manage pool.

http://logs.openstack.org/11/441911/1/check/gate-puppet-openstack-integration-4-scenario003-tempest-centos-7/66639b0/logs/puppet.txt.gz

It might be because we're attempting to run the update without ensuring the central service is up first.

http://logs.openstack.org/11/441911/1/check/gate-puppet-openstack-integration-4-scenario003-tempest-centos-7/66639b0/logs/designate/designate-manage.txt.gz#_2017-03-08_16_58_23_495

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/443297
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=e5d468a42cda7b477418d78a8b67c5471cc223a1
Submitter: Jenkins
Branch: master

commit e5d468a42cda7b477418d78a8b67c5471cc223a1
Author: Alex Schultz <email address hidden>
Date: Wed Mar 8 12:25:56 2017 -0700

    Actually run service validation for designate

    The service validation for designate-central was set to refreshonly but
    did not have anything actually notifying it to run. This change updates
    the validation to listen for the designate::service::end anchor so that
    we will wait for the service to be up before trying to manage the pools.

    Change-Id: Ife6b29388e97112666ad5602ac62ac7d8534c1d5
    Closes-Bug: #1671206

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/443349

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/443349
Committed: https://git.openstack.org/cgit/openstack/puppet-openstack-integration/commit/?id=9ea4c650e5f656e4f893b1d0370c8ebb5f9b684e
Submitter: Jenkins
Branch: stable/ocata

commit 9ea4c650e5f656e4f893b1d0370c8ebb5f9b684e
Author: Alex Schultz <email address hidden>
Date: Wed Mar 8 12:25:56 2017 -0700

    Actually run service validation for designate

    The service validation for designate-central was set to refreshonly but
    did not have anything actually notifying it to run. This change updates
    the validation to listen for the designate::service::end anchor so that
    we will wait for the service to be up before trying to manage the pools.

    Change-Id: Ife6b29388e97112666ad5602ac62ac7d8534c1d5
    Closes-Bug: #1671206
    (cherry picked from commit e5d468a42cda7b477418d78a8b67c5471cc223a1)