Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ibm_is_bare_metal_server network interface capabilities missing #3730

Closed
bryanbuckland opened this issue Apr 19, 2022 · 2 comments · Fixed by #3747
Closed

ibm_is_bare_metal_server network interface capabilities missing #3730

bryanbuckland opened this issue Apr 19, 2022 · 2 comments · Fixed by #3747
Assignees
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure

Comments

@bryanbuckland
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

Terraform v1.1.8
on darwin_amd64```

### Affected Resource(s)

<!--- Please list the affected resources and data sources. --->

* ibm_is_bare_metal_server network

### Terraform Configuration Files

<!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code --->

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

```hcl
resource "ibm_is_bare_metal_server" "esx_host" {
    count = var.vmw_host_count
    profile = var.vmw_host_profile
    user_data = data.template_file.userdata[count.index].rendered
    name = "${local.hostname}-${format("%03s", count.index)}"
    resource_group  = var.vmw_resource_group_id
    image = var.vmw_esx_image
    zone = var.vmw_vpc_zone
    keys = [var.vmw_key]
    primary_network_interface {
      subnet = var.vmw_host_subnet
      allowed_vlans = [100, 200, 300, 400, 700, 710]
      name = "pci-nic-vmnic0-uplink1"
      #name = "pci-nic-vmnic0-vmk0"
      security_groups = [var.vmw_sg_mgmt]
      enable_infrastructure_nat = true
    }
    network_interfaces {
     # pci2
     subnet = var.vmw_host_subnet
     allowed_vlans = [100, 200, 300, 400, 700, 710]
     # allowed_vlans = [10]
     name = "pci-nic-vmnic0-uplink2"
     security_groups = [var.vmw_sg_mgmt]
     enable_infrastructure_nat = true
    # }
   }

    vpc = var.vmw_vpc
    timeouts {
      create = "30m"
      delete = "30m"
    }
}

Debug Output

Panic Output

Expected Behavior

Network interfaces should be processed and added to the bare-metal server, like it does on the CLI / API

Actual Behavior

network interfaces are ignored by terraform and not submitted to the API

Steps to Reproduce

  1. terraform apply

Important Factoids

References

  • #0000
@astha-jain
Copy link
Contributor

Are we good to close? @bryanbuckland

@bryanbuckland
Copy link
Author

Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure
Projects
None yet
2 participants