panko: Do db_sync in api manifest
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Fri, 10 Mar 2017 09:44:56 +0000 (11:44 +0200)
committerEmilien Macchi <emilien@redhat.com>
Tue, 21 Mar 2017 13:55:47 +0000 (13:55 +0000)
commitd71efd8a8f2284be9c24ec5b6e5a12f067e5d706
treed3a5a0a7ff63b837076c16c0917c5c571d2b8325
parentcf77c118d7b107121aaa5f4b08177d0a47f4b69f
panko: Do db_sync in api manifest

The db_sync from panko comes from the panko-api package; So we move the
db_sync to be done in the api manifest as it's done for other services
such as barbican.

This is necessary since in cases where the overcloud deploy requires
puppet to do the installations, with the previous setup it failed since
the command wasn't available in the step it was being done.

Change-Id: I20a549cbaa2ee4b2c762dbae97f5cbf4d0b517c8
Closes-Bug: #1671716
(cherry picked from commit d73c2630b534b277122db68620be8923c4d3a6b4)
manifests/profile/base/panko.pp
manifests/profile/base/panko/api.pp