Red Hat Bugzilla – Bug 977594
Customer can never install foreman-libvirt off of ISO because installer script removes repofile
Last modified: 2014-04-24 13:10:57 EDT
Description of problem:
Users who install from ISO will not, without workaround, be able to install foreman-libvirt package from ISO, because the installer script, after initially configuring repo file, removes it after install is completed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download ISO and mount it.
2. Execute install_packages from iso
3. Noting that installer does not actually install foreman-libvirt, manually attempt to install it.
4. Look for repo file in /etc/yum.repos.d/ and/or examine installer script itself.
No package foreman-libvirt found
Observe that installer script removes repo file.
User can at least manually install foreman-libvirt metapackage separate from main installer.
cd <ISO mount dir>/Packages
rpm -Uvh foreman-libvirt-*.rpm
foreman-libvirt has dependencies, so yum might be the better route. That said, I still had some minor dependency issues installing foreman-libvirt, even though everything was there. I think the recommended route is creating a localrepo, but I guess it's not /too/ hard to identify all the necessary files...
yum localinstall foreman-libvirt-1.1.10014-1.noarch.rpm foreman-1.1.10014-1.noarch.rpm foreman-compute-1.1.10014-1.noarch.rpm
I'm not even sure what the correct fix for this would be? The solutions i can currently think of:
a) Install foreman-libvirt as part of katello-foreman-all
b) Assume the user will leave the ISO mounted, and leave the repo file in place.
c) have some script that will install a package from the iso (i.e. ./iso-install foreman-libvirt)
We could do (2), but leave the repo disabled by default so it doesn't interfere when the ISO's removed? Users could then do "yum --enablerepo=satellite6 install foreman-libvirt".
The other thing to consider is that we plan on having better support in the installer for plugins etc, so it might also be possible to re-run a part of the installer, which could re-enable the repo.
I dislike (1) because there are a number of pieces of optional functionality. Always installing them on non-ISO installs via katello-foreman-all I think is over the top and will add many more packages.
yeah, agree on you 100% with a). Leaving the repo file there but disabled is not a bad idea, i wonder what the likelihood of the user mounting it to a different location is though
instead of mounting why don't we just copy the repo to something like /var/satellite/installer-repo and reference that instead of mounted directly. The repo isn't *that* big is it?
chose /opt/satellite as the destination, since these files are not tracked by the package manager
This was verified and delivered with MDP2. Closing it out.
This was delivered and verified with MDP2. Closing the bug.