Bug 640319 - Manage Providers: cloud engine does not accept URL redirect for provider url
Summary: Manage Providers: cloud engine does not accept URL redirect for provider url
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: alpha
Assignee: Angus Thomas
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-05 14:51 UTC by wes hayutin
Modified: 2012-01-26 12:29 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description wes hayutin 2010-10-05 14:51:51 UTC
Description of problem:

Manage Providers: cloud engine does not accept URL redirect for provider url  

Recreate:
1. first test the url redirect of deltacloud core. You may need to edit the /etc/init.d/deltacloud-core-ec2 to allow outside connections. 
ADD:IPADDR="your IP or 0.0.0.0"

Modify the file
=======start===========
start() {
    echo -n "Starting deltacloud-core-$DRIVER: "

    $PROG -i $DRIVER -e $ENV -p $PORT >& $LOGFILE &
=======finish==========  
start() {
    echo -n "Starting deltacloud-core-$DRIVER: "

    $PROG -i $DRIVER -e $ENV -r $IPADDR -p $PORT >& $LOGFILE &

2. restart the service
3. verify that http://ip:port redirects your browser to http://ip:port/api
4. In cloud engine, navigate to System Settings -> Manage Providers 
5. add a provider
6. enter a name and http://ip:port 


Results:

undefined method `driver_name' for nil:NilClass 


Expected Results:
Cloud Engine can handle the redirect...


Test Case from tsedovic
Case 56935 "field check providers"
----------------------------------
1, We should test that a provider URL with HTTP redirect works. We can 
use the mock driver:

If you go to  <http://localhost:3001>, it redirects to 
<http://localhost:3001/api>

Comment 2 Chris Lalancette 2011-06-13 21:13:28 UTC
Tomas, is this fixed now?  This is ancient, so I assume yes, but I wanted to make sure before closing.

Thanks,
Chris Lalancette

Comment 3 wes hayutin 2011-06-14 15:39:49 UTC
moving to on_qa for review

Comment 4 wes hayutin 2011-07-08 21:43:52 UTC
woot.. finally working :)

http://hp-xw6600-02.rhts.eng.bos.redhat.com:3006 


10.16.65.48 - - [08/Jul/2011 17:39:25] "GET / HTTP/1.1" 301 - 0.0011
10.16.65.48 - - [08/Jul/2011 17:39:25] "GET /api HTTP/1.1" 200 926 0.0094
10.16.65.48 - - [08/Jul/2011 17:39:25] "GET / HTTP/1.1" 301 - 0.0008
10.16.65.48 - - [08/Jul/2011 17:39:25] "GET /api HTTP/1.1" 200 926 0.0150
10.16.65.48 - - [08/Jul/2011 17:39:26] "GET / HTTP/1.1" 301 - 0.0011
10.16.65.48 - - [08/Jul/2011 17:39:26] "GET /api HTTP/1.1" 200 926 0.0091
10.16.65.48 - - [08/Jul/2011 17:39:26] "GET /api/hardware_profiles HTTP/1.1"
200 1813 0.0123

[root@hp-xw6600-02 ~]# rpm -qa | grep aeolus
rubygem-aeolus-cli-0.0.1-1.el6.20110708135911gitdb1097c.noarch
aeolus-all-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-configure-2.0.1-0.el6.20110707131907gitfaa220b.noarch
aeolus-conductor-0.3.0-0.el6.20110708135911gitdb1097c.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110708135911gitdb1097c.noarch

Comment 5 wes hayutin 2011-08-01 19:53:54 UTC
release pending...

Comment 6 wes hayutin 2011-08-01 19:55:54 UTC
release pending...

Comment 8 wes hayutin 2011-12-08 13:51:21 UTC
closing out old bugs

Comment 9 wes hayutin 2011-12-08 14:04:26 UTC
perm close


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