cobbler check - how disable warnings?

[petermity]

The "cobbler check" command complains about iptables - but I have
the firewall services turned off.  How can I disable the warning, or
otherwise fool Cobbler into not complaining about it?

Likewise, at this time I don't really need to build Debian-based
systems - I'd like to play with it soon, but for the moment I'd
like to stop the complaint about debmirror.

Likewise, the boot-loaders.  I don't need anything but x86
support.  How can I stop the complaint without doing "cobbler
get-loaders"?  (Which I couldn't even do originally because it
still has no proxy support - see year-old issue #572 - I had to
use a different network to be able to do it).

[Scott Henson]

On Thu, 24 Feb 2011 21:15:05 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:
>  The "cobbler check" command complains about iptables - but
> I have
>  the firewall services turned off.  How can I disable the warning, or
>  otherwise fool Cobbler into not complaining about it?
>  
>  Likewise, at this time I don't really need to build Debian-based
>  systems - I'd like to play with it soon, but for the moment I'd
>  like to stop the complaint about debmirror.
>  
>  Likewise, the boot-loaders.  I don't need anything but x86
>  support.  How can I stop the complaint without doing "cobbler
>  get-loaders"?  (Which I couldn't even do originally because it
>  still has no proxy support - see year-old issue #572 - I had to
>  use a different network to be able to do it). 
Check isn't really meant to be run till it doesn't complain. There are
some things we can't really determine if they are in the right state or
not, so we just put them in the output. Not sure what we would do otherwise.

-- 
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME

[petermity]

Scott Henson <shenson(a)redhat.com&gt; wrote:

> On Thu, 24 Feb 2011 21:15:05 -0800, petermity
> <6t12-n6js(a)dea.spamcon.org&gt; wrote:
> > The "cobbler check" command complains about iptables - but I have
> > the firewall services turned off.  How can I disable the warning, or
> > otherwise fool Cobbler into not complaining about it?
> > 
> > Likewise, at this time I don't really need to build Debian-based
> > systems - I'd like to play with it soon, but for the moment I'd
> > like to stop the complaint about debmirror.
> > 
> > Likewise, the boot-loaders.  I don't need anything but x86
> > support.  How can I stop the complaint without doing "cobbler
> > get-loaders"?  (Which I couldn't even do originally because it
> > still has no proxy support - see year-old issue #572 - I had to
> > use a different network to be able to do it).
>
> Check isn't really meant to be run till it doesn't complain. There are
> some things we can't really determine if they are in the right state or
> not, so we just put them in the output. Not sure what we would do otherwise. 
Perhaps have a way to disable selected warnings. something like some
compilers or lints allow pinpoint control of warnings.

Or perhaps easier for you and more general, have a configuration item in
the settings file that lets a user put in a set of regular expressions to
filter out before reporting.

I can understand where it's not considered a big deal, but to me it's like
compiler output - some people ignore warnings, but I like to have it
completely clean, because then it's trivial to spot real problems.

[Scott Henson]

On Mon, 28 Feb 2011 22:12:29 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:
>  Perhaps have a way to disable selected warnings. something like some
>  compilers or lints allow pinpoint control of warnings.
>  
>  Or perhaps easier for you and more general, have a configuration item in
>  the settings file that lets a user put in a set of regular expressions to
>  filter out before reporting.
>  
>  I can understand where it's not considered a big deal, but to me it's like
>  compiler output - some people ignore warnings, but I like to have it
>  completely clean, because then it's trivial to spot real problems. 
I'm thinking a file in /etc/cobbler that lets you 'ack' specific
warnings from cobbler check? I need to dig into cobbler check at some
point in the future, so I'll put this on my todo list, unless someone
beats me to it.

-- 
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME

[petermity]

Scott Henson <shenson(a)redhat.com&gt; wrote:

> On Mon, 28 Feb 2011 22:12:29 -0800, petermity
> <6t12-n6js(a)dea.spamcon.org&gt; wrote:
> > Perhaps have a way to disable selected warnings. something like some
> > compilers or lints allow pinpoint control of warnings.
> > 
> > Or perhaps easier for you and more general, have a configuration item in
> > the settings file that lets a user put in a set of regular expressions to
> > filter out before reporting.
> > 
> > I can understand where it's not considered a big deal, but to me it's like
> > compiler output - some people ignore warnings, but I like to have it
> > completely clean, because then it's trivial to spot real problems.
>
> I'm thinking a file in /etc/cobbler that lets you 'ack' specific
> warnings from cobbler check? I need to dig into cobbler check at some
> point in the future, so I'll put this on my todo list, unless someone
> beats me to it. 
Thanks - I just submitted an enhancement ticket to help track this:
https://fedorahosted.org/cobbler/ticket/653