Bug 812852 - Providing hostname instead of localhost in configserver URL for ec2 gives proxy error 502
Summary: Providing hostname instead of localhost in configserver URL for ec2 gives pro...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configserver
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Greg Blomquist
QA Contact: dgao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 12:45 UTC by Shveta
Modified: 2012-04-17 11:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-16 20:21:33 UTC


Attachments (Terms of Use)

Description Shveta 2012-04-16 12:45:55 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Launched an instance in ec2 with configserver 
2. aeolus-configserver-setup 

This script will help you configure Apache as a proxy for a Config Server.
Typically this is only useful if you are not familiar with Apache
configurations and modules, specifically with mod_proxy, mod_auth_basic, and
mod_ssl.

Also, this configuration tool assumes that you are not currently running Apache
for any purposes on this server.  This configuration tool will create a Named
Virtual Host for *:443.  If this server is currently using Apache to serve
secure pages on port 443, then this tool should not be used.


Do you wish to continue [y/N]: y


Please provide the web application URL where the Config Server is currently
running on this server.  If the Config Server was installed from an RPM, then
this will typically be:

  http://localhost:4567/

The provided URL should be a fully qualified URL, providing the scheme,
hostname, and port:  http://HOSTNAME:PORT/


Enter the application URL [http://localhost:4567/]: https://ec2-107-21-65-224.compute-1.amazonaws.com
Root context: /
App URL: https://ec2-107-21-65-224.compute-1.amazonaws.com
Conductor Auth Key: 928166781437214184954144
Conductor Auth Secret: LsLB9Jhrz55SQTHblIEcA4OwbhLzrJFd5hLufHojTfF9TSU3
\n\n*** You need to add this config server information to a ***
*** provider account in conductor.                      ***
running: echo | /usr/bin/puppet --modulepath /usr/share/aeolus-configserver/configure/puppet/modules --external_nodes /tmp/tmp.sWUdeGJ5er --node_terminus exec
warning: Could not find class apache::auth for domu-12-31-39-13-e2-7c.compute-1.internal
notice: /File[/var/lib/aeolus-configserver/configs/oauth/928166781437214184954144]/ensure: defined content as '{md5}e116c92b880add445ceb4d575ddc561f'
notice: /Stage[main]/Apache::Base/Exec[permit-http-networking]/returns: executed successfully
notice: /Stage[main]/Apache::Base/Exec[graceful-apache]: Triggered 'refresh' from 1 events
notice: Finished catalog run in 132.22 seconds

3. https://ec2-107-21-65-224.compute-1.amazonaws.com/version gives proxy error 502 

4. Same thing i tried with empty value for URL (means http://localhost:4567) 

works fine ..

aeolus-configserver-setup 

This script will help you configure Apache as a proxy for a Config Server.
Typically this is only useful if you are not familiar with Apache
configurations and modules, specifically with mod_proxy, mod_auth_basic, and
mod_ssl.

Also, this configuration tool assumes that you are not currently running Apache
for any purposes on this server.  This configuration tool will create a Named
Virtual Host for *:443.  If this server is currently using Apache to serve
secure pages on port 443, then this tool should not be used.

Do you wish to continue [y/N]: y

Please provide the web application URL where the Config Server is currently
running on this server.  If the Config Server was installed from an RPM, then
this will typically be:

  http://localhost:4567/

The provided URL should be a fully qualified URL, providing the scheme,
hostname, and port:  http://HOSTNAME:PORT/

Enter the application URL [http://localhost:4567/]: 
Root context: /
App URL: http://localhost:4567/
Conductor Auth Key: 020353243834966511993550
Conductor Auth Secret: VXWmws0ZUkvryc2S06cDa7GgGjC3BtrmJ46vCFAm0dB7ctKl
\n\n*** You need to add this config server information to a ***
*** provider account in conductor.  
  

The above works fine and shows : 
<config-server><application-version>0.4.6</application-version><api-version>1</api-version></config-server>




Actual results:


Expected results:


Additional info:

rpm -qa|grep configserver
aeolus-configserver-0.4.6-2.el6.noarch

Comment 1 wes hayutin 2012-04-16 20:21:33 UTC
that is actually the design.. the setup should only resolve to localhost, the services are not meant to be accessible via a resolvable hostname

Comment 2 James Laska 2012-04-17 11:34:53 UTC
(In reply to comment #1)
> that is actually the design.. the setup should only resolve to localhost, the
> services are not meant to be accessible via a resolvable hostname

Should aeolus-configserver-setup even offer a choice to change it, if the default is the only supported option?


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