As become is applied to most of the tasks in the role, let's remove
them and suggest applying become on the playbook level instead.
We do not have become applied on task level in any other managed
role.
This also helps to workaround PAM/apparmor issue with CentOS
in Docker for molecule test.
We also deal with an intermittent failures in Docker, as interface
naming/ordering is random and non-deterministic with no way of
controlling it.
Thus, instead of detecting an IP address by interface, we hardcode the
IP address both for containers and in FRR configurations.
Change-Id: I73471dd895eea5c6abfbec24681c796d5e7d813d
In case of configuration changes it's better to reload FRR rather then
perform restart. Actions towards FRR lead to networking downtime until
connection is established and required routes reconciled.
To reduce the downtime let's reload FRR in case of simple config changes
Change-Id: I83746f3a101dc0f678a4a82d02160fc1fa8d8e52
According to RFC-8212 policies must be described in order to allow
announce/accept routes. Without policies being described, no routes
will be announced/recieved by default.
This patch fixes current CI failures.
Change-Id: Ia033cc7c3ed3146860ab96452bec988f3c3069bf
