From 3d30e7f4df816fd6b4fb9a78ebefeafa6e5098a0 Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 19 Jun 2024 11:12:52 +0200 Subject: [PATCH 01/12] Added a fix for BSC#1226285. --- xml/aarch64_inst_problem.xml | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/xml/aarch64_inst_problem.xml b/xml/aarch64_inst_problem.xml index 272a85b502..9ec0df37b9 100644 --- a/xml/aarch64_inst_problem.xml +++ b/xml/aarch64_inst_problem.xml @@ -104,6 +104,36 @@ + + Remote Installation using an IPMI console + + When installing remotely using an IMPI console, you may face problems with the installation. + To fix the problems and install &productnameshort;, proceed as follows: + + + + + Press e to enter the GRUB menu. + + + + + Replace splash=silent with ConsoleDevice=/dev/tty1. + + + + + Continue to boot with x or F10. The installer + will start in the terminal on F1. + + + + + When installing &productnameshort; using &pxename; network boot, add the following parameter + to the kernel parameter list: + + console=tty + From ac8c2af9a9265c0c4f0343a8340088cef2529382 Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 26 Jun 2024 13:30:09 +0200 Subject: [PATCH 02/12] Applied reviewers comment. --- xml/aarch64_inst_problem.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xml/aarch64_inst_problem.xml b/xml/aarch64_inst_problem.xml index 9ec0df37b9..300f00b308 100644 --- a/xml/aarch64_inst_problem.xml +++ b/xml/aarch64_inst_problem.xml @@ -113,7 +113,7 @@ - Press e to enter the GRUB menu. + Press e during start of the installer to enter the GRUB menu. From 8c27aeec892e5c221836aa677c8112d2acbd9f78 Mon Sep 17 00:00:00 2001 From: lvicoun Date: Wed, 26 Jun 2024 14:05:11 +0200 Subject: [PATCH 03/12] Apply suggestions from code review Co-authored-by: Daria Vladykina --- xml/aarch64_inst_problem.xml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/xml/aarch64_inst_problem.xml b/xml/aarch64_inst_problem.xml index 300f00b308..3d02bafb02 100644 --- a/xml/aarch64_inst_problem.xml +++ b/xml/aarch64_inst_problem.xml @@ -105,15 +105,15 @@ - Remote Installation using an IPMI console + Remote installation using an IPMI console - When installing remotely using an IMPI console, you may face problems with the installation. + When installing remotely using an IPMI console, you may face problems with the installation. To fix the problems and install &productnameshort;, proceed as follows: - Press e during start of the installer to enter the GRUB menu. + Press e during the start of the installer to enter the GRUB menu. @@ -123,8 +123,7 @@ - Continue to boot with x or F10. The installer - will start in the terminal on F1. + Continue to boot with x or F10. Press F1 to launch the installer in a terminal window. From 9e313f0371489e4a0f5b9c1de3ce8ef35e843e23 Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 26 Jun 2024 13:55:59 +0200 Subject: [PATCH 04/12] Fixed BSC#1226206. --- xml/ay_erb_templates.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xml/ay_erb_templates.xml b/xml/ay_erb_templates.xml index f944229698..e2c5819eb0 100644 --- a/xml/ay_erb_templates.xml +++ b/xml/ay_erb_templates.xml @@ -404,14 +404,14 @@ Configure the connected network cards <interfaces t="list"> - <% with_link = netword_cards.sort_by { |n| n[:name] }.find { |n| n[:link] } %> + <% with_link = network_cards.sort_by { |n| n[:name] }.find { |n| n[:link] } %> <% if with_link %> <interface> <device><%= with_link[:device] %></device> <startmode>auto</startmode> <bootproto>dhcp</bootproto> </interface> - <% end > + <% end %> </interfaces> From a1d40200b6dcd782d65c7bc342d096fadad90f22 Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 26 Jun 2024 12:40:22 +0200 Subject: [PATCH 05/12] Fix for BSC#1218070. --- xml/storage_filesystems.xml | 99 +++++++++++++++++++++---------------- 1 file changed, 56 insertions(+), 43 deletions(-) diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index b9b36d86c8..3aa591c104 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2109,12 +2109,12 @@ The file system has the following characteristics: - - - ufs - - - + - + - + - ufs + - + - + - Used by BSD, SunOS and NextStep. Only supported in read-only mode. @@ -2166,36 +2166,7 @@ The file system has the following characteristics: mount: /mnt/mx: unknown filesystem type 'minix' (hint: possibly blacklisted, see mount(8)). - - To enable the mounting of the file system, you need to remove the particular - file system from the blocklist. Each blocked file system has its own - configuration file, for example, for efs it is - /lib/modules.d/60-blacklist_fs-efs.conf. However, do - not edit these files, as they are overwritten whenever the package - suse-module-tools is updated. To allow automatic mounting - of the blocked file system, you have the following options: - - - - - - Create a symbolic link to /dev/null, for example, for - the efs file system: - -&prompt.sudo;ln -s /dev/null /etc/modules.d/60-blacklist_fs-efs.conf - - - - Copy the configuration file to /etc/modprobe.d: - -&prompt.sudo;cp /lib/modules.d/60-blacklist_fs-efs.conf /etc/modprobe.d/60-blacklist_fs-efs.conf - - And comment the following statement in the configuration file: - -# blacklist omfs - - - + Even though a file system cannot be mounted automatically, you can load the corresponding kernel module for the file system directly using @@ -2213,13 +2184,55 @@ The file system has the following characteristics: unblacklist: loading cramfs file system module unblacklist: Do you want to un-blacklist cramfs permanently (<y>es/<n>o/n<e>ver)? y unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-cramfs.conf - - - If you select yes, the modprobe - command calls a script that creates a symbolic link from the configuration - file of the provided file system to /dev/null. Thus, - the file system is removed from the blocklist. - + + Here you have the following options: + + + + yes + + + The module will be loaded and removed from the blakclist. Therefore, the module will be + loaded automatically when mounted in future without any other prompt. + + + The onfiguration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + created. Remove the file to undo the changes you performed. + + + + + no + + + The module will be loaded, but it is not removed from the blacklist. Therefore, on a next + module loading + you will see the prompt above again. + + + + + ever + + + The module will be loaded, but autoloading is disabled even for future and the prompt will + not be displayed anymore. + + + The onfiguration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + created. Remove the file to undo the changes you performed. + + + + + c + + + To interrup the module loading. + + + + Large file support in Linux From 350c63e5aa5e7a28831521dc80f9d66a5be434ce Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 26 Jun 2024 12:45:04 +0200 Subject: [PATCH 06/12] Fixed a typo. --- xml/storage_filesystems.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index 3aa591c104..824a8841a2 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2192,8 +2192,8 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c yes - The module will be loaded and removed from the blakclist. Therefore, the module will be - loaded automatically when mounted in future without any other prompt. + The module will be loaded and removed from the blacklist. Therefore, the module will be + loaded automatically in future without any other prompt. The onfiguration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is From 2ab167824142d09cf5e68e90af72a8bc4605b2c9 Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Wed, 26 Jun 2024 13:07:35 +0200 Subject: [PATCH 07/12] Validation fixes. --- xml/storage_filesystems.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index 824a8841a2..32025eaf1e 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2109,12 +2109,12 @@ The file system has the following characteristics: - - - - - - ufs - - - - - - + + + ufs + + + Used by BSD, SunOS and NextStep. Only supported in read-only mode. From 2999c65e36747c4d45fb4788dabc9c22f1a0fd65 Mon Sep 17 00:00:00 2001 From: lvicoun Date: Wed, 26 Jun 2024 14:53:45 +0200 Subject: [PATCH 08/12] Apply suggestions from code review Co-authored-by: Martin Wilck --- xml/storage_filesystems.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index 32025eaf1e..3242a4cb6a 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2196,7 +2196,7 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c loaded automatically in future without any other prompt. - The onfiguration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + The configuration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is created. Remove the file to undo the changes you performed. @@ -2219,7 +2219,7 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c not be displayed anymore. - The onfiguration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is + The configuration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is created. Remove the file to undo the changes you performed. @@ -2228,7 +2228,7 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c c - To interrup the module loading. + To interrupt the module loading. From 72d1b7b419612a94d3b869d3fb60521636b0c05d Mon Sep 17 00:00:00 2001 From: lvicoun Date: Thu, 27 Jun 2024 10:15:11 +0200 Subject: [PATCH 09/12] Apply suggestions from code review Co-authored-by: Daria Vladykina --- xml/storage_filesystems.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xml/storage_filesystems.xml b/xml/storage_filesystems.xml index 3242a4cb6a..969335c69f 100644 --- a/xml/storage_filesystems.xml +++ b/xml/storage_filesystems.xml @@ -2215,8 +2215,8 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c ever - The module will be loaded, but autoloading is disabled even for future and the prompt will - not be displayed anymore. + The module will be loaded, but autoloading is disabled even for future use, and the prompt + will no longer be displayed. The configuration file /etc/modprobe.d/60-blacklist_fs-${MODULE}.conf is @@ -2228,7 +2228,7 @@ unblacklist: cramfs un-blacklisted by creating /etc/modprobe.d/60-blacklist_fs-c c - To interrupt the module loading. + This option is used to interrupt the module loading. From db50873b6acf8237ce74516d8bff98968a3a8a10 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Ba=C5=BEant?= Date: Thu, 27 Jun 2024 12:56:17 +0200 Subject: [PATCH 10/12] Added a new use-case for recreating initramfs (#1735) * Added new usecase for recreatign initramfs * Apply suggestions from code review Co-authored-by: Daria Vladykina --- xml/bootconcept.xml | 45 ++++++++++++++++----------------------------- 1 file changed, 16 insertions(+), 29 deletions(-) diff --git a/xml/bootconcept.xml b/xml/bootconcept.xml index c91d642ae5..2daae22774 100644 --- a/xml/bootconcept.xml +++ b/xml/bootconcept.xml @@ -278,41 +278,13 @@ when you need to regenerate an initramfs manually: - - - - - - - - - - - - - - - - - - - - - - - - - - Adding drivers because of hardware changes - If you need to change hardware (for example, hard disks), and this + If you need to change hardware, for example, hard disks, and this hardware requires different drivers to be in the kernel at boot time, you must update the initramfs file. @@ -383,6 +355,21 @@ + + Adding or removing swap devices, re-creating swap area + + + Whenever you add or remove a swap device, or re-create a swap area + with a different UUID, update the initramfs as + outlined in . You may also + need to update variables that + include the option in + /etc/default/grub, and then regenerate + /boot/grub2/grub.cfg as outlined in . + + + From e06fca9f4b34e7b709b708e29a527b28583b1d2f Mon Sep 17 00:00:00 2001 From: Tom Schraitle Date: Wed, 26 Jun 2024 16:09:06 +0200 Subject: [PATCH 11/12] Update GHA * actions/checkout@v3 -> actions/checkout@v4 * actions/download-artifact@v3 -> actions/download-artifact@v4 * actions/upload-artifact@v3 -> actions/upload-artifact@v4 For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/ (cherry picked from commit 7d026802664e5cc736f093211d9b5d2ca7642e19) --- .github/workflows/docbook.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/docbook.yml b/.github/workflows/docbook.yml index 956b3d2471..31830f2fc6 100644 --- a/.github/workflows/docbook.yml +++ b/.github/workflows/docbook.yml @@ -21,7 +21,7 @@ jobs: allow-build: ${{ steps.select-dc-build.outputs.allow-build }} relevant-branches: ${{ steps.select-dc-build.outputs.relevant-branches }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Checking basic soundness of DC files uses: openSUSE/doc-ci@gha-select-dcs @@ -50,7 +50,7 @@ jobs: matrix: dc-files: ${{ fromJson(needs.select-dc-files.outputs.validate-list) }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Validating DC file(s) ${{ matrix.dc-files }} uses: openSUSE/doc-ci@gha-validate with: @@ -68,14 +68,14 @@ jobs: matrix: dc-files: ${{ fromJson(needs.select-dc-files.outputs.build-list) }} steps: - - uses: actions/checkout@v3 + - uses: actions/checkout@v4 - name: Building DC file(s) ${{ matrix.dc-files }} id: build-dc uses: openSUSE/doc-ci@gha-build with: dc-files: ${{ matrix.dc-files }} - name: Uploading builds as artifact - uses: actions/upload-artifact@v3 + uses: actions/upload-artifact@v4 with: name: ${{ steps.build-dc.outputs.artifact-name }} path: ${{ steps.build-dc.outputs.artifact-dir }}/* @@ -89,7 +89,7 @@ jobs: continue-on-error: true steps: - name: Downloading all build artifacts - uses: actions/download-artifact@v3 + uses: actions/download-artifact@v4 with: path: artifact-dir - name: Publishing builds on susedoc.github.io From 911b039ef75ad4345bbe153199f995e6e9b7128f Mon Sep 17 00:00:00 2001 From: Jana Halackova Date: Mon, 1 Jul 2024 17:21:36 +0200 Subject: [PATCH 12/12] Fix for BSC#1223355. --- xml/deployment_images_ignition.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xml/deployment_images_ignition.xml b/xml/deployment_images_ignition.xml index 562faeaff0..96a2bbf305 100644 --- a/xml/deployment_images_ignition.xml +++ b/xml/deployment_images_ignition.xml @@ -141,8 +141,7 @@ The storage attribute is used to configure partitions, RAID, define file systems, create files, etc. To define partitions, use the disks attribute. The - filesystem attribute is used to format partitions - and define mount points of particular partitions. The + filesystem attribute is used to format partitions. The files attribute can be used to create files in the file system. Each of the mentioned attributes is described in the following sections. @@ -286,6 +285,13 @@ storage: The <literal>filesystem</literal> attribute + + &ignition; does not perform modifications to mount units + + The file system attribute does not modify mount units. If you add a new partition or remove an + existing partition, you must manually adjust the mount units. + + filesystem must contain the following attributes: