Klaus Kämpf

I've solved it now by introducing an `operand_offset` variable. (Adding _printf_s to Ghidra pointed me to the right places, esp. showing that ParserWalker's value retrieval functions where called twice -...

Oh, two sleigh compiler implementations 🙈 Time to drop one ? 🤔 I'll see what I can do but I'm not a Java programmer.

The update command should be visible in the `elemental-operator` log. If it's there, it's an operator problem. If not, it's a UI problem.

It's sufficient to upload logs of _failed_ tests :wink:

> > The upgrade has been triggered at 11:01:16 and the elemental node rebooted at 11:30 The upgrade trigger happened at the same time when `elemental-system-agent` got stopped and `rancher-system-agent`...

covered in rancher/elemental-operator#9

Now tracked at rancher/elemental-operator#207

Uhm, not sure how to solve this. (Trying to be explicit here for those without IBS knowledge :wink:) There are (resp. will be) 3 builds in IBS 1. Devel:Elemental -...

I marked this as `later` for now and would rather wait for actual market feedback. What could be useful, however, is respective UI defaults.

> We are also missing elemental-toolkit in the list. Added