cinder hacking checks don't cover logging format string arg count

[Duncan Thomas]

For example:

LOG.debug("Volume %s caught fire and is at %d degrees C and climbing", (v[name], v[temp]))

The above is easy to code by accident, and the error is trivially recognisable by static analysis (this is done for you by python for %), so hacking should look for it.

A good candidate for the global hacking checks, but a cinder local version is a good start

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/220246

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/220246
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b7fc72c688ab0eaeb4a85a9af3a26428a94854c5
Submitter: Jenkins
Branch: master

commit b7fc72c688ab0eaeb4a85a9af3a26428a94854c5
Author: Derrick J. Wippler <email address hidden>
Date: Thu Sep 3 12:07:19 2015 -0500

    Hacking log format arg check

    Added hacking check for log lines that accidently pass a tuple as the
    second argument when providing format arguments.

    Change-Id: Ifba23948f9fb49e9f6a1ee7e743aba0cd864c827
    Closes-Bug: 1415241