Re: [PATCH 1/1] expand-on-first-boot: Use proper first-boot semantics

[Henning Schild <henning.schild@siemens.com>]

Am Thu, 11 Aug 2022 21:07:23 +0200
schrieb "Schmidl, Tobias (T CED SES-DE)" <tobiasschmidl@siemens.com>:

> Hi Henning,
> 
> Am Donnerstag, dem 11.08.2022 um 20:55 +0200 schrieb Henning Schild:
> >
> > If this does not work on buster and maybe ubuntu versions we might
> > carry, we can not merge this.
> > We will have to find a way to use the old way for buster and the new
> > way for versions that actually do work.
> >
> > Or what does "does not work with buster" actually mean? Will the
> > overall systemd status turn red and the resize fail, or will it be a
> > problem we can consider minor?
> >  
> 
> The `ConditionFirstBoot` is not met, not even on the first boot on the
> system:
> 
> 
> ```
> root@localhost:~# systemctl status --no-pager expand-on-first-boot
> ● expand-on-first-boot.service - Expand last partition
>    Loaded: loaded (/lib/systemd/system/expand-on-first-boot.service;
> enabled; vendor preset: enabled) Active: inactive (dead)
> Condition: start condition failed at Wed 2022-08-10 13:16:50 UTC;
> 1min 5s ago └─ ConditionFirstBoot=true was not met
> ```
> 
> So yes, `expand-on-first-boot` is never executed with this patch on
> buster.

And on top systemd might be unhappy about general health i guess.

Anyhow, Reject! buster is an isar target and has to work.

Henning

> 
> Kind regards,
> 
> Tobias