this package can only be run from a bootstrapper

This Package Can Only Be Run From A Bootstrapper Download The Correct
This Package Can Only Be Run From A Bootstrapper Registration Process Successfully

The bootstrap script you create is executed on the client when it is registered, and ensures all the necessary packages are deployed to the client.

There are some parameters contained in the bootstrap script, which ensure the client system can be assigned to its base channel, including activation keys and GPG keys.

This Package Can Only Be Run From A Bootstrapper Download The Correct

If the repository information does not match exactly, the bootstrap script will not be able to download the correct packages.

A bootstrap offers packages for installing Salt on clients and for registering Salt or traditional clients.

For Salt clients running SUSE Linux Enterprise Server 12 or older, you will also require the python-xml package.

Bootstrap scripts based on Python 2 must be re-created for openSUSE Leap 15 and SLE 15 systems.

Attempting to register openSUSE Leap 15 or SLE 15 systems using Python 2 bootstrap scripts will fail.

This Package Can Only Be Run From A Bootstrapper Registration Process Successfully

If you disable SSL nevertheless you will need to manage custom CA certificates to be able to run the registration process successfully.

A minimal requirement when modifying a bootstrap script for use with SUSE Manager is the inclusion of an activation key.

Most packages are signed with GPG, so you will also need to have trusted GPG keys on your system to install them.

Navigate to Home Overview and, in the Tasks box, click Manage Activation Keys.

You must enter the full name of the key you wish to use in the bootstrap script exactly as presented in the key field.

For more information about activation keys, see client-configuration:clients-and-activation-keys.adoc.

You must comment out exit 1 with a hash mark ( ) to activate the script and then enter the name of the key for this script in the ACTIVATIONKEYS field as follows.

At the command prompt, and change to the bootstrap directory.

To review a package EULA, open the package detail page in the Web UI.

The feature is not currently supported on Red Hat Enterprise Linux or Salt clients.

When a package has been locked, it will show a padlock icon, indicating that it can not be installed.

Any attempt to install a locked package will be reported as an error in the event log.

Locked packages will also indirectly lock any dependent packages.

You can also choose to enter a date and time for the lock to activate.

Leave the date and time blank if you want the lock to activate as soon as possible.

Leave the date and time blank if you want the lock to deactivate as soon as possible.