Bug 1012027

Summary: Config-file comparison does not notice permission change.
Product: Red Hat Satellite 5 Reporter: Matej Kollar <mkollar>
Component: Configuration ManagementAssignee: Stephen Herr <sherr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 560CC: cperry, dyordano
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-22 12:54:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 924189    

Description Matej Kollar 2013-09-25 15:02:48 UTC
Description of problem: Configuration files as specified in channels are have not only their content but other properties as well, namely file permissions.
Change in those might be of interest, as some programs refuse to operate in case that configuration files they use have inappropriate permissions (for example if they are word-readable). Therefore it can be considered issue that comparing actual config files with those specified in satellite does not notice difference in permissions.

Version-Release number of selected component:

  rhncfg-actions-5.10.55-5.el6sat
  rhncfg-5.10.55-5.el6sat
  rhncfg-client-5.10.55-5.el6sat

How reproducible: always/deterministic


Steps to Reproduce:

  1. Create configuration channel, create some configuration file
  2. Add system to channel, deploy file
  3. change permissions on file (not content), schedule compare file:
        Systems -> <system>
          -> Configuration (provisioning entitilement needed)
          -> Compare files

Actual results:
  no changes are reported

Expected results:
  note about changed permissions

Additional info:
  similarly we should be able to notice selinux context change, owner, group...

  trying to identify change of name would not be good idea, as it is identifying
  info, in that case reporting missing (or changed content if two files are
  swapped) would be ok (case where files are swapped but content is
  same is trivial as it is not distinguishable from "valid" state).

Comment 1 Dimitar Yordanov 2014-07-22 12:54:50 UTC

*** This bug has been marked as a duplicate of bug 1004746 ***