Bug 977810 - Config file management: diffs not shown through webui
Summary: Config file management: diffs not shown through webui
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.9
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 11:31 UTC by pierre.casenove
Modified: 2019-09-16 11:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-16 11:50:57 UTC
Embargoed:


Attachments (Terms of Use)

Description pierre.casenove 2013-06-25 11:31:55 UTC
Description of problem:
Spacewalk 1.9 introduced the possibility to configure rhncfg-client to output the diffs on config files managed by spacewalk, even is the file is not readable by everyone.
The new option "display_diff = True" is needed in file /etc/sysconfig/rhn/rhncfg-client.conf to print the output.

This works through the CLI but does not work through the WEB UI

Moreover, in the latest spacewalk client rpms, the default rhncfg-client.conf file does not contain the parameter "display_diff = True".


Version-Release number of selected component (if applicable):1.9

How reproducible: Manage a non world readable file through spacewalk


Steps to Reproduce:
1. Manage (for example) sshd_config file (which is not world readable) by spacewalk
2. Schedule a config file comparison from the WEB UI
3. Once the comparison done, go to the result page

Actual results:
Message "Differences exist in a file that is not readable by all. Re-deployment
of configuration file is recommended" is printed in the web UI

Expected results: differences, is some exist.


Additional info:

Comment 2 Michael Mráka 2019-09-16 11:50:57 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.


Note You need to log in before you can comment on or make changes to this bug.