Autoinstallation of a SLES/SLED 12 SP1 fails in SUSE Manager with "unknown module cobbler" error

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

Environment

SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
SUSE Linux Enterprise Desktop 12 Service Pack 1 (SLED 12 SP1)
SUSE Manager 2.1

Situation

Whenever a new autoinstallation for SLE 12 SP1 (no matter whether SLES or SLED) is tried, it fails with the error message displaying an alert like this:
Error: These sections of AutoYaST profile cannot be processed on this system:
<cobbler/>
Maybe they were misspelled or your profile does not contain all the needed YaST packages in <software/>section.

Resolution

The PTF that solves the issue can be accessed here:

https://ptf.suse.com/f2cf38b50ed714a8409693060195b235/sles12-sp1/10014/x86_64/20160122/


However, rather than including this into a new ISO, for most customers the easiest solution would be to use a DUD (Driver Update Disk) that contains the updated rpm's. A signature file would be needed as well.

DUD download link, including signature: bsc955878-v2-autoyast2.tar.gz

The instructions for using the DUD are as follows:

- Both files should be copied to a web server. Usually a good idea would be to use the one in the SUSE Manager, so the files can be copied under the location:
/srv/www/htdocs/pub/sub_directory
- Proper permissions should be granted to the files. If possible names should not be changed, as the signature file (.asc) needs to have the same name in order to be automatically read.

- In SUSE Manager, under: Systems - Autoinstallation - Distributions - Choose your SLES 12 SP1 distribution, a kernel option like this needs to be added:
dud=http://yoursusemanagerserver.yourdomain.com/pub/sub_directory/dudfilename.dud
A warning will still be displayed, but it can now be bypassed by simply hitting enter.
In cases where manual interaction is not desired, the autoyast file can be modified, so that most errors/warnings get a timeout and then the installation will finish without user's interaction, by adding the following:
<report>
 <messages> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </messages> <errors> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </errors> <warnings> <show config:type="boolean">true</show> <timeout config:type="integer">10</timeout> <log config:type="boolean">true</log> </warnings> </report>

Disclaimer

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:7017278
  • Creation Date: 19-Feb-2016
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise Server
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

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

Join Our Community

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.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

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

Go to Customer Center