The main playbook is a bit like a maze at this point, but things happens like:
- playbooks/quickstart.yml includes provision.yml
- provision yaml uses the provision/local role which adds the virthost with the root user: https://github.com/openstack/tripleo-quickstart/blob/master/roles/provision/local/tasks/main.yml#L47
- provision remote does a bunch of stuff, including the tasks you mentioned
- it creates non_root_user on the virthost and readds its to the inventory with the new user
Thus the role runs with root privileges at this point and doesn't require become.
The main playbook is a bit like a maze at this point, but things happens like:
- playbooks/ quickstart. yml includes provision.yml /github. com/openstack/ tripleo- quickstart/ blob/master/ roles/provision /local/ tasks/main. yml#L47
- provision yaml uses the provision/local role which adds the virthost with the root user: https:/
- provision remote does a bunch of stuff, including the tasks you mentioned
- it creates non_root_user on the virthost and readds its to the inventory with the new user
Thus the role runs with root privileges at this point and doesn't require become.