Building ubuntu-xenial image with diskimage-builder (https://git.openstack.org/openstack/diskimage-builder.git at tag 1.26.1) and element os-collect-config from tripleo-image-elements (https://git.openstack.org/openstack/tripleo-image-elements.git at tag 5.2.0) creates a systemd service file with the following contents:
$ cat /lib/systemd/system/os-collect-config.service
[Unit]
Description=Collect metadata and run hook commands.
After=cloud-final.service
Before=crond.service
[Service]
ExecStart=/usr/local/bin/os-collect-config
Restart=on-failure
[Install]
WantedBy=multi-user.target
$
resulting in dependency cycle:
systemd[1]: multi-user.target: Found ordering cycle on multi-user.target/start
systemd[1]: multi-user.target: Found dependency on os-collect-config.service/start
systemd[1]: multi-user.target: Found dependency on cloud-final.service/start
systemd[1]: multi-user.target: Found dependency on multi-user.target/start
systemd[1]: multi-user.target: Breaking ordering cycle by deleting job os-collect-config.service/start
systemd[1]: os-collect-config.service: Job os-collect-config.service/start deleted to break ordering cycle starting with multi-user.target/start
Thus it's never started by systemd.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE