A question regarding the order in which commands in the same stage but different files are executed.

[rohitntnx]

Hi,

I have two files, 01_network.yaml and 03_agent.yaml. Both files have a kairos-install.pre stage with commands.

In the logs, I see that commands in 03_agent.yaml file's kairos-install.pre are executed before 01_network.yaml's kairos-install.pre.
Is this a bug I should report?

[talss89]

Hi @rohitntnx,

Please check out the "Overriding default configs" section on this page.

Specifically:

What about overriding stages that are in the same stage? Or making sure they run after our wanted step

For example, you have a default stage that runs in the boot.after stage, and you want to override it with your own configuration.

In this case, running them would not guarantee that your configuration is applied after the default one, as both configurations are in the same stage.

For this case yip provides an after directive that allows you to run your configuration after the default one, even if they are in the same stage.

I believe this is due to how cloud-config files are merged. I don't think it's a bug, just slightly unintuitive perhaps.

Does using yip's after directive help? Remember, you can inspect the DAG with kairos-agent run-stage -a <your-stage-to-inspect>

[rohitntnx]

Thanks @talss89 . I tried after: directive, as per your suggestion, here is what I did:

03_agent.yaml

#cloud-config

stages:
  kairos-install.pre:
    - name: "install ops"
      after:
        - name: "network-config"
      commands:
        - |

#cloud-config

stages:
  kairos-install.pre:
    - name: "network-config"
      files:

After booting I am getting this crash in yip:

[talss89]

Your stage name is wrong, I think.

It should be the full name of the stage (combination of path and name). The example in the docs is /oem/01_first.yaml.First stage

If you're unsure of the name to use, check the resolved DAG - it'll show you the stage names in full. Here's the example from the docs:

1.
 <init> (background: false) (weak: false)
2.
 <Start agent.0> (background: false) (weak: true)
 <Start recovery on tty1.Recovery> (background: false) (weak: true)
 <Start installer on tty1..0> (background: false) (weak: true)
 <Default config.Default sysctl settings> (background: false) (weak: true)
 <Enable QEMU tools.Enable QEMU.0> (background: false) (weak: true)
3.
 <Enable QEMU tools.Enable QEMU.1> (background: false) (weak: true)
 <Start installer on tty1..1> (background: false) (weak: true)
4.
 <Enable QEMU tools.Enable VBOX.2> (background: false) (weak: true)
5.
 <Enable QEMU tools.Enable VBOX.3> (background: false) (weak: true)
2025-07-04T07:18:12Z DBG [2994] Generating op for stage '/oem/91_sysctl.yaml.first step'
2025-07-04T07:18:12Z DBG [2994] Generating op for stage '/oem/92_another.yaml.0'
1.
 <init> (background: false) (weak: false)
2.
 </oem/91_sysctl.yaml.first step> (background: false) (weak: true)
3.
 </oem/92_another.yaml.0> (background: false) (weak: true)

[rohitntnx]

Thanks a lot! corrected the stage name, and now it works.
I am wondering why commands are not executed in the order in which the files are read? Would it be a value-add?

[talss89]

Great!

I think it's the nature of a DAG - dependencies are actively resolved before execution. I guess perhaps in the event of a tie break (where no stages have dependencies), prioritising via filename might be a nice touch!

[rohitntnx]

Thanks!