Bug 2364442

Summary: regression: Fedora IoT 42 ostree ISO Anaconda installer doesn't run %post kickstart sections
Product: [Fedora] Fedora Reporter: Andrey <butirsky>
Component: anacondaAssignee: Peter Robinson <pbrobinson>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 42CC: anaconda-maint, kkoukiou, miabbott, w
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://github.com/rhinstaller/anaconda/discussions/6397
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269538    

Description Andrey 2025-05-06 17:22:13 UTC
This is regression.

With the very same kickstart, Fedora IoT 41 does run %post sections:

# grep -irI %post /tmp/
/tmp/anaconda.log:15:59:53,292 INF kickstart.script: Running kickstart %%post script(s)
/tmp/anaconda.log:15:59:57,469 INF kickstart.script: All kickstart %%post script(s) have been run

I do not see any attempts on Fedora IoT 42. %pre section runs, though.

Reproducible: Always

Steps to Reproduce:
1. Boot Fedora IoT 42 ostree ISO with any custom ks containing %post section.
2. Let system autoinstall.
3. Without reboot, from the installer console, run:
# grep -irI %post /tmp/
Actual Results:
No relevant "%post" lines found anywhere in /tmp/* files.

Expected Results:
Something like this:
# grep -irI %post /tmp/
/tmp/anaconda.log:15:59:53,292 INF kickstart.script: Running kickstart %%post script(s)
/tmp/anaconda.log:15:59:57,469 INF kickstart.script: All kickstart %%post script(s) have been run

Comment 1 Peter Robinson 2025-05-06 20:01:43 UTC
Can you report this upstream here please: https://github.com/fedora-iot/iot-distro/issues

Comment 3 Andrey 2025-05-29 11:49:09 UTC
Please note I don't see the issue with Fedora Silverblue ISO,
so it's yet unknown if it's Anaconda or IoT issue.