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.

Bug 1062303

Summary: Foreman Cli : Add_Smart Proxy fails
Product: Red Hat Satellite Reporter: Tazim Kolhar <tkolhar>
Component: HammerAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED NOTABUG QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: cwelton, dcleal, omaciel
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-06 16:47:26 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:
Attachments:
Description Flags
foreman-debug none

Description Tazim Kolhar 2014-02-06 15:46:28 UTC 
Created attachment 860244 [details]
foreman-debug

Description of problem:
Add_Smart Proxy  fails

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


How reproducible:
everytime

Steps to Reproduce:
1.]# hammer -v -u admin -p changeme proxy create --url='http://yCxpYV:7504' --name='xmp9ij'
[ERROR 2014-02-06 10:35:45 Exception] Unable to communicate with the proxy: getaddrinfo: Name or service not known
Please check the proxy is configured and running on the host.
Could not create the proxy:
  Unable to communicate with the proxy: getaddrinfo: Name or service not known
  Please check the proxy is configured and running on the host.

2.
3.

Actual results:
the cli fails

Expected results:
the cli should pass

Additional info:
Comment 1 RHEL Program Management 2014-02-06 16:10:13 UTC 
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.
Comment 2 Og Maciel 2014-02-06 16:12:00 UTC 
Tazim, have you checked that the proxy is running and configured as the error message asks?
Comment 4 Dominic Cleal 2014-02-06 16:47:26 UTC 
It looks like you're randomising URLs for smart proxies, which you can't do to test this feature, sorry.

The URLs have to be valid, and have to point to a real server running a real Foreman smart proxy.  Foreman will need to contact the proxy server.

The error here ("getaddrinfo: Name or service not known") indicates the hostname ("yCxpYV") isn't valid.