Description of problem: As I was validating a test case, I came across https://bugzilla.redhat.com/show_bug.cgi?id=822671 which states that one should not be able to re-run katello-configure after the system has already been configured. This is no longer true and re-running katello-configure is allowed and supported. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run katello-configure --deployment=cfse more than once 2. 3. Actual results: Expected results: Additional info:
I don't get it. What is actual and expected result? It should work. Is there an error?
I apologize, this is a doco bug. Yes, katello configure can be now executed as many times as needed. It will "correct" everything according our configuration definition written in Puppet DSL. It also has some new options. You can list them in the man page of katello-configure.
I maybe would add a warning: Warning: Katello-configure always replaces all the configuration files from templates. To see which files are replaces do # rpm -ql katello-configure | grep erb
Available In: http://documentation-devel.engineering.redhat.com/docs/en-US/CloudForms/1.1/html/Installation_Guide/Configuration_Options1.html Changes: 1. We've added the options as well as the additional line "The command <command>katello-configure</command> can be run multiple times after initial configuration." Options have been added on an earlier bug so the changes have already been added. 2. <warning> <para> When run, <command>katello-configure</command> replaces all the configuration files with the standard templates. If the <application>System Engine</application> has customized configuration files, please back them up before running <command>katello-configure</command>. </para> <para> The following command will show you the files that will be replaced when you run the <command>katello-configure</command> command: </para> <screen> # rpm -ql katello-configure | grep erb </screen> </warning>
This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug. LKB
This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug. LKB