public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidl, Tobias" <tobiasschmidl@siemens.com>
To: "Schild, Henning" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] expand-on-first-boot: Use proper first-boot semantics
Date: Thu, 11 Aug 2022 19:07:23 +0000	[thread overview]
Message-ID: <4cea2672ae8ff903c6340769d5dbf75801eca9b5.camel@siemens.com> (raw)
In-Reply-To: <20220811205509.2004e2ea@md1za8fc.ad001.siemens.net>

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.

Kind regards,

Tobias

  reply	other threads:[~2022-08-11 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 19:26 [PATCH 0/1] " Tobias Schmidl
2022-08-10 19:26 ` [PATCH 1/1] " Tobias Schmidl
2022-08-11 18:55   ` Henning Schild
2022-08-11 19:07     ` Schmidl, Tobias [this message]
2022-08-11 19:47       ` Henning Schild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4cea2672ae8ff903c6340769d5dbf75801eca9b5.camel@siemens.com \
    --to=tobiasschmidl@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox