![](https://seccdn.libravatar.org/avatar/7d22a6866e873232b8dea8377472e3d2.jpg?s=120&d=mm&r=g)
Hello, I have build an opensuse microOS iso image with kiwi-ng successfully. Then, I tried to customize my iso with an autoyast profile with the help of this documentation : https://osinside.github.io/kiwi/working_with_images/setup_yast_on_first_boot... The image was built successfully but when I use it, I have the following error : No workflow defined for this installation mode What does mean this error ? How can I fix it ? Should the kiwi-ng documentation be updated ? I also reported this issue on kiwi google group: https://groups.google.com/g/kiwi-images/c/r3L_fwXp3Xc Regards, Gabriel.
![](https://seccdn.libravatar.org/avatar/f9a9cf77af20d925b328ee8c95c0068c.jpg?s=120&d=mm&r=g)
Hi Gabriel,
from your description I am not sure if I get exactly what you try to
achieve. So let me ask inside text:
On Mon, 17 Jun 2024 10:25:11 -0000
"Gabriel MACHADO"
Hello,
I have build an opensuse microOS iso image with kiwi-ng successfully.
Is that kiwi description available somewhere to check if all packages are there?
Then, I tried to customize my iso with an autoyast profile with the help of this documentation : https://osinside.github.io/kiwi/working_with_images/setup_yast_on_first_boot...
The documentation is about using yast2-firstboot and not about autoyast.
The image was built successfully but when I use it, I have the following error : No workflow defined for this installation mode
Can you describe how exactly you use it? Like how you run it, how you pass autoyast profile, etc.
What does mean this error ? How can I fix it ?
The error mean basically that you try to run in mode for which it does not have defined workflow. There can be multiple reasons. E.g. missing workflow definition for firstboot if you follow documentation and try to run firstboot without its data files and config. But to know exactly what happens it can help if you provide ( sharing somehow, e.g. in bugzilla or via some sharing service, not sent via email ) yast logs - `save_y2logs` command helps to collect all needed information.
Should the kiwi-ng documentation be updated ?
I would say yes, as it mixtures autoyast and firstboot, which is different modes and usage. Autoyast is for automatic or semi-automatic installation. Firstboot is for interactive first boot configuration ( useful for images that is deployed and need some fine tuning ).
I also reported this issue on kiwi google group: https://groups.google.com/g/kiwi-images/c/r3L_fwXp3Xc
Regards, Gabriel.
Josef
participants (2)
-
Gabriel MACHADO
-
jreidinger