lvm is reporting problems, not sending heartbeat. Service will appear "down"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
Pike |
New
|
Undecided
|
Unassigned | ||
openstack-ansible |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Hi,
I have deployed Openstack-ansbile (Pike) in my test environment on Ubuntu 16.
I restarted Controller(it is Deployment node as well) and compute nodes.
After this, i am seeing cinder-volume service being down and lvm is reporting errors on the compute node's cinder logs.
Even "cinder-volumes" virtual group is missing from the vgs output.
On Controller:
---------------
root@ubt-
+------
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------
| cinder-scheduler | infra1-
| cinder-volume | ubuntu-compute1@lvm | nova | enabled | down | 2018-05-
+------
On Compute:
-----------
logs in compute1-cinder.log are as below:
root@ubuntu-
2018-05-18 17:42:43.218 5983 ERROR cinder.service [-] Manager for service cinder-volume ubuntu-compute1@lvm is reporting problems, not sending heartbeat. Service will appear "down".
2018-05-18 17:42:53.219 5983 ERROR cinder.service [-] Manager for service cinder-volume ubuntu-compute1@lvm is reporting problems, not sending heartbeat. Service will appear "down".
2018-05-18 17:43:00.019 5983 WARNING cinder.
2018-05-18 17:43:03.219 5983 ERROR cinder.service [-] Manager for service cinder-volume ubuntu-compute1@lvm is reporting problems, not sending heartbeat. Service will appear "down".
2018-05-18 17:43:13.220 5983 ERROR cinder.service [-] Manager for service cinder-volume ubuntu-compute1@lvm is reporting problems, not sending heartbeat. Service will appear "down".
Can anyone please suggest me a solution for this??
I am very new to Openstack, can anyone please respond in detail steps about this issue?
Regards,
Shivashankar
description: | updated |
Changed in openstack-ansible: | |
status: | New → Incomplete |
Changed in cinder: | |
status: | New → Invalid |
Hey there,
It looks like you're running into an issue which could be a config problem, but also could be a bug. Do you have output of your cinder-volume logs? That would be helpful in determining the issue
Thanks!