Red Hat Bugzilla – Bug 1281340
config file comparison event detail page is missing link to the diff
Last modified: 2016-01-11 10:19:57 EST
Created attachment 1093128 [details]
Same steps performed on Satellite 5.6.0 and 5.7.0 and result of config diff event page (5.7.0 is missing the link)
Description of problem:
When configuration file comparison finds a difference, event detail page is missing link to the diff.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create config channel, create file in it, ensure the client have
`rhn-actions-control --enable-all`, deploy that file on the client,
change that deployed file on the client
2. Schedule config file diff:
Systems -> <client> -> Configuration -> Compare Files
3. Run `rhn_check` on the client so the diff is executed
4. Check if we have link to the diff on the event page
Systems -> <client> -> Events -> History -> <event>
No link to the diff, although when I guess "acrid" parametr, diff displays nicely: https://<fqdn>/rhn/systems/details/configuration/ViewDiffResult.do?sid=<sid>&acrid=...
See the attached screenshot.
Link to the diff of whats on the system and what in the config channel should be present.
This was noticed by Vivek Dhande <firstname.lastname@example.org> - thanks!
This is a regression against 5.6.0.
Fixed in SW under https://bugzilla.redhat.com/show_bug.cgi?id=1205108. The following commit fixes the problem:
*** Bug 1290773 has been marked as a duplicate of this bug. ***
Reproduced on spacewalk-java-2.3.8-120.el6sat.noarch using the reproducer from comment #1, with the same result - no link to file difference present.
Updated to spacewalk-java-2.3.8-123.el6sat.noarch, modified the managed file on a registered station, and scheduled a new diff run. I have run rhn_check on the registered station, and checked the event log on Satellite server. The link to file difference is now present. See the attached screenshot.
Created attachment 1106731 [details]
Screenshot of the diff event details page before and after update.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.