[Bug 2076666] Re: systemd-firstboot.service not running on first boot

[Nick Rosbrook]

As can be seen here, it's skipped because ConditionFirstBoot=yes fails
(i.e. the boot does not meat the "first boot semantics[1][2]).
Essentially, this is determined by /etc/machine-id.

I *believe* on Ubuntu, our images are configured with an empty
/etc/machine-id, so as defined by [2], a "first boot" of an Ubuntu image
will not be considered a "first boot" by ConditionFirstBoot= standards.

I can't speak to the intentions of "first boot" for Ubuntu images, but
this is working as intended from a systemd perspective.

[1] https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#ConditionFirstBoot=
[2] https://www.freedesktop.org/software/systemd/man/latest/machine-id.html#First%20Boot%20Semantics

** Changed in: systemd (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2076666

Title:
  systemd-firstboot.service not running on first boot

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Verified for 24.04 and 24.10 where `systemd-firstboot.service` is
  present. Does not apply to earlier releases.

  ○ systemd-firstboot.service - First Boot Wizard
       Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static)
       Active: inactive (dead)
    Condition: start condition unmet at Mon 2024-08-12 16:19:33 UTC; 9min ago
         Docs: man:systemd-firstboot(1)

  Aug 12 16:19:33 ubuntu systemd[1]: systemd-firstboot.service - First
  Boot Wizard was skipped because of an unmet condition check
  (ConditionFirstBoot=yes).

  Cloud partners have inquired as to whether the inactive behavior is
  intentional - and if not if this is something which will be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2076666/+subscriptions