Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1359221 - katello-installer --katello-proxy-url fails due to '_' in the fqdn in proxy server name
Summary: katello-installer --katello-proxy-url fails due to '_' in the fqdn in proxy s...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Installer
Version: 6.1.9
Hardware: All
OS: Linux
unspecified
high vote
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1360471
TreeView+ depends on / blocked
 
Reported: 2016-07-22 14:23 UTC by Josh Foots
Modified: 2018-08-31 15:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-07 15:38:22 UTC


Attachments (Terms of Use)

Description Josh Foots 2016-07-22 14:23:06 UTC
Description of problem:
katello-installer --katello-proxy-url <servername> --katello-proxy-port 8020

fails when there are special characters in the FQDN of the proxy

the problem is the URI module cannot parse the underscore in the proxy's FQDN 

Version-Release number of selected component (if applicable):


How reproducible:

Very

Steps to Reproduce:
1. run the katello-installer --katello-proxy-url with an underscore in the address
2.
3.

Actual results:
katello-installer --katello-proxy-url <servername> --katello-proxy-port 8020
/usr/share/ruby/uri/generic.rb:214:in `initialize': the scheme https does not accept registry part: proxy_server.mutualofomaha.com (or bad hostname?) (URI::InvalidURIError)
        from /usr/share/ruby/uri/http.rb:84:in `initialize'
        from /usr/share/ruby/uri/common.rb:214:in `new'
        from /usr/share/ruby/uri/common.rb:214:in `parse'
        from /usr/share/ruby/uri/common.rb:747:in `parse'
        from /usr/share/ruby/uri/common.rb:996:in `URI'
        from /usr/share/katello-installer/hooks/pre_validations/11-check_proxy_url.rb:11:in `block (4 levels) in load'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hooking.rb:32:in `instance_eval'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hooking.rb:32:in `block (4 levels) in load'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hook_context.rb:13:in `instance_exec'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hook_context.rb:13:in `execute'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hooking.rb:49:in `block in execute'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hooking.rb:47:in `each'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/hooking.rb:47:in `execute'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/kafo_configure.rb:92:in `execute'
        from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:67:in `run'
        from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:125:in `run'
        from /usr/share/gems/gems/kafo-0.6.5.9/lib/kafo/kafo_configure.rb:116:in `run'
        from /usr/sbin/katello-installer:46:in `<main>'
lx086:/etc/yum.repos.d#


Expected results:

For the URI to correctly process the special characters.


Additional info:

Comment 1 Chris Roberts 2016-07-22 15:55:43 UTC
Josh,

For the meantime we can do the following:

https://ip

or we can comment out the installer check. Let me know if you need help with this.

- Chris

Comment 3 Stephen Benjamin 2016-08-01 18:41:38 UTC
There seems to be a good bit of misinformation out there about the dreaded underscore. As far as I can tell, _ is only valid in certain cases but this isn't one of them - "proxy_server" is part of the host name and the RFC's explicitly disallows underscore there. More info here - 
http://domainkeys.sourceforge.net/underscore.html

Ruby URI module is handing this correctly I think. 

@Chris, Can we close this NOTABUG? I think the error message is helpful enough ("bad host name")

Comment 4 Chris Roberts 2016-09-07 15:38:22 UTC
@Stephen,

I agree I have only see 1 case come in with this issue. Most customers are following the RFC guidelines. Also it looks that the case is closed attached to this bug so further supporting a close.

Closing this out as NOTABUG.

- Chris Roberts


Note You need to log in before you can comment on or make changes to this bug.