This error may appear when LaMachine updates from ansible 2.7 to 2.8, if this occurs, simply rerun the update.