[Spacewalk-list] Force Configuration File Compliance During Compares?

[Stephan Duehr]

Hi,

the API does not expose details of config compare actions:

>>> sys_events = client.system.listSystemEvents(session, sys_id)
>>> pp.pprint([e for e in sys_events if e['id'] == 14090])
[   {   'action_type': 'Show differences between profiled config files and deployed config files',
        'archived': 0,
        'completed_date': <DateTime '20141002T18:14:52' at 19f85f0>,
        'completion_time': '2014-10-02 18:14:52.090907',
        'created': '2014-10-02 18:14:44.37733',
        'created_date': <DateTime '20141002T18:14:44' at 19f8518>,
        'earliest_action': '2014-10-02 18:14:00.0',
        'failed_count': 0,
        'id': 14090,
        'modified': '2014-10-02 18:14:52.090907',
        'modified_date': <DateTime '20141002T18:14:52' at 19f8560>,
        'name': 'Show differences between profiled config files and deployed config files',
        'pickup_date': <DateTime '20141002T18:14:51' at 19f84d0>,
        'pickup_time': '2014-10-02 18:14:51.846311',
        'result_msg': 'Files successfully diffed',
        'scheduler_user': 'stephand',
        'successful_count': 1,
        'version': '2'}]

In Spacewalk Web UI however, I see
The client completed this action on 10/2/14 6:14 PM
Client execution returned "Files successfully diffed" (code 0)
Config Files:
/etc/ssh/sshd_config (rev. 2)
/var/tmp/testdir_from_channel/testfile_06 (rev. 1) Missing file
...

It would be a useful feature, if the API would expose some
details of the compare action result. If not all details, at least
something that tells if differences exist or not.

Regards

Stephan


On 10/02/2014 03:43 PM, Glennie, Jonathan - 0443 - MITLL wrote:
> Hello-
> 
>  
> 
> Is there a way to configure spacewalk to automatically push config files to client systems when the compares get run and differences are noticed?  I’m working with a large number of VMs and sometimes
> they get rolled back to previous states from snapshots, therefor any config file updates/changes that have been previously made and pushed do not get reapplied as SW thinks the client picked up and
> executed it’s task, even though the client is then in a state where it hasn’t.  I would like to be able to tell SW and the client to automatically re-deoploy config files to a machine when differences
> are found, but right now the only way I can think of to do that is to put a cron entry on every machine to run “rhncfg-client get” at some specified time interval.  It’s a lot of unnecessary overhead
> and the network traffic could be trimmed down quite a bit if SW and the clients were only updating files that need to be and only when they need to be.   Does anyone know of a better way?  Thanks. 
> 
>  
> 
> -Jon
> 
> 
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 


-- 
Stephan Dühr                                stephan.duehr at dass-it.de
dass IT GmbH                               Phone: +49.221.3565666-90
http://www.dass-IT.de                        Fax: +49.221.3565666-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRB52500
Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz