Deployment additional nodes to updated 9.1 cluster failed due to "(/Stage[main]/Osnailyfacter::Upgrade::Pkg_upgrade/Service[pacemaker]) Could not evaluate: Could not find init script or upstart conf file for 'pacemaker'"

[Artem Hrechanychenko]

Detailed bug description:
    "Success
Provision of 4 environment node(s) is done.
Deployment is done. No changes.
    Stopped 5 nodes
    Your deployment was unsuccessful."

Steps to reproduce:
1) Deploy any 9.0 cluster
2) configure additional yum repo:http://mirror.fuel-infra.org/mos-repos/centos/mos9.0-centos7/snapshots/proposed-2016-09-07-044322/x86_64/
3)yum install -y python-cudet
4)Prepare Master node:
  #update-prepare prepare master
5) #update-prepare prepare env 1
6) add additional deb repo to cluster "deb http://mirror.fuel-infra.org/mos-repos/ubuntu/snapshots/9.0-2016-09-06-192322/ mos9.0-proposed main restricted" with prio = 1200
8) fuel2 update --env 1 install --restart-rabbitmq --restart-mysql
9) verify networks
10) run ostf
11) add Add to existing cluster 2 controllers and 1 compute+cinder nodes
12) verify networks
13) deploy changes

Expected results:
Deployment successfully

Actual results:
(/Stage[main]/Osnailyfacter::Upgrade::Pkg_upgrade/Service[pacemaker]) Could not evaluate: Could not find init script or upstart conf file for 'pacemaker'

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/367850

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/362239
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=52aa94c173c0c8497ef889ac1587bc66e6abdca4
Submitter: Jenkins
Branch: master

commit 52aa94c173c0c8497ef889ac1587bc66e6abdca4
Author: dmburmistrov <email address hidden>
Date: Mon Aug 29 18:59:11 2016 +0300

    Use "safe" mirror list on upgrade

    All "safe" repos for using in upgrade will be configured in UI and
    available in Hiera. Then this list will be used to link this mirrors
    to separate "sources.d" directory. This directory will be used to point
    APT another source location. That allows us to get list of packages, which
    will be upgraded with specified in "sources.d" mirrors. Then, available
    packages will be upgraded.

    To keep this process configurable we can specify hash of packages, which
    should be upgraded throw hiera.

    DocImpact

    Closes-bug: #1616553
    Closes-bug: #1621056

    Change-Id: Idf4ff71c04f8a75c572bb24e560b3827f3d55bac

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/367850
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c4ea02a3cd32a0dd8e1ba1db36b81ea89717d02a
Submitter: Jenkins
Branch: stable/mitaka

commit c4ea02a3cd32a0dd8e1ba1db36b81ea89717d02a
Author: dmburmistrov <email address hidden>
Date: Mon Aug 29 18:59:11 2016 +0300

    Use "safe" mirror list on upgrade

    All "safe" repos for using in upgrade will be configured in UI and
    available in Hiera. Then this list will be used to link this mirrors
    to separate "sources.d" directory. This directory will be used to point
    APT another source location. That allows us to get list of packages, which
    will be upgraded with specified in "sources.d" mirrors. Then, available
    packages will be upgraded.

    To keep this process configurable we can specify hash of packages, which
    should be upgraded throw hiera.

    DocImpact

    Closes-bug: #1616553
    Closes-bug: #1621056

    Change-Id: Idf4ff71c04f8a75c572bb24e560b3827f3d55bac

[TatyanaGladysheva (tgladysheva)]

Verified on 9.1 snapshot #270.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-library 10.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-library 10.0.0 release.