Description of problem: On two separate customer Satellites I've recently started seeing that the "Configs" column in the "Systems -> Systems" overview page is not updating after config files are deployed and diffed. The details page of a given system will show that the system is clean (no config file differences) while the overview page shows a number > 0 for that system. I can knock that number loose by adding a config file to the configuration channel and then running another diff. However if I change that file in the configuration manager, deploy and diff, the System page's config column sticks with a "1" again while the system details page shows it as clean. Manual checksum checks show that files are deploying and everything is working. It just that the overview page is only updating under circumstances I don't understand. This is a recent change in behaviour. Possibly introduced after an update to "spacewalk-*-2.0.3-29" packages in July 8th. Version-Release number of selected component (if applicable): spacewalk-*-2.0.3-29 How reproducible: Happens with all client systems. Steps to Reproduce: 1. On a system with existing configuration file differences, system_x, observe the number of differences reported for that system on the Systems overview page in the "Configs" column. 2. Now deploy all configuration files to system_x and run a diff of all files on system_x. 3. Observe the "Config" column at "Systems -> Systems" for system_x 4. Observe file diff status at "Systems -> Systems -> system_x -> Configuration" under "Recent Events" Actual results: System overview page will show file differences while the "system details -> Configuration" page under "Recent Events" will show 0 differences. Disk state on client system_x is accurately represented by the "Recent Events" status. Files are deployed and in sync with configuration management system. Expected results: I expect the overview page to update the number in the "Configs" column after configuration file diffs are run. Additional info:
*** This bug has been marked as a duplicate of bug 1140180 ***