Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 977594 - Customer can never install foreman-libvirt off of ISO because installer script removes repofile
Summary: Customer can never install foreman-libvirt off of ISO because installer scrip...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 01:15 UTC by Corey Welton
Modified: 2019-09-26 15:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-24 17:09:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Corey Welton 2013-06-25 01:15:18 UTC 
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):


How reproducible:


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.

Actual results:

No package foreman-libvirt found
Observe that installer script removes repo file.

Expected results:
User can at least manually install foreman-libvirt metapackage separate from main installer.

Additional info:
Comment 3 Mike McCune 2013-06-25 01:55:54 UTC 
WORKAROUND:

cd <ISO mount dir>/Packages
rpm -Uvh foreman-libvirt-*.rpm
Comment 4 Corey Welton 2013-06-25 14:10:42 UTC 
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...

e.g.: 

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
Comment 6 Justin Sherrill 2013-10-15 13:30:44 UTC 
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)

Thoughts?
Comment 7 Dominic Cleal 2013-10-15 14:26:28 UTC 
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.
Comment 8 Justin Sherrill 2013-10-15 15:01:46 UTC 
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
Comment 9 Mike McCune 2013-10-16 21:09:40 UTC 
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?
Comment 10 Justin Sherrill 2013-10-23 15:20:12 UTC 
https://github.com/Katello/katello-misc/pull/20

chose /opt/satellite as the destination, since these files are not tracked by the package manager
Comment 13 Og Maciel 2013-10-25 19:21:21 UTC 
* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.8.25-1.el6sam.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.8.25-1.el6sam.noarch
* candlepin-tomcat6-0.8.25-1.el6sam.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* foreman-1.3.0-20.el6sat.noarch
* foreman-postgresql-1.3.0-20.el6sat.noarch
* katello-1.4.6-49.el6sat.noarch
* katello-all-1.4.6-49.el6sat.noarch
* katello-certs-tools-1.4.4-1.el6sat.noarch
* katello-cli-1.4.3-27.el6sat.noarch
* katello-cli-common-1.4.3-27.el6sat.noarch
* katello-common-1.4.6-49.el6sat.noarch
* katello-configure-1.4.7-7.el6sat.noarch
* katello-configure-foreman-1.4.7-7.el6sat.noarch
* katello-foreman-all-1.4.6-49.el6sat.noarch
* katello-glue-candlepin-1.4.6-49.el6sat.noarch
* katello-glue-elasticsearch-1.4.6-49.el6sat.noarch
* katello-glue-pulp-1.4.6-49.el6sat.noarch
* katello-selinux-1.4.4-4.el6sat.noarch
* openldap-2.4.23-31.el6.x86_64
* pulp-katello-plugins-0.2-1.el6sat.noarch
* pulp-nodes-common-2.3.0-0.24.beta.el6sat.noarch
* pulp-nodes-parent-2.3.0-0.24.beta.el6sat.noarch
* pulp-puppet-plugins-2.3.0-0.24.beta.el6sat.noarch
* pulp-rpm-plugins-2.3.0-0.24.beta.el6sat.noarch
* pulp-selinux-2.3.0-0.24.beta.el6sat.noarch
* pulp-server-2.3.0-0.24.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.0.7-1.el6sat.noarch
* signo-0.0.23-2.el6sat.noarch
* signo-katello-0.0.23-2.el6sat.noarch
Comment 14 Bryan Kearney 2014-04-24 17:09:27 UTC 
This was verified and delivered with MDP2. Closing it out.
Comment 15 Bryan Kearney 2014-04-24 17:10:57 UTC 
This was delivered and verified with MDP2. Closing the bug.
Note You need to log in before you can comment on or make changes to this bug.