Bug 834412 - [RFE] RPM should set up Apache config, not aeolus-configure
Summary: [RFE] RPM should set up Apache config, not aeolus-configure
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configure
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
Assignee: John Eckersberg
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-21 19:12 UTC by Matt Wagner
Modified: 2014-08-17 22:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 20:53:58 UTC
Embargoed:

Attachments (Terms of Use)

Description Matt Wagner 2012-06-21 19:12:41 UTC 
Description of problem:
When I built some Conductor RPMs from source and installed them, they laid down a new /etc/httpd/aeolus-conductor.conf file. It seems to be HTTP (*:80) only.

Apparently, aeolus-configure sets up an HTTPS Apache file, and changes the HTTP config to just throw redirects to the HTTPS one.

This setup makes zero sense. Why not just set up Apache correctly in the RPM, versus laying down a broken configuration and then requiring a script to be run to make it work?

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


How reproducible:


Steps to Reproduce:
1. Install Aeolus RPMs, do not run aeolus-configure
2. Restart Conductor and Apache
3. Visit https://localhost/conductor
  
Actual results:
404

Expected results:
200 (or 302, or even a 304)


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