Situation

When we create a tester vm it makes it seems you can choose a node, but first the word is misleading its more an SID or something for the slice

But not only that, but if you put 0002 instead of 0001 it won't even work. So we should not even show this or let the admin choose a number. It is 0001 by default afaik.

# Situation - When we create a tester vm it makes it seems you can choose a node, but first the word is misleading its more an SID or something for the slice ![image](/attachments/e82ce37d-2509-447b-8b75-74c869bd8043) - But not only that, but if you put 0002 instead of 0001 it won't even work. So we should not even show this or let the admin choose a number. It is 0001 by default afaik.

image.png

9.5 KiB

mik-tf commented

2026-06-07 05:07:36 +00:00

Author

Owner

Done. The provision Node field is now hidden and fixed to the default slice, so an operator cannot enter a value that does not exist (a wrong slice silently failed to provision). Explicit node selection will return when the deployer supports more than one dedicated node (#264). Deployed to the admin machine.

Signed-by: mik-tf mik-tf@noreply.invalid

Done. The provision Node field is now hidden and fixed to the default slice, so an operator cannot enter a value that does not exist (a wrong slice silently failed to provision). Explicit node selection will return when the deployer supports more than one dedicated node (#264). Deployed to the admin machine. Signed-by: mik-tf <mik-tf@noreply.invalid>

mik-tf closed this issue

2026-06-07 05:07:37 +00:00

Rows
Columns

Hero Deployer SID node #263

Situation