Support for Ignition files version 3.4.0

Hello, as I’m trying to move a bigger installation from CoreOS to MicroOS and there is the following question. is support for ignition files with version 3.4.0 (https://coreos.github.io/ignition/migrating-configs/#from-version-330-to-340) created for example with butane 1.5.0 (https://coreos.github.io/butane/upgrading-fcos/#from-version-140-to-version-...) planned, especially the luks discard and open options are essential for our use case. Docu of MicroOS for ignition https://en.opensuse.org/Portal:MicroOS/Ignition an example butane file that should work since it works with CoreOS: variant: fcos version: 1.5.0 passwd: users: - name: core groups: - "sudo" - "docker" ssh_authorized_keys_local: - id_ed25519_fcos_user_core.pub storage: disks: - device: /dev/vda partitions: - label: root number: 4 # 0 means to use all available space size_mib: 0 resize: true luks: - name: root label: luks-root device: /dev/disk/by-partlabel/root key_file: local: luks.key wipe_volume: true discard: true options: - --pbkdf=argon2id open_options: - --perf-no_read_workqueue - --perf-no_write_workqueue filesystems: - device: /dev/mapper/root format: xfs wipe_filesystem: true label: root

Hi, Am 16.08.23 um 11:29 Uhr schrieb abkantung.fuechse_0t@icloud.com:
openSUSE MicroOS contains the current Ignition version 2.16.2, so yes, the 3.4.0 spec is supported.
One point that immediately caught my eye: On openSUSE MicroOS it is required to add the /home filesystem to the configuration file explicitly when adding a new user, see https://en.opensuse.org/Portal:MicroOS/Ignition#Create_new_users for an example snippet. Ignaz -- Ignaz Forster <iforster@suse.com> Research Engineer SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

Just an addendum: I tested your configuration and it seems our initrd is missing several components regarding luks support. I'll have another look at it tomorrow. Kind Regards, Ignaz Am 16.08.23 um 11:29 Uhr schrieb abkantung.fuechse_0t@icloud.com:
-- Ignaz Forster <iforster@suse.com> Research Engineer SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

Thanks for taking a look at it. Are there any further insights or can I help somehow?

Hi, a new Ignition package was released a few days ago (for openSUSE Tumbleweed & MicroOS), containing several fixes regarding LUKS support. With these your configuration file should be working as it is now, with two exceptions: * XFS is not supported out of the box, i.e. the initrd does not contain mkfs.xfs by default. It would work with our default images if you would change the file system to btrfs. * As mentioned in my first response already: For adding users you will also need to add the /home partition to the configuration (see e.g. https://documentation.suse.com/sle-micro/5.1/html/SLE-Micro-all/cha-images-i...) Unfortunately another bug currently prevents Ignition from finishing successfully, but as soon as https://build.opensuse.org/request/show/1109552 is released it should be working. Kind Regards, Ignaz Am 08.09.23 um 14:57 Uhr schrieb Fabi D:
Thanks for taking a look at it. Are there any further insights or can I help somehow?
-- Ignaz Forster <iforster@suse.com> Research Engineer SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

Hi, thanks for the hints regarding xfs and home directory. Do you have more details on "Ignition package was released a few days ago". Where can I find it? Or read about it?

Am 11.09.23 um 15:22 Uhr schrieb Fabi D:
The updated Ignition package is part of Tumbleweed / MicroOS already. If you download an updated image (or update an existing system) you will receive the new version. It seems the new snapshot 20230910 (announced 1½ hours ago on this very mailing list) also contains the updated Combustion package I was talking about in my previous mail, so if you download the current official image you should be good to go! In general, because you asked: If you want to try any package manually you can go to it's devel project (https://build.opensuse.org/package/show/devel:kubic:ignition/ignition in this case) and use "Download package". The Changelog will be contained in the file <package>.changes (ignition.changes in this case). However, with Ignition and Combustion being firstboot mechanisms, a manual package download probably won't help you too much. You might want to download the images generated by the openQA tests (e.g. on https://openqa.opensuse.org/tests/3560253#downloads - you will find the link to the actual Staging project in the submit request) instead if you want to be a very early adaptor :-) In any case: The starting point of everything is the devel project of the package in OBS - be it test packages, the current status or looking at the most recent changes. Ignaz -- Ignaz Forster <iforster@suse.com> Research Engineer SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

Thanks for the help. A test run with the ContainerHost-SelfInstall iso shows that the following butane file does not go through with the error. " [ 696.4770431 dracut-pre-trigger18201: Failed to send request to update environment: No such file or directory 698.62534310 T18471 ETRFS: device label ROOT devid 1 transid 97 deursda3 scanned by ludey-worker) (1847) " Any help is appreciated. butane (also configuring home next to the other device throws an error in the butane to ignition file step): variant: fcos version: 1.5.0 passwd: users: - name: core groups: - "sudo" - "docker" # ssh_authorized_keys_local: # - id_ed25519_fcos_user_core.pub password_hash: $y$j9T$vrCC7VE5KE2iDPgrhkHVf.$ixL1H2IU3V5pE6u6C3oOQLaTm1MH7RNETrm/N7mGX0A storage: disks: - device: /dev/vda partitions: - label: root number: 4 # 0 means to use all available space size_mib: 0 resize: true luks: - name: root label: luks-root device: /dev/disk/by-partlabel/root key_file: local: luks.key wipe_volume: true discard: true options: - --pbkdf=argon2id open_options: - --perf-no_read_workqueue - --perf-no_write_workqueue filesystems: - device: /dev/mapper/root format: btrfs wipe_filesystem: true label: root # - path: /home # format: btrfs # wipe_filesystem: false # mount_options: # - "subvol=/@/home"

Am 12.09.23 um 16:46 Uhr schrieb Fabi E:
At least at first glance these messages don't seem to be related. Are there any other messages, or let me turn the question around: How do you realize that applying the configuration was not successful? Do you end up in a dracut emergency shell? If so, then you can look for Ignition specific log output with `journalctl`. You should find the exact error there.
Kind Regards, Ignaz
Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)
participants (4)
-
abkantung.fuechse_0t@icloud.com
-
Fabi D
-
Fabi E
-
Ignaz Forster