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.
Previously, the Satellite Server did not inform the user of any errors that occured when enabling repositories. Better error reporting messages have been added into the web UI. If an issue crops up when enabling repositories, the UI should now inform the user about these errors.
Created attachment 921042[details]
debug log
Description of problem:
Uploaded manifest which was successful. Then went to enable rhel 6 repo and kickstart repo. The spinner next to Red Hat Enterprise Linux 6 Server (Kickstart) spins for a while and then expands with no options underneath. (see attached screenshot).
Looked in production.log and noticed the ISE. The CDN today seems to be slow so that might be part of the issue but we should handle errors gracefully and have some type of indication of failure to user.
attaching production.log for debugging.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7979 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|b0a8b01cd1863997f786ccfb9c7b73c592abfded.
** Verified against Z-Stream **
Error message received when verifying:
There was an error attempting to enable or disable this repository:
getaddrinfo: Name or service not known
Satellite-6.0.4-RHEL-7-20141029.5
foreman-1.6.0.47-1.el7sat.noarch
foreman-compute-1.6.0.47-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.5-2.el7sat.noarch
foreman-gce-1.6.0.47-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-1.3.0-2.el7sat.noarch
foreman-libvirt-1.6.0.47-1.el7sat.noarch
foreman-proxy-1.6.0.30-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.4-2.el7sat.noarch
foreman-vmware-1.6.0.47-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-3.el7sat.noarch
foreman-selinux-1.6.0.15-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.1.el7sat.noarch
foreman-ovirt-1.6.0.47-1.el7sat.noarch
foreman-postgresql-1.6.0.47-1.el7sat.noarch
qe-sat6-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch
qe-sat6-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch
rubygem-hammer_cli_foreman-0.1.1-16.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el7sat.noarch
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/RHBA-2014:1857
Created attachment 921042 [details] debug log Description of problem: Uploaded manifest which was successful. Then went to enable rhel 6 repo and kickstart repo. The spinner next to Red Hat Enterprise Linux 6 Server (Kickstart) spins for a while and then expands with no options underneath. (see attached screenshot). Looked in production.log and noticed the ISE. The CDN today seems to be slow so that might be part of the issue but we should handle errors gracefully and have some type of indication of failure to user. attaching production.log for debugging.