Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Capsule install fails (again) when using only required repos.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150311.1
How reproducible:
Steps to Reproduce:
1. Register client and subscribe it to (x)Server, Sat-common and Sat-capsule repos
2. Attempt to install capsule using only these repos.
3. View results.
Actual results:
[root@cloud-qe-3 ~]# yum repolist
Loaded plugins: package_upload, product-id, subscription-manager
repo id repo name status
!Default_Organization_Sat6_-_Capsule_Capsule_-_RHEL7 Capsule - RHEL7 116
!Default_Organization_Sat6_-_Common_Common_-_RHEL7 Common - RHEL7 53
rhel-7-server-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server (RPMs) 6,674
[root@cloud-qe-3 ~]# capsule-installer --parent-fqdn "rhsm-qe-2.rhq.lab.eng.bos.redhat.com" --register-in-foreman "true" --foreman-oauth-key "qpcfyaEKGVXi4xizKZz68k8jTfh4ijbE" --foreman-oauth-secret "Hebf8gVqzH73DqokbzJnMWAVc6Qa5EGy" --pulp-oauth-secret "o2QYsWFB2PHY9nAV96mUtMKruXn626Zq" --certs-tar "cloud-qe-3.idmqe.lab.eng.bos.redhat.com-certs.tar" --puppet "true" --puppetca "true" --pulp "true" --qpid-router "true" --reverse-proxy=true
Execution of '/usr/bin/yum -d 0 -e 0 -y list katello-debug' returned 1: Error: No matching Packages to list
/Stage[main]/Capsule::Install/Package[katello-debug]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list katello-debug' returned 1: Error: No matching Packages to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list pulp-docker-plugins' returned 1: Error: No matching Packages to list
/Stage[main]/Pulp::Install/Package[pulp-docker-plugins]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list pulp-docker-plugins' returned 1: Error: No matching Packages to list
Installing Done [100%] [.........................................................................................................]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/capsule-installer/capsule-installer.log
Expected results:
Capsule can be installed with only requisite repos enabled.
Additional info:
I have confirmed that the capsule/common repos for the appropriate compose have been selected and synced to my capsule.
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.
https://access.redhat.com/errata/RHSA-2015:1592