Fix rspecs for custom pacemaker providers

[Bogdan Dobrelya]

The change https://review.openstack.org/#/c/148930 put Fuel custom providers for pacemaker as a separate pacemaker module.
The tests for it providers should be fixed as well. Once its done, we should enable them in fuel rspecs.

[Dmitry Ilyin (idv1985)]

New providers are ready and are on the review. We have postponed their merge to the 6.1.1

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/238885

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dmitry Ilyin (<email address hidden>) on branch: master
Review: https://review.openstack.org/238885

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/224857
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=2f2239025ac0d0893470a309b9e03c884fb0da89
Submitter: Jenkins
Branch: master

commit 2f2239025ac0d0893470a309b9e03c884fb0da89
Author: Vladimir Kuklin <email address hidden>
Date: Mon Feb 29 16:53:55 2016 +0300

    Refactor to pcmk_ resources

    Use pcmk_* resources from the new pacemaker module
    instead of the old cs_* resources from the upstream
    corosync modules and custom cs_rsc_* resources from the
    duct tape patched corosync module.

    The new pacemaker module is rewritten from the scratch
    and provides improved performance, transparency and
    debuggability. It uses it's own XML engine and depends
    neither on "pcs" nor on "crm" applications.

    "corosync" modules will still be used to install the
    corosync cluster, and the "pacemaker" modules will
    be used to work with the cluster's configuration.

    Refactor pacemaker services to use pacemaker::service
    wrapper. It controlls primitive creation and run in the
    uniform way and creates ocf_handler helpers for
    manual primitive management.

    Add run_failed_log feature to fuel_noop_tests to
    replay the failed tests after they were fixed.

    Change-Id: Ifd5813c657031cdd7b86368cd971742483a5b8a1
    Related-Bug: 1414583
    Related-Bug: 1453773
    Related-Bug: 1482248

[Timur Nurlygayanov (tnurlygayanov)]

Ok, the issue was fixed, marked as Fix Released.
Please reopen the issue if it wasn't completely fixed or if it will be reproduced again.