Red Hat Bugzilla – Bug 158292
redhat-release is not upgraded through Satellite if /etc/issue is modified
Last modified: 2007-11-30 17:07:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050514 Fedora/1.0.4-0.fdr.1.2 Firefox/1.0.4
Description of problem:
When attempting to schedule redhat-release errata for update on a system with a modified /etc/issue (all of mine in other words), the update fails. The reason for the failure is that a config file has changed.
If /etc/issue is changed on a system to provide a company message, this package install fails. This can be circumvented by setting noReplaceConfig=0 in /etc/sysconfig/up2date. This is not an acceptable solution as it would expose real configuration files to risk.
Apparantly /etc/issue is seen as a configuration file, which seems unusual. This file does not affect the performance of the server or any application, nor do changes to this file affect operation of the server. This file is information only.
It is standard business practice to place a message to be displayed at login, often including legal disclaimer wording to authorise monitoring.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Schedule redhat-release update through satellite
2. Run rhn_check on server where update was scheduled for
Actual Results: Install of package fails with message
Name Version Rel Reason
redhat-release 3AS 13.5.1Config modified
Expected Results: Package should have installed, possibly backing /etc/issue up
Not really an up2date issue, reassigning to redhat-release.
I would like to add that while setting the noReplaceConfig to 0 does allow
up2date to install the new version without error, but it also replaces your
company banner with the default redhat one. Actually it renames your modified
banner to /etc/issue.rpmsave before extracting the new redhat issue file. This
must be because the issue file is defined like this in the spec file:
This behavior needs to be changed to allow up2date to work in an environment
where company policy requires a customized login banner.
I've confirmed that with the version of redhat-release included in RHEL 3 U7,
/etc/issue is now properly marked as %config(noreplace) and that up2date with a
modified /etc/issue results in package upgrade and the creation of /etc/issue.rpmnew