Bug 1228332

Summary:	[doc] Issue in "Deploying a raw disk image"
Product:	[Non-product-specific documentation] Documentation	Reporter:	Ignaz Forster <iforster>
Component:	Smart Docs	Assignee:	Frank Sundermeyer <fs>
Status:	NEW ---	QA Contact:	Tanja Roth <taroth>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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.