Scott Henson <shenson(a)redhat.com> wrote:
On Mon, 07 Mar 2011 23:57:41 -0800, petermity
<6t12-n6js(a)dea.spamcon.org> wrote:
> Scott Henson <shenson(a)redhat.com> wrote:
>
> >On Fri, 04 Mar 2011 00:16:24 -0800, petermity <6t12-n6js(a)dea.spamcon.org>
wrote:
> >> In 2.0.10, when validateks completes I get:
> >>
> >> *** potential errors detected in kickstarts ***
> >> *** TASK COMPLETE ***
> >>
> >> even when every profile shows empty for stdout and stderr, and no
> >> other complaints are shown, e.g. all of them look like:
> >
> >Looking through the code, I'm not sure why that would happen. The only
> >thought I have is that ksvalidate is returning a non-zero exit code for
> >some reason. Beyond that, I'm a little stumped.
>
> I manually ran ksvalidator against the getks output for each of
> my profiles. I have to provide a -v parameter for the version of
> Red Hat kickstart to validate against, e.g. "-v RHEL5", to get
> ksvalidator to work properly. I don't understand how you can run
> the command without doing so. For instance, for one profile the
> validateks output shows:
Ok, that makes sense. I'll see about getting a fix commited for this. Thanks.
It doesn't really make sense to me - the stdout or stderr shown
by cobbler validateks should be matching the ksvalidator output
if it's just the missing -v. But those show nothing, so there
must be more to it - which hopefully you will easily discover
once you get into it.