Fuel for OpenStack

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

Bug #1339596 reported by Anastasia Palkina on 2014-07-09

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Fuel for OpenStack	Fix Committed	High	Aleksandr Didenko	Fuel for OpenStack 5.1
	5.0.x	Won't Fix	Medium	Aleksandr Didenko	Fuel for OpenStack 5.0.1

Bug Description

"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'

See original description

Revision history for this message

Anastasia Palkina (apalkina) wrote on 2014-07-09:

fuel-snapshot-2014-07-09_08-45-06.tgz Edit (108.9 MiB, application/x-tar)

description:	updated
summary:	Could not find init script or upstart conf file for 'cinder-scheduler' + and 'cinder-api'

Vladimir Kuklin (vkuklin) on 2014-07-09

Changed in fuel:
assignee:	Fuel Library Team (fuel-library) → Aleksandr Didenko (adidenko)

Revision history for this message

Aleksandr Didenko (adidenko) wrote on 2014-07-09:

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.

Revision history for this message

Aleksandr Didenko (adidenko) wrote on 2014-07-09:

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.

Revision history for this message

Aleksandr Didenko (adidenko) wrote on 2014-07-09:

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.

Dmitry Pyzhov (dpyzhov) on 2014-08-14

no longer affects:

fuel/5.1.x

Aleksandr Didenko (adidenko) on 2014-09-23