Random mailing list tip. The statement "feature X is broken" doesn't help me much as I don't know what that means. Worse, it means I have to try it to figure out if I can figure out what may or may not be broken, and that takes up a fair amount of time.
Broken can mean something throws a traceback, doesn't work like you think it should, or perhaps something quite different. So, when posting problems, it helps if everyone can please include the following: (A) What command or operation you were trying to run. If this was on the command line, include the actual command or commands from your bash history. (B) What you expected to happen or where trying to do (C) What actually happened. If this was on the command line, include the full output of the command and other commands as relevant, like sections of "cobbler report" (D) If there is an exception, include the tails of /var/log/cobbler (for local operations) or /var/log/cobblerd (for web operations) to show those exceptions. This can be skipped if it's obvious, such as the exception is already visible from the command line, or there is no exception and the behavior is just different than expected. Most folks are pretty good about this, but in general, it's better to have more detail than less. This goes not just for cobbler, but all projects ... Thanks! --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
