Custom Query (894 matches)


Show under each result:

Results (112 - 114 of 894)

Ticket Owner Reporter Resolution Summary
#836 desai solj wontfix Action support for Snapshots model

We need to add Action entries to Snapshots to prevent this:

Failed to bind entry: Action googleearth
Handled 1 events in 0.000s
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/", line 486, in __bootstrap_inner
  File "/usr/lib/python2.5/", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/root/bcfg2/Bcfg2/Server/Plugins/", line 79, in load_snapshot
    self.statistics_from_old_stats(metadata, data)
  File "/root/bcfg2/Bcfg2/Server/Plugins/", line 98, in statistics_from_old_stats
    + build_snap_ent(entry)
  File "/root/bcfg2/Bcfg2/Server/Plugins/", line 34, in build_snap_ent
KeyError: 'Action'
#855 desai somekool <[email protected]…> wontfix release a patch update for 0.9.6

0.9.6 still deserve a maintenance release.

on top of the two patches I uploaded on ticket #846

I will upload to this ticket my modified RPM spec file and 2 more patches.

#888 desai somekool <[email protected]…> wontfix generate Probes scripts with a templating system like TGenshi

this might sounds like a crazy request. but it seems to be the best way I could reuse code between probes.

sometimes identical logic needs to be used in several probes script. but no code reuse is possible between them unless I push a library script on all my system. which I don't want to update every now and then. I like the way bcfg2 push those probes script and runs them.

I think it'd be cool to preprocess the probes with TGenshi for more power... In the mean time, I guess I can push the file with a TGenshi ConfigFile? entry and ask the probe to run it. but people here don't like to push scripts with bcfg2.

unless you tell me a probe/group can output multiples group/probe entry?

Note: See TracQuery for help on using queries.