Skip to content

Commit

Permalink
Removed spacewalk-koan from the list of required packages (#3571)
Browse files Browse the repository at this point in the history
* Removed spacewalk-koan from the list of required packages
SUSE/spacewalk#26118
uyuni-project/uyuni#8905
* differentiate between plain salt and salt bundle
  • Loading branch information
keichwa committed Jan 6, 2025
1 parent d8f3e14 commit 04c7c73
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 13 deletions.
3 changes: 2 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
- Added external link for creating virtual network peer for Azure in
- Updated Troubleshooting Autoinstallation in Administration Guide
- Added external link for creating virtual network peer for Azure in
Specialized Gudes (bsc#1234441)
- Clarified SSH authentication methods during Web UI bootstrap process in
Client Configuration Guide (bsc#1233497)
Expand Down
Original file line number Diff line number Diff line change
@@ -1,17 +1,12 @@
[[troubleshooting-autoinstallation]]
= Troubleshooting Autoinstallation

Depending on your base channel, new autoinstallation profiles might be subscribed to a channel that is missing required packages.
If you use the plain {salt} (salt-minion) implementation for communication, you on your own must make sure that all the needed software (software packages) is properly available in configured client channels.
It is not recommended to use this implementation together with {productname}.

For autoinstallation to work, these packages are required:
With the default {salt} bundle (venv-salt-minion) implementation you only need a client tools channel as a child channel that is compatible with your client base channel.
All required packages will be part of the {salt} bundle.

* [package]``pyOpenSSL``
* [package]``rhnlib``
* [package]``libxml2-python``
* [package]``spacewalk-koan``

To resolve this issue, check these things first:

* Check that the tools software channel related to the base channel in your autoinstallation profile is available to your organization and your user.
* Check that the client tools software channel related to the base channel in your autoinstallation profile is available to your organization and your user.
* Check that the tools channel is available to your {productname} as a child channel.
* Check that the required packages and any dependencies are available in the associated channels.:
* Only if using the plain {salt} (salt-minion) implementation, also check that the required packages and any dependencies are available in the associated channels.
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ It is also possible to use the Salt Bundle on systems that run a {salt} Minion c
The registration method with the Salt Bundle is the recommended registration method.
This section explains the advantages and limitations of the current implementation.

The Salt Bundle is provided as the [package]``venv-salt-minion`` that consists of {salt}, Python 3, and the Python modules {salt} depends on.
The Salt Bundle is provided as the [package]``venv-salt-minion`` package that consists of {salt}, Python 3, and the Python modules {salt} depends on.

Bootstrapping with {webui} is using Salt Bundle as well, so bootstrapping with {webui} is not Python dependant.
Using the Salt Bundle, it is no longer needed that the client provides any Python interpreter or modules.
Expand Down

0 comments on commit 04c7c73

Please sign in to comment.