Cobbler triggers when adding a system record
by Urwin, Paul
Hello
I'm having a problem working out how to get a Cobbler python trigger to be executed when I add a system record.
I have my python module in /usr/lib/python2.4/site-packages/cobbler/modules/paul_test.py (as far as I can tell the filename isn't important).
Based on the old filesystem path based triggers I've registered it using:
def register():
# this pure python trigger acts as if it were a legacy shell-trigger, but is much faster.
# the return of this method indicates the trigger type
return "/var/lib/cobbler/triggers/add/system/post/*"
But it does not seem to get executed when I add a system.
However, if I add a shell script in /var/lib/cobbler/triggers/add/system/post/mytest.sh, the shell script does get run.
There is no documentation I can find that specifically documents the new python style triggers in any detail, what I have found at:
https://github.com/cobbler/cobbler/wiki/Triggers
Certainly suggests I'm doing the right thing, in as much as it says that using the old paths in the register function is what you should do.
Has anyone got any ideas?
Cheers,
Paul
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
11 years, 6 months
Cutting a release from trunk?
by Jonathan Underwood
Hi,
The past couple of days I've been trying to work out what was going on
with cobbler import with the --available-as flag, which is broken in
the current release. Happily I just tested trunk, and I see the issue
is now fixed. Perhaps this is a good point to push out a bug fix
release, as this issue (for me) completely broke cobbler import.
The issue is described here https://github.com/cobbler/cobbler/issues/289
Cheers,
Jonathan
11 years, 6 months