SUSE Support

Here When You Need Us

Unable to bootstrap and bootstrap repository is not found

This document (000021107) is provided subject to the disclaimer at the end of this document.


All attempts to bootstrap a client fails. When attempting to bootstrap with the bootstrap script, messages regarding a missing bootstrap repository are seen in the output. For example:
* check for necessary packages being installed...
* client codebase is sle-15-sp4
2023-06-16 01:16:12 ERROR 404: 404.
package salt is not installed
package salt-minion is not installed
* going to install missing packages...
2023-06-16 01:16:12 ERROR 404: 404.
Bootstrap repo '' does not exist.
Repository 'susemanager:bootstrap' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
Some of the repositories have not been refreshed because they were not known.
The word "bootstrap" is seen in the URL in the error, the error is 404, and the repository that is not found is called "susemanager:bootstrap".

Additionally, "package not found" errors are seen while trying to create this bootstrap repository. These errors may be shown in the logs in /var/log/rhn/mgr-create-bootstrap-repo, or in the output of the mgr-create-bootstrap-repo command. For example:
ERROR: package 'timezone' not found
ERROR: package 'salt' not found
ERROR: package 'python3-salt' not found
ERROR: package 'salt-minion' not found
ERROR: package 'venv-salt-minion' not found
ERROR: package 'dmidecode' not found
ERROR: package 'libunwind' not found


This issue is resolved by ensuring that the source of the packages in the bootstrap repository is properly synced. These packages come from the SUSE Manager Client Tools child channels that correspond to the product installed on the client. These Client Tools channels are required for SUSE Manager to add clients.

You can add the Client Tools child channels with the SUSE Manager WebUI, by logging in as an admin user and navigating to Admin > Setup Wizard > Products. From here, search for and expand the base product that is in use by the client, and find and check both of the Client Tools products under this, then click the '+Add Products' button on the top right.

Once this product is done syncing and the packages are available in the Client Tools child channels, you should be able to create the bootstrap repository at this time.

Once the bootstrap repository exists, the client should not have an issue with accessing it during the bootstrap process.


The SUSE Manager Client Tools channels provide packages that SUSE Manager uses during the bootstrap process. If this Client Tools product is not synced properly, the packages needed for the bootstrap repository are unavailable, which prevents the bootstrap repository from being created.

Additional Information

The bootstrap repository is usually created and updated automatically, when its corresponding base product is synced during automatic nightly syncs.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000021107
  • Creation Date: 22-Jun-2023
  • Modified Date:22-Jun-2023
    • SUSE Manager Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.