STACKIT Server without Network Interfaces

[tim-szostakowski-rewion]

Description

When using the https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs/resources/server Resource block, it should be possible to create a server without Network interfaces in order to make use of
https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs/resources/server_network_interface_attach
and
https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs/resources/network_interface

properly. Otherwise you get an error:
│ Error: Error creating server
│
│ with stackit_server.this["vm9"],
│ on resources.vm.tf line 1, in resource "stackit_server" "this":
│ 1: resource "stackit_server" "this" {
│
│ Calling API: 400 Bad Request, status code 400, Body: {"code":400,"msg":"request body has an error: doesn't match schema #/components/schemas/v2CreateServer: doesn't match
│ schema due to: Error at "/networking": input matches more than one oneOf schemas And Error at "/networking": input matches more than one oneOf schemas"}
│

[tim-szostakowski-rewion]

it makes no sense to have adding and removing network interfaces as a breaking change to the vm

[tim-szostakowski-rewion]

Current workaround is to add a server like

resource "stackit_server" "this" {
for_each = local.server_map

project_id = var.stackit_project_id
name = each.value.name
machine_type = each.value.machine_type
desired_status = each.value.desired_status
availability_zone = each.value.availability_zone
boot_volume = each.value.boot_volume
keypair_name = try(each.value.keypair_name, null)
user_data = try(each.value.user_data, null)
agent = {
provisioning_policy = "INHERIT"
}

network_interfaces = [
for nic_key, nic in local.nic_map :
stackit_network_interface.this[nic_key].network_interface_id
if nic.vm_key == each.key
]

lifecycle {
ignore_changes = [
network_interfaces
]
}
}

and remove the network interface attachments manually e.g. in portal to then make use of the https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs/resources/server_network_interface_attach, otherwise you get an error like

│ Error: Error attaching network interface to server
│
│ with stackit_server_network_interface_attach.this["vm10-nic-0"],
│ on resources.vm.nics.tf line 14, in resource "stackit_server_network_interface_attach" "this":
│ 14: resource "stackit_server_network_interface_attach" "this" {
│
│ Calling API: 409 Conflict, status code 409, Body: {"code":409,"msg":"conflict: Port xxx is still in use."}
│

[GokceGK]

Hi @tim-szostakowski-rewion ,

thanks for reporting the issue. With the v1 version of API, it was possible to create server without network interfaces, but with the v2 api this field is now required. https://docs.api.stackit.cloud/documentation/iaas/version/v2#tag/Servers/operation/v2CreateServer

Can you provide us the full configuration, especially the nic_map. And also what is your use case, we generally want to have a nic in our servers. Why it is being removed manually and then attaching again? Do you need to change network interface of server time to time?

I can only reproduce this issue if my network_interface is attached to a server already. I am not sure how the filtering with if nic.vm_key == each.key part works.

Best regards,
Gökce from STACKIT Developer Tools