Mocks utils.execute_with_timeout for mongodb tests

The mongodb test_prepare_from_backup unit test doesn't
mock utils.execute_with_timeout causing it to prompt
for a password and/or hang.

Change-Id: I22d839f9bbd6faf97bba16616e7f2cbcf725ab1e
Closes-Bug: 1353570
recent audit log change broke this LOG.debug message

My recent change to this file as part of the audit logging changes
(b668e85c) introduced this error.

Change-Id: If540d94432835f7f28817b00a39c5c704cb71813
Closes-Bug: #1354107
Merge "Mocks utils.execute_with_timeout for mongodb tests"
Correct monkey patching in GuestAgentBackupTest

This change addresses some intermittent failures in tests that we've
been seeing recently.

The failure would typically manifest itself in
test_prepare_from_backup test in test_mongodb_manager.py but in theory
it could occur elsewhere. The good thing about this change is that it
will make the intermittent failures persistent. But, thanks to the fix
for bug 1353570 (change I22d839f) the failures won't happen any
longer.

This change, without the earlier change for bug 1353570 did in fact
serve to make the intermittent failures permanent. The issue is that
GuestAgentBackupTest didn't unpatch execute_with_timeout when it was
done. This meant that tests running after it were running in an
environment where execute_with_timeout was patched. But, just in case
you had a test which didn't itself patch execute_with_timeout and it
happened to run on a thread that hadn't run GuestAgentBackupTest,
you'd get a bad result.

The fix is to include code to save and restore execute_with_timeout in
setUp and tearDown.

Change-Id: I60187145d25524b4e7614d5d8cce9027521db44c
Closes-Bug: #1347337
Merge "recent audit log change broke this LOG.debug message"
Adjusted audit logging for taskmanager module

The taskmanager module audit log messages are unclear, some debug
messages are supposed to be info and vice versa.

Changed logging of various messages to conform to standard.

Change-Id: Idaa46b67096c1fbbacdf730c06c823aaf3e1e255
Partial-Bug: #1324206
Update 'list_users' call to use AGENT_HIGH_TIMEOUT

The list_users call in the guestagent takes about 0.4s - 0.5s per
user, and currently uses the AGENT_LOW_TIMEOUT. This means that it's
possible for the call to easily time out if there are ~11-12 users
on the guest.

This has been causing a lot of false negative failures in the
int-tests, so this updates the 'list_users' call to use the
AGENT_HIGH_TIMEOUT instead of the AGENT_LOW_TIMEOUT.

Closes-bug: 1356085
Change-Id: I589baa0e95febfb63538b79a082cc3dc55f66510
Merge "Adjusted audit logging for taskmanager module"