Description of problem: engine-setup can download missing packages. so i was expecting to: 1. install ovirt-engine-setup-base (as it contains engine-setup) 2. engine-setup (to do all work for me) but... # engine-setup ***L:ERROR Internal error: No module named engine_common thus ovirt-engine-setup-base should require ovirt-engine-setup-plugin-ovirt-engine-common why did i not install ovirt-engine? i just need to setup websocket proxy on different host than where engine is running. so i don't see sense to have jboss/java on this machine. hmmmm... current deps are just opposite: # rpm -qR ovirt-engine-setup-plugin-ovirt-engine-common cracklib-python libselinux-python m2crypto nfs-utils ovirt-engine-setup-base = 3.5.0-0.0.master.20140629172257.git0b16ed7.el6 policycoreutils-python python-psycopg2 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 yum rpmlib(PayloadIsXz) <= 5.2-1 i don't know if this is OK. i think most people would attempt to do it my way: 1. yum provides '*/engine-setup' 2. yum install $rpm # rpm -qR ovirt-engine-setup-base /bin/sh /bin/sh bind-utils config(ovirt-engine-setup-base) = 3.5.0-0.0.master.20140629172257.git0b16ed7.el6 iproute libxml2-python logrotate otopi >= 1.2.0-1 ovirt-engine-lib >= 3.5.0-0.0.master.20140629172257.git0b16ed7.el6 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 for me engine-setup is the boss here and should depend on its servants. Version-Release number of selected component (if applicable): ovirt-engine-setup-base-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch How reproducible: 100% Steps to Reproduce: 1. yum install ovirt-engine-setup-base 2. engine-setup 3. Actual results: oops Expected results: should at least work Additional info:
*** This bug has been marked as a duplicate of bug 1114978 ***