Bug 1228332 - [doc] Issue in "Deploying a raw disk image"
Summary: [doc] Issue in "Deploying a raw disk image"
Status: NEW
Alias: None
Product: Documentation
Classification: Non-product-specific documentation
Component: Smart Docs (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Frank Sundermeyer
QA Contact: Tanja Roth
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-25 12:10 UTC by Ignaz Forster
Modified: 2024-07-25 12:10 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ignaz Forster 2024-07-25 12:10:58 UTC 
Deploying a raw disk image (https://documentation.suse.com/sle-micro/6.0/html/Micro-deployment-raw-images/index.html#deployment-raw-procedure)

and

Section 1.1, “First boot detection” (https://documentation.suse.com/sle-micro/6.0/html/Micro-deployment-raw-images/index.html#deployment-first-boot-detection)

The "Note: Rerunning the initial configuration" box from the first link and the whole section 1.1 from the second link are still referring to the file /boot/writable/firstboot_happened which is not used any more.

With SLE Micro 6.0 the firstboot detection mechanism has been reworked as follows instead:
- It will check for the presence of the file /etc/machine-id in the sysroot now (mostly matching what systemd is also doing for evaluating ConditionFirstBoot=yes). If it is not there it is assumed that this is a firstboot, enabling the systemd firstboot.target.
- To rerun the firstboot configuration "ignition.firstboot" or "combustion.firstboot" (just the presence counts, there doesn't have to be a value assigned) can be appended to the kernel command line manually as before.