Newly built image (incorporating combustion) fails to boot
This document (000022002) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Micro 6
SUSE Linux Enterprise Micro 5
Situation
New image build which uses combustion and has the root file system residing on LVM, fails to boot.
Resolution
Either do not place the root file system on LVM or do not use combustion as a part of the image build.
Cause
This is due to a dead-lock situation.
The first-boot detection needs to run after the root device has become available (to be able to check for /etc/machine-id presence), but before the network configuration is applied (such that the combustion script can provide configuration).
The network config is applied during initqueue. As a result, the system waits for the root device before initqueue runs LVM detection, resulting in this impossible boot order:
Root Device available > first boot detection > initqueue [network detection > LVM Detection]
First boot detection fails as the LVM detection has not happened yet (and will never happen in this scenario).
Additional Information
Please note that combustion and Ignition (although present in some minimal SLES images provided by SUSE) are not intended for general use with SUSE Linux Enterprise Server (SLES12/SLES15/SLES16).
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:000022002
- Creation Date: 22-Aug-2025
- Modified Date:22-Aug-2025
-
- SUSE Linux Enterprise Micro
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
