Bug 1339608 - Ansible Tower Provider URL field not working as expected
Summary: Ansible Tower Provider URL field not working as expected
Keywords:
Status: CLOSED DUPLICATE of bug 1322590
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Greg Blomquist
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 12:41 UTC by Lutz Lange
Modified: 2016-05-27 11:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-27 11:42:48 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lutz Lange 2016-05-25 12:41:31 UTC
Description of problem:
  Adding a new Ansible Tower list a field as "URL"
  A URL is http://server:port or https://server:port
  Both do not work. 
  Instead the Hostname is what was expected.

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


How reproducible:
  Try to add Ansible Tower with a full URL.

Actual results:
  Connection not working with https://mytower.example.com

Expected results:
  This field should be able to use URLs or be called hostname instead


Additional info:

Comment 2 Brandon Dunne 2016-05-26 15:07:49 UTC
I tested on both master and darga and this is already fixed.  What version are you testing against?

Comment 3 Lutz Lange 2016-05-26 15:23:16 UTC
I used :

cfme-gce-5.6.0.7-1
and 
Ansible Tower Version 2.4.3

Comment 6 Brandon Dunne 2016-05-26 18:07:23 UTC
Do you think your issue is environment related?  If you share the url and credentials I can try to debug further.

Comment 7 Brandon Dunne 2016-05-27 11:42:48 UTC
Tried in the test environment and could not reproduce the error. This should be resolved by the bug and PR above and should be working since 5.6.0.2.  If you are able to reproduce an error, please reopen.

*** This bug has been marked as a duplicate of bug 1322590 ***


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