Merge pull request #4383 from uyuni-project/1248803-m-fileChange

Fixed command for bootstrap repository

Author: 0rnela

CHANGELOG.md

@@ -1,3 +1,5 @@
+- Fixed instruction and command in Client Configuration Guide
+  (bsc#1248803) 
 - Added openSUSE Tumbleweed support for Uyuni
 - Documented the new autoinstallation snippets (bsc#1194792)
 - Improved the appearance of Web UI instructions in Administration

modules/client-configuration/pages/bootstrap-repository.adoc

@@ -1,13 +1,13 @@
 [[client-cfg-tools-repository]]
-= Bootstrap Repository
+= Bootstrap repository
 :revdate: 2025-02-06
 :page-revdate: {revdate}
 
 A bootstrap repository contains required packages for registering clients during bootstrapping.
 When products are synchronized, bootstrap repositories are automatically created and regenerated on the {productname} Server.
 
 
-== Prepare to Create a Bootstrap Repository
+== Prepare to create a bootstrap repository
 
 
 When you select a product for synchronization, the bootstrap repository is automatically created as soon as all mandatory channels are fully mirrored.
@@ -28,12 +28,12 @@ include::snippets/check_sync_cli.adoc[]
 
 
 
-== Options for Automatic Mode
+== Options for automatic mode
 
 You can change how the automated bootstrap repository creation works.
 This section details the various settings.
 
-Flush Mode::
+Flush mode::
 By default, existing repositories are updated only with the latest packages.
 You can configure it to always start with an empty repository instead.
 To enable this behavior, add or edit this value in [path]``/etc/rhn/rhn.conf``:
@@ -42,7 +42,7 @@ To enable this behavior, add or edit this value in [path]``/etc/rhn/rhn.conf``:
 server.susemanager.bootstrap_repo_flush = 1
 ----
 
-Automatic Mode::
+Automatic mode::
 
 By default, automated regeneration of the bootstrap repositories is enabled.
 To disable it, add or edit this value in [path]``/etc/rhn/rhn.conf``:
@@ -53,17 +53,16 @@ server.susemanager.auto_generate_bootstrap_repo = 0
 
 
 
-=== Configure Bootstrap Data File
+=== Configure bootstrap data file
 
 The tool uses a data file with information about which packages are required for each distribution.
 The data file is stored at [path]``/usr/share/susemanager/mgr_bootstrap_data.py``.
 {suse} updates this file regularly.
 If you want to makes changes to this file, do not edit it directly.
-Instead, create a copy in the same directory and edit your copy:
+Instead, create a copy in persistent directory and edit your copy:
 
 ----
-cd /usr/share/susemanager/
-cp mgr_bootstrap_data.py my_data.py
+cp /usr/share/susemanager/mgr_bootstrap_data.py /srv/susemanager/my_data.py
 ----
 
 When you have made your changes, configure {productname} to use the new file.
@@ -81,27 +80,38 @@ You need to keep the new file up to date with changes provided by {suse}.
 
 
 
-== Manually Generate a Bootstrap Repository
+== Manually generate a bootstrap repository
 
 By default, bootstrap repositories are regenerated daily.
 You can manually create the bootstrap repository from the command prompt.
 
 
 
-.Procedure: Generating the Bootstrap Repository for {sle}
+.Procedure: Generating the bootstrap repository for {sle}
+[role=procedure]
+_____
+
 . At the command prompt on the {productname} Server, as root, list the available distributions to create bootstrap repositories for:
+
 +
+
 ----
 mgr-create-bootstrap-repo -l
 ----
+
 . Create the bootstrap repository, using the appropriate repository name as the product label:
+
 +
+
 ----
 mgr-create-bootstrap-repo -c SLE-version-x86_64
 ----
+
 +
+
 . Alternatively, use the number shown next to the distribution name in the list of available distributions.
 
+_____
 
 The client repository is located in [path]``/srv/www/htdocs/pub/repositories/``.
 
@@ -114,9 +124,14 @@ Use this procedure only if your environment requires it.
 
 
 
-.OPTIONAL Procedure: Specifying a Parent Channel for a Bootstrap Repository
+.OPTIONAL Procedure: Specifying a parent channel for a bootstrap repository
+[role=procedure]
+_____
+
 . Check which parent channels you have available:
+
 +
+
 ----
 mgr-create-bootstrap-repo -c SLE-15-x86_64
 Multiple options for parent channel found. Please use option
@@ -125,15 +140,19 @@ Multiple options for parent channel found. Please use option
 - sle-product-sles_sap15-pool-x86_64
 - sle-product-sled15-pool-x86_64
 ----
+
 . Specify the appropriate parent channel:
+
 +
+
 ----
 mgr-create-bootstrap-repo -c SLE-15-x86_64 --with-parent-channel sle-product-sled15-pool-x86_64
 ----
 
+_____
 
 
-=== Repositories with Multiple Architectures
+=== Repositories with multiple architectures
 
 
 If you are creating bootstrap repositories that include multiple different architectures, you need to be careful that all architectures are updated correctly.
@@ -150,7 +169,7 @@ mgr-create-bootstrap-repo --no-flush -c SLE-15-SP2-s390x
 
 
 
-== Bootstrap and Custom Channels
+== Bootstrap and custom channels
 
 If you are using custom channels, you can use the [option]``--with-custom-channels`` option with the [command]``mgr-create-bootstrap-repo`` command.
 In this case, you also need to specify the parent channel to use.