I think this might actually be a problem in puppet-tripleo (or elsewhere). There is no mention of the "tripleo-bootstrap" role being executed and the playbook would be outputting task information such as "Ensure network service is enabled". It looks like a Bash script is written to a temporary file that is hardcoded to enable the network service.
```
2019-11-04 18:28:17.214 | dib-run-parts 51-disable-libvirtd-service completed
2019-11-04 18:28:17.214 | dib-run-parts Running /tmp/in_target.d/post-install.d/51-enable-network-service
2019-11-04 18:28:17.217 | + set -o pipefail
2019-11-04 18:28:17.217 | + systemctl enable network
2019-11-04 18:28:17.222 | network.service is not a native service, redirecting to systemd-sysv-install.
2019-11-04 18:28:17.222 | Executing: /usr/lib/systemd/systemd-sysv-install enable network
2019-11-04 18:28:17.224 | failed to glob pattern /etc/rc0.d/[SK][0-9][0-9]network: No such file or directory
```
I think this might actually be a problem in puppet-tripleo (or elsewhere). There is no mention of the "tripleo-bootstrap" role being executed and the playbook would be outputting task information such as "Ensure network service is enabled". It looks like a Bash script is written to a temporary file that is hardcoded to enable the network service.
``` libvirtd- service completed target. d/post- install. d/51-enable- network- service sysv-install. systemd/ systemd- sysv-install enable network d/[SK][ 0-9][0- 9]network: No such file or directory
2019-11-04 18:28:17.214 | dib-run-parts 51-disable-
2019-11-04 18:28:17.214 | dib-run-parts Running /tmp/in_
2019-11-04 18:28:17.217 | + set -o pipefail
2019-11-04 18:28:17.217 | + systemctl enable network
2019-11-04 18:28:17.222 | network.service is not a native service, redirecting to systemd-
2019-11-04 18:28:17.222 | Executing: /usr/lib/
2019-11-04 18:28:17.224 | failed to glob pattern /etc/rc0.
```