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:
If a user tries to use katello-disconnected with a full URL, as opposed to the hostname -- which is done elsewhere in the product -- an unhandled trace is thrown.
Version-Release number of selected component (if applicable):
Satellite-6.0.4-RHEL-6-20140829.0
How reproducible:
Steps to Reproduce:
1. Attempt to use katello-disconnected akin to
2. katello-disconnected import -m ~/mymanifest.zip --proxy-host http://squid.example.com --proxy-port 8888 --proxy-user admin --proxy-password nimda
Actual results:
/opt/rh/ruby193/root/usr/share/ruby/net/http.rb:763:in `initialize': getaddrinfo: Name or service not known (SocketError)
from /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:763:in `open'
from /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:763:in `block in connect'
from /opt/rh/ruby193/root/usr/share/ruby/timeout.rb:55:in `timeout'
from /opt/rh/ruby193/root/usr/share/ruby/timeout.rb:100:in `timeout'
from /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:763:in `connect'
from /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:756:in `do_start'
from /opt/rh/ruby193/root/usr/share/ruby/net/http.rb:745:in `start'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:62:in `get'
from /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/util/cdn_var_substitutor.rb:154:in `get_substitutions_from'
from /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/util/cdn_var_substitutor.rb:143:in `for_each_substitute_of_next_var'
from /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/util/cdn_var_substitutor.rb:85:in `substitute_vars_in_prefix'
from /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/util/cdn_var_substitutor.rb:61:in `substitute_vars'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:382:in `block (3 levels) in populate_repositories'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:379:in `each_value'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:379:in `block (2 levels) in populate_repositories'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:376:in `each'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:376:in `block in populate_repositories'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:362:in `each_value'
from /usr/share/katello-disconnected/lib/manifest_reader.rb:362:in `populate_repositories'
from /usr/bin/katello-disconnected:375:in `import'
from /usr/bin/katello-disconnected:469:in `<main>'
Expected results:
In reality, we should be handling proxy URLs/hosts uniformly across the product -- requiring users exclude http(s) in some places while requiring it be included elsewhere.
Failing that, we should really at least capture an exception like the above.
Additional info:
The katello-disconnected server synchronization and export functions are being moved into the Satellite server itself. With 6.2, the katello-disconnected command will no longer be delivered and instead will be replaced with a new export and import functions delivered via the UI and hammer CLI. This bug is being closed as "WONTFIX" since it relates only to the existing katello-disconnected tooling. Please check the Satellite docs with the release of Satellite 6.2 on how to use the new content export and import features.