Other people aren't seeing this (yet?), but unless you explicitly exclude v 3.4 of commons-lang3 from the azure build (which
HADOOP-13660 does), then the dependency declaration of commons-lang3 v 3.3.2 is creating a resolution conflict. That's a dependency only needed for the local dynamodb & tests.
I propose to fix this in s3guard by explicitly declaring the version used in the tests to be that of the azure-storage one, excluding that you get for free. It doesn't impact anything shipped in production, but puts the hadoop build in control of what versions of commons-lang are coming in everywhere by way of the commons-config version declared in hadoop-common