Again, this was acknowledged as a bug by abadger in [1]. It had been
fixed in 2.0, but then regressed again (as expected [2]). As I note in
the GitHub thread, the current behavior makes role variables completely
unreliable and dangerous to use, because if a previous role happens to
include a variable with the same name as a role variable from a later
role, the role variable is ignored.