Description of problem: `katello-configure` needs to be specified with configuration property --deployment=cfse (as the absence right now points to Katello) So doing the installation makes the stuff ok, but just refers all the UI links via "/katello/<pages>" which is not correct ("/cfse/<pages>) is the right one IMO. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.doing `katello-configure` without --deployment=cfse 2. 3. Actual results: doc does not contain a note having --deployment=cfse option to be specified. Expected results: point users to have --deployment=cfse (other options: headpin, katello, sam) Additional info:
Thanks for raising this issue Garik. I'm not in favor of changing the default configuration documentation for the 1.1 release at this time. I'm not opposed to the change for a future release, but in my view, it's too late to make this change for 1.1. We've never documented using --deployment=cfse in previous releases, and I'm concerned that if we start to document it now, we may expose unexplored/untested areas of katello. Additionally, recommending use of an optional non-required parameter for katello-configure seems incomplete. If --deployment=cfse is truly important, perhaps it should be a required parameter ... otherwise we'll have confused customers with different baseurls. Lastly, changing to recommending using --deployment will differ from testing performed throughout the beta. My recommendation would be to leave the documentation and code as is for 1.1 and explore a more cohesive approach for a future release.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.