Use Your Own GPG Key

If the repositories you are using for autoinstallation have unsigned metadata, you usually have to use the insecure=1 kernel parameter as an option of the autoinstallable distribution, and use a spacewalk/sles_no_signature_checks code snippet in the AutoYaST installation file.

A safer alternative is to provide your own GPG key.

This technique applies to SUSE clients only.
Procedure: Include Your Own GPG Key

  1. Create a GPG key.

  2. Use it to sign the package’s metadata.

  3. Add it to the initial RAM disk of your installation media.

  4. To upload the GPG key to the server use mgrctl gpg upload <PATH_TO_KEY_FILE_OR_URL>. This command calls the Uyuni API to add the key to the customer keyring. Valid administrator credentials are required.

  5. Run command mgradm restart. This command creates a unique keyring using the SUSE and the customer keyring.

When you signed the metadata with your new GPG key, any already onboarded client will not know about the new key. Ideally, you should sign the metadata before you register any client.

For already onboarded clients that use those repositories, the workaround is to disable GPG key checking on them.