Pacemaker isn't used in Packstack, so moving it to openstack-puppet-modules.

*** Bug 1031797 has been marked as a duplicate of this bug. ***

But it _is_ used by foreman, so it is needed in packstack-modules-puppet.  We use that rpm for our puppet dependencies just like packstack does

Moving bug to the correct component doesn't mean we won't add it to packstack submodule set, since it is source for openstack-puppet-modules.

Adding OtherQA for bugs in MODIFIED

I verified that this matches expected:

[root@localhost ~]# rpm -ql openstack-packstack | grep pacemaker | grep filesystem
/usr/lib/python2.6/site-packages/packstack/puppet/modules/pacemaker/manifests/resource/filesystem.pp
[root@localhost ~]# cat /usr/lib/python2.6/site-packages/packstack/puppet/modules/pacemaker/manifests/resource/filesystem.pp
class pacemaker::resource::filesystem($device,
                                      $directory,
                                      $fstype,
                                      $group='',
                                      $interval="30s",
                                      $ensure=present) {
  $resource_id = delete("fs-${directory}", '/')
  pacemaker::resource::base { $resource_id:
    resource_type   => "Filesystem",
    resource_params => "device=${device} directory=${directory} fstype=${fstype}",
    group           => $group,
    interval        => "30s",
    ensure          => $ensure,
  }
}

openstack-packstack-2013.1.1-0.37.dev705.el6ost.noarch

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html