Don't check if beah harness repo exists when alternative harness is used

Bug: 1005865
Change-Id: I004c37ec04c9c0fe5614e720198f3acc94fb0913
add new workflow-installer-test command

Bug: 1026730
Change-Id: I81bd8fb2c72c54e51b251a14ade90bbc5966310d
docs: recommend running bkr watchdogs-extend during upgrades

Change-Id: Idfa58f655ad8002ede4f3455bd25642777bebe0c
added missing TimeoutProxyHTTP and urlparse to bkr.common.xmlrpc

Change-Id: I598858eb87015236b7f51a4746faa7f340de1b58
set power_quiescent_period to 5 when upgrading to 0.16

We are using a Python default rather than a SQL default for this column,
but that means we need to explicitly set the column to its default value
for all existing rows when upgrading.

Bug: 1078620
Change-Id: I3f07b49229c8ab6f864308cc673e2729bc9677fa
tests: attempting to fix timing-sensitivty in test_job_delete

Sometimes the job deletion tests fail because they go to the recipe
page, expecting the recipe to be deleted, but it's not yet. This appears
to be because they are clicking through before the deletion has
completed.

I'm hoping that this patch fixes it by correcting the XPath used to look
for the deleted table row.

Change-Id: I33b7ddd188d572f30cb168f166c5437992201df2
change aarch64 pxedir to keep admins happy.
Fix duplicate packages causing a server fault when submitting a new job

Bug: 883887
Change-Id: Ie3679c9bcea0014f273131cc94b09fd342e20137
rename OSMajor.osversion and OSMajor.osminor properties to OSMajor.osversions

Up until 0.16 we had both OSMajor.osversion and OSMajor.osminor meaning
the same thing (list of OSVersion). During the conversion to SQLAlchemy
declarative in 0.16, OSMajor.osversion was accidentally dropped.

This patch renames them both to OSMajor.osversions, which more
accurately reflects what the property really is.

Bug: 1078941
Change-Id: I90497858c2487ad578fec4673dae8e7b15871a93
access policy editor: "Add" button for explicitly adding new rows

The current behaviour is to add a new row as soon as a typeahead
completion is made. That's problematic because typeahead.js doesn't have
an official way to indicate if a match has been made, and the current
hack does not work when the typed value matches a suggestion that was
not in the prefetch. It is also subject to a race if the user blurs the
input before the typeahead suggestions have been displayed.

With this patch the typeahead is treated purely as a suggestion (which
is the way it is intended to be used), it's up to the user to enter or
select the right value and then click Add or press Enter to add the row
to the policy. If they enter a non-existent user or group we show an
error when they attempt to save the policy.

Change-Id: I4b5284a36d2a6d63748e89494abf854ee86b8dde
define a 'remote' for group typeahead instead of relying on prefetch

If the set of groups in Beaker has changed since it was prefetched, new
groups would never appear in the suggestions even when they were typed.
Now the group typeahead will always fetch fresh suggestions.

Bug: 1076322
Change-Id: I36122bfd6dde2b50394d4962de43bdf5e2bea11f
Revert "change aarch64 pxedir to keep admins happy."

This reverts commit 537ceb0f47636041f7873813100abb7b084e510a.

Change-Id: I96e6c34ce0d192cd3208ea5f9ecff672c32e0c7b
tests: actually test quiescent period is obeyed

The previous version of the test was catching AssertionError, but
TestCase.fail() raises AssertionError so it would always pass.

We can also skip the log inspection in this case.

Change-Id: I644d0dba57db3723087a28f22df55c17c2158412
insert commands into the top of the queue instead of appending

System.command_queue is supposed to be in descending order (most recent
command at the top).

Normally the insertion position makes no difference because we will be
querying System.command_queue back in a separate transaction, which
means it will always end up ordered correctly. This change is only
significant for tests which enqueue commands, expecting them to end up
in the right position in the list.

Change-Id: I69ee2c34535fffd662ea40c00a83b7b785da09f1
obey quiescent period in consecutive power commands

We need to wait for the quiescent period after waiting for all
predecessor commands, otherwise the quiescent period delay will happen
concurrently.

Also record the last command timestamp only when the command has
finished, rather than before it is started, since it may take some time
to complete.

Bug: 1079816
Change-Id: Id4bbf79ae739a669b54ffde0101329f5174424e1
split 'reboot' commands into 'off' and 'on' on the server side

This way the quiescent period will correctly be applied to both the
'off' and 'on' commands. Currently there is no delay between 'off' and
'on' when rebooting.

Bug: 1079603
Change-Id: I907d6f7b6546124769d2b267482345685e779fee
release notes for 0.16.1

Change-Id: Ia9101fd7a883d3407b313d85d384c114cb17a04f
fix handling of release_action in save_power controller

Since commit da6966ce the power config form validator is actually
applied, therefore release_action is now already a valid ReleaseAction
enum value. Calling ReleaseAction.from_string() on it again results in
a ValueError.

Bug: 1080685
Change-Id: Iefda403ac457aa2321d5f9ac37a93f28eb97aec8
add bz1080685 to 0.16.1 release notes
Automatic commit of release 0.16.1