Comment 2 for bug 2046483

Reopening this bug as we've now seen a second traceback that is now introduced by upstream commit https://github.com/canonical/cloud-init/commit/36b7f48d71 which also invokes systemctl early in boot and doesn't have the same retry mechanism around it.

The resulting tracebacks are something like

Traceback (most recent call last):
  File "/usr/bin/cloud-init", line 33, in <module>
    sys.exit(load_entry_point('cloud-init==23.4.2', 'console_scripts', 'cloud-init')())
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 1108, in main
    retval = util.log_time(
  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2808, in log_time
    ret = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 140, in handle_status_args
    details = get_status_details(paths, args.wait)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 384, in get_status_details
    boot_status_code, description = get_bootstatus(
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 258, in get_bootstatus
    in subp.subp(["systemctl", "show-environment"]).stdout
  File "/usr/lib/python3/dist-packages/cloudinit/subp.py", line 322, in subp
    raise ProcessExecutionError(
cloudinit.subp.ProcessExecutionError: Unexpected error while running command.
Command: ['systemctl', 'show-environment']
Exit code: 1
Reason: -
Stdout:
Stderr: Failed to connect to bus: Connection refused