Bug 786978

Summary:	Need to host SystemEngine at https://<host>/cfse vs /katello
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	WebUI	Assignee:	Jordan OMara <jomara>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.1	CC:	athomas, bkearney, cwelton, gkhachik, tomckay
Target Milestone:	Unspecified	Keywords:	Question, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	786981 (view as bug list)		Environment:
Last Closed:	2012-04-27 00:31:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	786981

Description Mike McCune 2012-02-02 19:51:46 UTC

Need to make whatever necessary changes SystemEngine so installs show up in the website under:

https://<host>/cfse 

right now they show up under /katello/

Will require changes to:

 * rails configuration
 * httpd conf files (katello.conf)
 * client side configuration files that default to /katello/
 * possible other areas I'm not currently thinking of

Comment 1 Jeff Weiss 2012-02-06 15:09:31 UTC

Perhaps we should consider

/cloudforms/systemengine
/cloudforms/cloudengine

or something of that nature (hosting the multiple components of CF under one directory).

Comment 2 Jordan OMara 2012-02-24 18:08:52 UTC

committed f0de8056d88136a7da665daf1a355782ab3e2d3d

you can now use --deployment={cfse,sam,headpin,katello}

Comment 4 Mike McCune 2012-03-07 23:43:51 UTC

mass move ON_QA after brewing

Comment 5 Corey Welton 2012-03-08 20:45:04 UTC

Not seeing latest brew build default to /cfse.  I suspect backend/installer changes are not in yet.

Comment 6 Mike McCune 2012-03-08 22:10:36 UTC

when you did 'katello-configure' did you do 'katello-configure --deployment=cfse'?

worked fine for me when I did this with the latest brew built packages yesterday

Comment 7 Corey Welton 2012-03-09 20:06:30 UTC

Verified - although if we wanted to split hairs, it fails mostly-silently in the CLI for an invalid target:

[root@deploy12 ~]# katello-configure --deployment=cfsedd
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20120309-150029/main.log]
[root@deploy12 ~]#

Ideally we should probably tell the user what the valid targets are and/or indicate that the install has halted when something invalid is used.  

Will mark this bz verified and may or may not open a different bz re: what's noted above.

Comment 8 Mike McCune 2013-08-16 18:10:13 UTC

getting rid of 6.0.0 version since that doesn't exist