Red Hat Bugzilla – Bug 1001161
Installation of ovirt-hosted-engine-setup RPM should not be dependent on vdsm-gluster package.
Last modified: 2015-09-22 09:09 EDT
installation of ovirt-hosted-engine-setup-1.0.0-0.1.beta.el6.noarch.rpm should not be dependent on vdsm-gluster package.
not sure i agree.
hosted engine is dependent on vdsm, which depends on vdsm-gluster.
why would it be any different?
vdsm doesn't depend on vdsm-gluster
so where is this dep coming from?
Currently, in the hosted engine environment, this dependency comes from the hosted engine setup, which should be fixed, as the gluster functionality it needs is part of the regular VDSM core RPMs.
vdsm-gluster RPM contains functionality to create gluster bricks, volumes, etc... but the hosted engine setup doesn't need that.
When bootstraping a host in the engine, the vdsm-gluster package is installed only if this host need to support the gluster service.
This bug is currently attached to errata RHBA-2013:15257. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.