Could not find init script or upstart conf file for 'cinder-scheduler' and 'cinder-api'

[Anastasia Palkina]

"build_id": "2014-07-08_13-57-45",
"mirantis": "yes",
"build_number": "107",
"ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
"nailgun_sha": "c0082e3a0e8544bad7bd45c15c5dd8632ea045b5",
"production": "docker",
"api": "1.0", "fuelmain_sha": "b0f5151d12751b9b55dcd69bd1445d0d480012d6",
"astute_sha": "a4edb51661f50c66e247e0b8d00f2d01e0658fe6",
"release": "5.0.1",
"fuellib_sha": "d4cb36208efaf51a7c0ca012fa63d596d4ee2e29"

1. Create new environment (Ubuntu, HA mode)
2. Choose Nova network, vlan manager
3. Choose Ceph for images
4. Choose Ceilometer
5. Add 3 controller+mongo, compute, cinder, 2 ceph
6. Start deployment. It was successful
7. But there is error on second controller (node-16) in puppet.log:

2014-07-08 15:51:29 ERR

 (/Stage[main]/Cinder::Scheduler/Service[cinder-scheduler]) Failed to call refresh: Could not find init script or upstart conf file for 'cinder-scheduler'

2014-07-08 15:52:42 ERR

 (/Stage[main]/Cinder::Api/Service[cinder-api]) Failed to call refresh: Could not find init script or upstart conf file for 'cinder-api'

[Aleksandr Didenko (adidenko)]

Here is the original problem:

2014-07-08T15:47:13.935362+00:00 err: Could not start Service[rabbitmq-server]: Execution of '/etc/init.d/rabbitmq-server start' returned 2:

Due to this "cinder-scheduler" package was not even installed:

2014-07-08T15:47:21.316247+00:00 notice: (/Stage[main]/Cinder::Scheduler/Package[cinder-scheduler]) Dependency Service[rabbitmq-server] has failures: true
2014-07-08T15:47:21.317719+00:00 warning: (/Stage[main]/Cinder::Scheduler/Package[cinder-scheduler]) Skipping because of failed dependencies

Checking into logs further to see why rabbitmq start failed.

[Aleksandr Didenko (adidenko)]

Records from rabbitmq-startup_err.log:

2014-07-08T15:47:09.723829+00:00 err:
2014-07-08T15:47:09.723829+00:00 err: Crash dump was written to: erl_crash.dump
2014-07-08T15:47:09.723829+00:00 err: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

So it looks like rabbitmq crashed during start for some reason.

[Aleksandr Didenko (adidenko)]

Should be fixed with rabbitmq OCF in master branch (5.1). Not going to be fixed in 5.0 since we're not planning to change the way we start rabbitmq. Lowering priorinty since it's rather rare issue when rabbit crashed like that during service start.