Bug 916808

Summary: Add Server VDSM not running after reboot - server in Not Responsive state
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Matt Mahoney <mmahoney>
Component: rhscAssignee: Bala.FA <barumuga>
Status: CLOSED NOTABUG QA Contact: Matt Mahoney <mmahoney>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, sabose, ssampat
Target Milestone: ---   
Target Release: RHGS 2.1.2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-28 14:45:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Console engine logs & server sosreport none

Description Matt Mahoney 2013-03-01 00:52:02 UTC 
Created attachment 704042 [details]
Console engine logs & server sosreport

Description of problem:

The symptoms of this issue appear to be the same as bug:

https://bugzilla.redhat.com/show_bug.cgi?id=878327

Version-Release number of selected component (if applicable):

QA6 build

How reproducible:


Steps to Reproduce:
1. Create RHS M with RHS-2.0-20130219.3
2. Add new server via Console
3.
  
Actual results:
Add server results in Not Responsive, vdsm not running on RHS node.

Expected results:
VDSM should be running after reboot due to Server Add.

Additional info:
Comment 2 Shireesh 2013-03-01 05:39:54 UTC 
What is the version of libvirt installed on the node?
Comment 3 Bala.FA 2013-03-01 06:27:50 UTC 
I am not able to find useful information in the attachment.  Please add the followings from the node

1. console output 'service vdsmd restart'
2. bootstrap logs from /tmp/*.log
Comment 4 Bala.FA 2013-03-06 12:36:33 UTC 
Could you tell me /var/log/vdsm directory ownership to vdsm:kvm or not?
Comment 5 Matt Mahoney 2013-03-07 16:25:08 UTC 
Yes, ownership is set to vdsm:kvm.
Comment 7 Matt Mahoney 2013-03-28 14:45:57 UTC 
The VM has long been deleted, and this issues has not again been encountered in later builds. Marking to Closed, and will reopen if issue happens again.