Description of problem: When using Kerberos authentication, beaker-log-delete prints a line like Kerberos initialization for HTTP/hostname@REALM This is a problem because we expect the admin to call this command in a cron job, and cron jobs should be silent unless something goes wrong. beaker-log-delete should therefore be silent by default, unless something goes wrong. It could potentially have a --debug or --verbose option like some of the server commands, if that is desired. Version-Release number of selected component (if applicable): 0.16.2 How reproducible: always Steps to Reproduce: 1. Configure beaker-log-delete to use Kerberos authentication for talking to the archive server 2. Run beaker-log-delete Actual results: Prints output. Expected results: Silent unless failure. Additional info: I think the output comes from requests-kerberos.
I would like us to fix this ASAP since it is currently making it difficult to find failures in log-delete (which we are also experiencing, it seems).
Actually I just realised this output is probably from k5start. Need to figure out: * do we document the use of k5start anywhere? if not, it should be * can we pass k5start an option to suppress the message? if not, need to do something like redirect stdout to /dev/null... either way add it to the docs
It's -q.