looks like the problem may have been a bug in ansible 2.2.0.0, so pin to 2.1.3.0
looks like the problem may have been a bug in ansible 2.2.0.0, so pin to 2.1.3.0

internetarchive/brozzler,internetarchive/brozzler,nlevitt/brozzler,internetarchive/brozzler,nlevitt/brozzler,nlevitt/brozzler,nlevitt/brozzler,nlevitt/brozzler,internetarchive/brozzler