What I did was; first action in kickstart file is a snippet check_variables, this will check all used variables with their value. For instance to determine if specific database stuff needs to be done; #if $db == "yes" or $db == "no" #set db_parameter_check = "OK" #end if If all variables are set correctly then it show a message "# KICKSTART FILE CHECK: OK" in the top of kickstart file. If not then the message "# *** KICKSTART FILE CHECK: FAILED ****" So we do a View Kickstart before the actual deployment, to see if it is OK or not. Informatie van de Raad voor de rechtspraak, de rechtbanken, de gerechtshoven en de bijzondere colleges vindt u op www.rechtspraak.nl.

Hi Stefan, This is probably due to the yum cached metadata for the repository not having expired since you updated the repository. Check the metadata_expire value in /etc/yum.conf You can lower the value if you wish yum to check for updated metadata more often. Paul Paul Urwin GTI Linux Engineering JPMorgan, 1 Triton Square, Regents Place, London, NW1 3FN -----Original Message----- From: cobbler-bounces(a)lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Heijmans S (spir-it) Sent: Wednesday, March 02, 2011 11:55 To: 'cobbler mailing list' Subject: cobbler reposync Hello, After using 'cobbler reposync' I always need to do a 'yum clean all' on the client before the updates are visible. We use cobbler-2.0.5-1.el5 & cobbler-web-2.0.5-1.el5. In /etc/cobbler/settings I've got the following createrepo settings; createrepo_flags: "-c cache --update -C" The 'cobbler reposync' syncs to a local repository which is updated with 'createrepo --update .' Any ideas why 'yum clean all' is necessary? Regards, Stefan Informatie van de Raad voor de rechtspraak, de rechtbanken, de gerechtshoven en de bijzondere colleges vindt u op www.rechtspraak.nl. _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler 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.

On Wed, 02 Mar 2011 00:15:01 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote: I believe the directives you need are #assert and #raise. Though they are probably disabled by safe templating. I'll include one of them in the next release of cobbler (along with the ability to modify the whitelist in the settings file). -- Scott Henson Red Hat CIS Operator WVU Alum BSAE/BSME

petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote: With Cobbler V2.0.11, I was able to (indirectly) do what I wanted here. I couldn't find a way to use the Cheetah exception-handling directives directly to cause a nice clear error message. Instead, I used #echo to put out an error message of my own. I have a wrapper script that does validation (basically runs getks), and it looks for and shows this error message. It would still be nice to do this directly in Cobbler - halt and put out a user-defined message - without having to wrap the process independently.