[2125942565] Upstream Reporter: Cheng Zhang
Upstream issue status: Closed
Upstream description:

1. 1. 1. Describe the bug

When send in multiple kargs input in a single string, the `kargs` seems to treat it as a single key value pair. For example run `rpm-ostree karg --delete "init_on_alloc=1 init_on_free=1"` will delete neither parameter, and `rpm-ostree karg --append-if-missing "init_on_alloc=1 init_on_free=1"` will duplicate these two kargs even when they exists

1. 1. 1. Reproduction steps

1. run `rpm-ostree karg --append "init_on_alloc=1 init_on_free=1"`, notice that `init_on_alloc=1 init_on_free=1` gets added to kargs
2. run `rpm-ostree karg --append-if-missing "init_on_alloc=1 init_on_free=1"`, will duplicate these two kargs even when they are already present
3. run `rpm-ostree karg --delete "init_on_alloc=1 init_on_free=1"` will give an error stating the argument is not found

1. 1. 1. Expected behavior

`rpm-ostree karg --append-if-missing "init_on_alloc=1 init_on_free=1" ` should not duplicate the kargs, and `rpm-ostree karg --delete "init_on_alloc=1 init_on_free=1"` should delete the kargs when they are present.

Or at least raise an error/warning to the user about invalid input.

1. 1. 1. Actual behavior

Described in "Reproduction steps" section

1. 1. 1. System details

```
$ rpm-ostree version

rpm-ostree:
Version: '2024.2'
Git: 3d9a8755ddd96395a5c1d02b42243eb54ea01193
Features:

• rust
• compose
• container
• fedora-integration
  ```

1. 1. 1. Additional information

Related:

• https://discussion.fedoraproject.org/t/how-i-do-to-put-several-kernel-arguments-in-rpm-ostree-in-a-single-command/74113
• https://github.com/secureblue/secureblue/pull/202