Skip to content

Fixes #39720 - add kickstart-network-no-activate host parameter - #11222

Open
abjo233 wants to merge 1 commit into
theforeman:developfrom
abjo233:39720-kickstart-network-no-activate
Open

Fixes #39720 - add kickstart-network-no-activate host parameter#11222
abjo233 wants to merge 1 commit into
theforeman:developfrom
abjo233:39720-kickstart-network-no-activate

Conversation

@abjo233

@abjo233 abjo233 commented Sep 1, 2026

Copy link
Copy Markdown

Fixes #39720

Satellite: https://redhat.atlassian.net/browse/SAT-49421
Installer bug (not fixed here): https://redhat.atlassian.net/browse/RHELPLAN-140012

What

Add optional host/OS/Host group parameter kickstart-network-no-activate.
When true, kickstart_network_interface prefixes the Kickstart network
command with --no-activate. Default is false, so existing renders are
unchanged.

Why

RHEL 9+ LACP bonds brought up in initramfs get reactivated by Anaconda
when Kickstart applies network, which breaks early rhsm. The documented
workaround is --no-activate. Users currently have to clone Kickstart
default (or this snippet) to use it.

How to test

  1. Provision with stock Kickstart default, parameter unset → network line
    has no --no-activate (same as today).
  2. Set OS or Host group parameter kickstart-network-no-activate=true
    rendered KS contains network --no-activate ....
  3. On an LACP+rhsm host, installation/registration succeeds without cloning
    Kickstart default.

When true, Kickstart network lines include --no-activate so Anaconda
does not reactivate an LACP bond already brought up from boot options.
Default remains unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant