public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2] If expand last partition fails, unsupervised systems reboot
Date: Wed, 14 Dec 2022 10:24:19 +0100	[thread overview]
Message-ID: <CAJGKYO5WBfx9k7Nk4BGCR0z9hRP6Bh2fX8w3B7_jkNTrNqnVag@mail.gmail.com> (raw)
In-Reply-To: <20221214100528.0386e83b@md1za8fc.ad001.siemens.net>

On Wed, 14 Dec 2022 at 10:05, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Wed, 14 Dec 2022 09:47:07 +0100
> schrieb Henning Schild <henning.schild@siemens.com>:
>
> > Patch can not be reviewed so i can as well top-post.
> >
> > We should maybe separate the discussion with the reboot trap and the
> > unsupervised file from the "aligning the nothing to do exit code to 0"
>
> I think it might also be a good idea to set
>
> ExecStopPost=-/bin/systemctl disable expand-on-first-boot.service
>
> in addition to ExecStartPost doing the same. So no matter if we succeed
> or not, we only give it one try. But i did not test that.

if it fails, it is a good thing to retry the next time. Some issues
might depend on boot timing which might be variable. if you want to
test what happens put a "false" as first instruction after set -e and
you will see. In any case the script should be written to be able to
cope with a different behaviour of the systemd between failure and
success because tomorrow we can change that. (reasonable
generalisation).

By the way my patch does not only change the exit 1 with exit 0 but
set a trap on exit to reboot the unsupervised systems to go working in
production without the planned filesystem resize = underprovided =
nasty failures at future unpredictable time. It is easy to revise a
patch that is just a text file attached to an e-mail... LOL

Best, R-

  reply	other threads:[~2022-12-14  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  7:52 Roberto A. Foglietta
2022-12-14  8:47 ` Henning Schild
2022-12-14  9:05   ` Henning Schild
2022-12-14  9:24     ` Roberto A. Foglietta [this message]
2022-12-14  9:26 ` Roberto A. Foglietta

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=CAJGKYO5WBfx9k7Nk4BGCR0z9hRP6Bh2fX8w3B7_jkNTrNqnVag@mail.gmail.com \
    --to=roberto.foglietta@gmail.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