Description of problem: If a user runs a the installation script that comes with RHN Satellite, they will discover that, after running 'cobbler check', a few things remain unconfigured: [root@530sat ~]# cobbler check /bin/sh: /usr/sbin/semanage: No such file or directory The following potential problems were detected: #0: you need to set some SELinux content rules to ensure cobbler works correctly in your SELinux environment, run the following: /usr/sbin/semanage fcontext -a -t public_content_t "/var/lib/tftpboot/.*" && /usr/sbin/semanage fcontext -a -t public_content_t "/var/www/cobbler/images/.*" #1: change 'disable' to 'no' in /etc/xinetd.d/tftp #2: reposync is not installed, need for cobbler reposync, install/upgrade yum-utils? #3: yumdownloader is not installed, needed for cobbler repo add with --rpm-list parameter, install/upgrade yum-utils? #4: The default password used by the sample templates for newly installed machines (default_password_crypted in /etc/cobbler/settings) is still set to 'cobbler' and should be changed #5: fencing tools were not found, and are required to use the (optional) power management features. install cman to use them Some of these options might be up to the user to configure, but as it stands, the user might be led to believe that no further configuration is required. Version-Release number of selected component (if applicable): 530, 5/1 build How reproducible: Always Steps to Reproduce: 1. Run Satellite install script 2. Read through the dialog presented to the user 3. Run a 'cobbler check' Actual results: User not told that further configuration is required (if it is), or cobbler check emits errors similar to those reported Expected results: User either told that further configuration is required or cobbler check does not emit errors Additional info:
So cobbler check is a documented command. http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3.0/html/Reference_Guide/ch-cobbler.html#s2-cobbler-reqs-check All the output is controlled by Cobbler. I would suggest that Mike McCune/Justin/Partha works with Michael DeHann to create new bug(s) under cobbler upstream to address the issue. I suspect that improved wording would be nice. Most of these are relevant - depending on your planned usage of cobbler within Satellite. If your not doing PXE boot environment off Satellite then do not worry. Same for SELinux and the other items listed. So just clearer wording, but do not stop the display of these messages. Of course the Cobbler team (Mike, Justin, Partha with Michael) may on review determine that some of these should have indeed already been addressed during the installation part. Cliff
As stated in Comment #1, this bug is to act as a tracker or task list for Satellite Development to create new tickets against Cobber to get the correct behavior for Satellite usage. It is intended for this to be an effort where "Mike McCune/Justin/Partha works with Michael DeHann to create new bug(s) under cobbler upstream to address the issue." This bug should not be assigned to Michael DeHann as there are no specific actions, and this is a Satellite bug, not a Cobbler bug.
Agreed, these are steps that either the user or the Satellite installer did not complete and is not a Cobbler bug. A cobbler bug would be if one of these items were fixed and cobbler is still mentioning they should be addressed. Assign these to someone working on the Sat integration if we believe this is something the Satellite installer should be taking care of.
cobbler ticket filed: https://fedorahosted.org/cobbler/ticket/461
VERIFIED on 6/19 build.
RELEASE_PENDING from 7/24 build.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html
*** Bug 589693 has been marked as a duplicate of this bug. ***