docs: fix a few typos in bkr(1) man page

Change-Id: I6096e1c5f3b41372191fb84d3de2b4ef04cebef4
fix console log storage in beaker-watchdog

This was a typo introduced by 32dea6ec.

Change-Id: I95a68087b980954704bc89fe2800a910ae2ec6de
set timeout for oVirt requests

The timeout needs to be quite short because if oVirt is not responding
it will hold up the entire main loop of beakerd.

Change-Id: Ibdfdda0956a7b3570aac222643d31823cf34addb
Adjust single processor ordering to only consider bare metal
systems.
tests: fix for c17d4b52

The exception type changed, but there's no reason we need to actually
assert it. We can assert the human-friendly message instead.

Change-Id: I90b33d77ad3b71ea6669ca5381cb342fb5436863
show status as "Updating..." if job is dirty

Now that job status is updated asynchronously it is unavoidable that it
lags behind "reality". So we need some way of indicating to the user
that the status we are showing is not up to date, if the job is marked
dirty. Otherwise it looks like Beaker is broken, for example when
cancelling a job and the user is returned to My Jobs, their job would
appear there as still Running.

Change-Id: Icb4be10beb92a58ba9e57c5159cd78c4963343a2
split LC log storage into subdirs of 1000

This avoids building up directories with too many entries, as would
happen if the Beaker instance is running lots of jobs but no archive
server is configured.

Change-Id: I3106b2f12189b28656610cf30f127f143c402580
Merge "Adjust single processor ordering to only consider bare metal systems." into release-0.12
Merge "show status as "Updating..." if job is dirty" into release-0.12
Merge "tests: fix for c17d4b52" into release-0.12
Merge "split LC log storage into subdirs of 1000" into release-0.12
filter out dirty jobs in beakerd loops

A recipe may be aborted at various stages of processing in beakerd (for
example, no matching systems in process_new_recipe, or an exception in
schedule_queued_recipe). In that case the recipe status won't actually
change until update_dirty_jobs does its thing. So the other beakerd
loops need to exclude dirty jobs otherwise they may end up trying to
abort the same recipe over and over.

Change-Id: Ifd4bcbf9738c201c75751d77421fb8a67bb33a0d
Merge "filter out dirty jobs in beakerd loops" into release-0.12
fix <hypervisor/> to preclude oVirt

Putting <hypervisor value="" /> in a recipe's hostRequires should
prevent it from being run on an oVirt guest, but that wasn't working due
to this surprising little gotcha:

    >>> 'KVM'.__eq__(None)
    NotImplemented
    >>> bool('KVM'.__eq__(None))
    True
    >>> operator.__eq__('KVM', None)
    False

Change-Id: Id45d1dd45141d5e7ff8d1ddb7be9da09413fe3b6
beaker-expire-distros: distinguish missing trees from server errors

Change-Id: Id76f09b6adc7dcd81383b59eb204b12aedbd7036
beaker-expire-distros: fix handling nfs+iso URLs

    Error checking for existence of URL nfs+iso://example.com:/srv/pub/RHEL-7.0-20120711.2-Server-x86_64-iso/ for distro tree 958:
    Cannot access NFS server o or autofs not running (/net/o does not exist)

Change-Id: I3b833ba1e88447e6cebd02ec310c2b4efb5afc32
Merge "fix <hypervisor/> to preclude oVirt" into release-0.12
Add 'System/LoanComment' column for search results

Change-Id: Ica4a77e40ae0784b9c25fb393533397539f31b4a
Merge "Add 'System/LoanComment' column for search results" into release-0.12
Merge changes I3b833ba1,Id76f09b6 into release-0.12

* changes:
  beaker-expire-distros: fix handling nfs+iso URLs
  beaker-expire-distros: distinguish missing trees from server errors