Bug 1123483
Summary: | ISE when selecting Repositories to enable (likely CDN issue); need better messaging / error reporting | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Shannon Hughes <shughes> | ||||||||
Component: | WebUI | Assignee: | Justin Sherrill <jsherril> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 6.0.3 | CC: | achan, bbuckingham, bhamrick, bkearney, chrobert, dcleal, hjensas, jmontleo, sthirugn, xdmoon | ||||||||
Target Milestone: | Unspecified | Keywords: | Triaged | ||||||||
Target Release: | Unused | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
URL: | http://projects.theforeman.org/issues/7979 | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: |
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.
|
Story Points: | --- | ||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2014-11-13 22:28:52 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 1115190 | ||||||||||
Attachments: |
|
Created attachment 921043 [details]
repo expansion
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. Created attachment 922242 [details]
manifest
Created redmine issue http://projects.theforeman.org/issues/7979 from this bug 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 *** Bug 1121269 has been marked as a duplicate of this bug. *** 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 *** Bug 1149670 has been marked as a duplicate of this bug. *** |
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.