Skip to content

Allow to configure the multipath behavior at the agama config (profile)#2574

Draft
ancorgs wants to merge 2 commits intomasterfrom
unattended_multipath
Draft

Allow to configure the multipath behavior at the agama config (profile)#2574
ancorgs wants to merge 2 commits intomasterfrom
unattended_multipath

Conversation

@ancorgs
Copy link
Copy Markdown
Contributor

@ancorgs ancorgs commented Jul 17, 2025

Problem

Currently Agama honors LIBSTORAGE_MULTIPATH_AUTOSTART, unconditionally activating multipath if that boot argument is used, even if libstorage-ng does not detect a multipath setup.

If that argument is not provided Agama raises a question if a multipath setup is detected in the system. And the user needs to answer that question.

That leaves the users of unattended installations with two mechanisms to activate multipath:

  • Force it via the mentioned boot argument.
  • Specify the answer to the question.

The second option is possible for unattended installations but kind of cumbersome compared to the AutoYaST possibility of simply writing <start_multipath>true</start_multipath> at the profile.

Solution

This pull request adds a new section to the JSON Agama configuration (a.k.a. profile) to specify whether multipath should be started during installation. Removing the dependency on a boot argument or a separate configuration for answers.

@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 76.037% (+11.7%) from 64.317%
when pulling 9d9f4eb on unattended_multipath
into 5249cbc on master.

@coveralls
Copy link
Copy Markdown

coveralls commented Jul 17, 2025

Coverage Status

coverage: 76.037% (+11.7%) from 64.317%
when pulling 9d9f4eb on unattended_multipath
into 5249cbc on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants