Fuel for OpenStack

[library] Cinder-volume installs on controller node

Bug #1325892 reported by Vladimir Kuklin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Aleksandr Didenko
Fuel for OpenStack 5.1
4.1.x
Won't Fix
Low
Fuel Library (Deprecated)
Fuel for OpenStack 4.1.1-updates
5.0.x
Won't Fix
Low
Fuel Library (Deprecated)
Fuel for OpenStack 5.0.2

Bug Description

{"build_id": "2014-06-03_00-40-36", "mirantis": "yes", "build_number": "338", "nailgun_sha": "a828d6b7610f872980d5a2113774f1cda6f6810b", "ostf_sha": "c959aa55f83fe2555cf2d382559271c7a9b17467", "fuelmain_sha": "15805b14f36fc0a896f136051a3be10fea4611d9", "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968", "release": "4.1B", "fuellib_sha": "377f27df4cb008b400b69013dbd606e6225f5c04"}

Deploy Ubuntu + nova-network+cinder node. Controller gets cinder-volume service started, which should not happen.

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

The real problem is that cinder-volume service running on a controller node without cinder VG still gets scheduled by cinder-scheduler, which causes volume creation to fail. Making sure cinder-volume is stopped on controllers is a band-aid around that Cinder bug.

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/5.1.x
Dmitry Ilyin (idv1985)
summary: - Cinder-volume installs on controller node
+ [library] Cinder-volume installs on controller node
Vladimir Kuklin (vkuklin)
Changed in fuel:
importance: Low → High
assignee: Fuel Library Team (fuel-library) → Aleksandr Didenko (adidenko)
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

Tested on ISO 5.1 #320:

1) Ubuntu, simple flat, 2 nodes: controller + compute
There are no cinder-volume packages or processes on nodes.

2) Ubuntu, simple flat, 3 nodes: controller + compute + cinder
cinder-volume is installed and running on cinder node only.

Controller node processes:
/usr/bin/python /usr/bin/cinder-scheduler --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-scheduler.log
/usr/bin/python /usr/bin/cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-api.log

Cinder node processes:
/usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log

Controller packages:
cinder-api
cinder-common
cinder-scheduler
python-cinder
python-cinderclient

Cinder node packages:
cinder-common
cinder-volume
python-cinder

So there is no such problem in the current master branch.

Changed in fuel:
status: Triaged → Invalid
Revision history for this message
Andrew Woodward (xarses) wrote :

We won't be fixing low or medium bugs for 4.1.x or 5.0.x any longer. If this needs to be addressed we need to increase priority

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.