Issues of floating bare metal server id and reserved ip is not updating

[peiyang2024]

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

Affected Resource(s)

• ibm_is_bare_metal_server_network_interface_floating_ip
• ibm_is_bare_metal_server_network_interface_allow_float

Terraform Configuration Files

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

resource "ibm_is_bare_metal_server_network_interface_allow_float" "bms_nics" {
    count = 3
    bare_metal_server = ibm_is_bare_metal_server.bms.id
    subnet = ibm_is_subnet.subnet.id
    name   = "test-${count.index}"
    vlan   = 101
}

resource "ibm_is_bare_metal_server_network_interface_floating_ip" "bms_nic_fip" {
  bare_metal_server = ibm_is_bare_metal_server.bms.id
  network_interface = ibm_is_bare_metal_server_network_interface_floating_ip.bms_float_nic.floating_bare_metal_server
  floating_ip       = ibm_is_floating_ip.fip.id
}

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

There are two issues:

1. When we create quite a big number of vlan interfaces, some IP addresses of the created vlan interfaces returned 0.0.0.0, actually these IP addresses resources are created correctly, we can get the correct IP from console or cli.
2. When attaching a floating ip to an allow float nic, and the nic is floated, for example bm000->bm001, there is error occurs complains about the incorrect bm_id (bm000) passed to the resource.

Important Factoids

References

• #0000

[davidyao19]

@ujjwal-ibm once you have the workaround fix, would you associate it with this issue too? Thanks.

[astha-jain]

@davidyao19 are we good to close this issue?

[davidyao19]

Sorry late @astha-jain Yes, we can close it now. Thanks!