alarms: Fix checksum alarm filter.

The filter provided for checksum alarms generated by the pool scrubber
is out of sync with the actual logging statement in the scrubber.

This patch fixes the regex for the filter to match.

Target: master
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
Require-book: no
Require-notes: yes
Acked-by: Karsten
Acked-by: Paul

RELEASE NOTES

Fixes a bug present since April 2013 (but up to now undiscovered by us) preventing
reporting of checksum alarms from the pool scrubber.
srm-client: by default only delegate for srmcp with 3rd-party copies

Currently, the SRM client will delegate for all calls.  This patch
updates the default behaviour so it doesn't delegate, except for
srmcp involving an SRM-endpoint and some remote end-point.

Patch: https://rb.dcache.org/r/7031/
Acked-by: Karsten Schwank
Requires-book: no
Requires-notes: yes
srm: fix status of all-failed container jobs

The status of a container job is updated as a side-effect of running
the ContainerRequest#getRequestStatus method.  Unfortunately, if
all the file requests have failed then a very long, multi-line
status is recorded, which includes a copy of the previous
status.

This patch fixes the status so that, even under these circumstances,
the status line is a short string.

Target: master
Requires-notes: no
Requires-book: no
srm: fix retry and failure messages for scheduled jobs

The state-change history of a job is needlessly verbose, which masks
what was the real problem.

This patch tidies up the output so the underlying message is recorded.

Target: master
Require-notes: no
Require-book: no
Patch: https://rb.dcache.org/dashboard/
Acked-by: Karsten Schwank
srm: make timestamps easier to read

The current format for time-stamps in SRM output follows ISO 8601, but is
needlessly verbose.

The timezone designator is optional: if ommitted, local timezone is assumed.
This only matters if the information is shared across multiple timezones and
the source is ambigous.  Since log files also include the SRM's cell name,
which is unique within a dCache inistance, I believe such ambiguity is
sufficiently unlikely that it doesn't justify the extra three characters in the
output.

According to Wikipedia, ISO 8601 says:

    4.3.2 NOTE: By mutual agreement of the partners in information interchange,
          the character [T] may be omitted in applications where there is no
          risk of confusing a date and time of day representation with others
          defined in this International Standard.

Since (personally) I find the 'T' makes the output harder to read and a single
space easier, this patch removes the 'T' and replaces it with a single space.

I'm not sure if this is in complete agreement with the above note, but I
believe there's no real risk of misinterpretation the fields.

Target: master
Revert "Update to DataNucleus 4"

This reverts commit 5e710729cf24782c596d6a2baf8b5974d7ef51fd.

After above commit, S2 tests started to fail.  The underlying
problem is presented as a org.datanucleus.exceptions.NucleusUserException
with the following message

    Could not create new "sequence" "pin_sequence" since autoCreate
    flags do not allow it.

For the S2 tests, the message is always the same and appears to
originate from pin-manager.

I've reverting this patch at Gerd's request.

04 Jul 2014 12:20:18 (SRM-sisyphus) [131.169.72.210:53318 45M:33:srm2:prepareToGet:-2147482625:-2147482624] Uncaught exception in thread pool-11-thread-9
libs: revet luquibase to 3.1.2

The 3.2.0 version produces incorrect checksums:

https://liquibase.jira.com/browse/CORE-1950

Acked-by: Paul Millar
Target: master
Require-book: no
Require-notes: no