Bug 829312 - VDSM: vdsm RPM should have dependency on vdsm-gluster RPM
Summary: VDSM: vdsm RPM should have dependency on vdsm-gluster RPM
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Shireesh
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-06 12:54 UTC by Daniel Paikov
Modified: 2013-07-04 07:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-10 06:12:23 UTC
Embargoed:

Attachments (Terms of Use)

Description Daniel Paikov 2012-06-06 12:54:53 UTC 
vdsm RPM should have dependency on vdsm-gluster RPM. Otherwise "service vdsmd start" fails.
Comment 2 Bala.FA 2012-06-08 05:43:16 UTC 
In theory it should not fail to start without vdsm-gluster rpm.  Could you send me vdsm.log on failure?
Comment 3 Bala.FA 2012-06-08 10:27:22 UTC 
You can also give me 'service vdsmd start' output on failure.
Comment 4 Bala.FA 2012-06-08 10:43:46 UTC 
vdsm without gluster rpm works fine for me.  Please add 'rpm -qa | grep vdsm' output here.

Well.  If I add vdsm-gluster dep to vdsm, it will be cyclic dependency.  Either we remove vdsm dependency to vdsm-gluster and add vdsm-gluster dependency to vdsm or leave to the current behaviour ie vdsm-gluster depends on vdsm and you should explicitly install vdsm-gluster by hand.
Comment 5 Shireesh 2012-06-08 12:51:55 UTC 
I think it is ok for user to install vdsm-gluster manually in case of upstream. In downstream, all required packages (including vdsm-gluster) will be installed by default in the RHS2.0 servers, so we will not have any issues. (This is still in the works, and should be available very soon in RHS2.0)

Daniel, if you are not able to start vdsmd because of the dependency issue, please provide details requested by Bala.
Comment 6 Daniel Paikov 2012-06-10 06:12:23 UTC 
I think I had a different problem that prevented me from running vdsmd. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.