Plan shows changed on every run for my openstack_networking_port_v2

[KZachariassen]

Hi,

When I do a plan it shows a change on every run for my openstack_networking_port_v2

resource "openstack_networking_port_v2" "lb-vip-port" {
  name = "lb-vip-port"
  network_id = "${openstack_networking_network_v2.LB_VIP_Internal_Network.id}"
  mac_address = "fa:16:3e:9c:22:85"
  admin_state_up = "true"
  lifecycle { 
	prevent_destroy = true
  }
  
  #---------------------
  # LoadBalancer IP'S
  #---------------------
  #LB Subnet IP
  fixed_ip {
    subnet_id = "${openstack_networking_subnet_v2.LB_VIP_Internal_Network_Subnet.id}"
	ip_address = "192.168.10.253"
  } 
  #MGMT PUBLIC VIP IP  
  fixed_ip {
    subnet_id = "${openstack_networking_subnet_v2.LB_VIP_Internal_Network_Subnet.id}"
	ip_address = "192.168.10.254"
  }

  #---------------------
  # DBA IP'S
  #---------------------
  #_vip-dbaxxrmqc01.dus.dba.qaxx.dk-qa.ecg.so, _vip-dbaxxrmqc01.dus.dba.qaxx.dk-qa.ecg.so-admin 
  fixed_ip {
    subnet_id = "${openstack_networking_subnet_v2.LB_VIP_Internal_Network_Subnet.id}"
    ip_address = "192.168.10.15"
  }
}

It looks like it changing the order of the ip every time

~ module.network.openstack_networking_port_v2.lb-vip-port
    fixed_ip.0.ip_address:  "192.168.10.154" => "192.168.10.253"
    fixed_ip.1.ip_address:  "192.168.10.153" => "192.168.10.15"
   fixed_ip.1.ip_address:  "192.168.10.15" => "192.168.10.254"

~ module.network.openstack_networking_port_v2.lb-vip-port
    fixed_ip.0.ip_address:  "192.168.10.115" => "192.168.10.254"
    fixed_ip.1.ip_address:  "192.168.10.154" => "192.168.10.153"
   fixed_ip.1.ip_address:  "192.168.10.153" => "192.168.10.15"

[GeertJohan]

I can confirm as I'm having the same issue here. It's very annoying, but doesn't break the plan execution.

In my case it seems that openstack doesn't keep track of the order in which fixed ip's were added and instead sorts them alphabetically.

[jtopjian]

Hi all,

I just submitted #12613 which should fix this issue. If you're able to compile from source, please feel free to try it out ahead of time. :)

Thanks,
Joe

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.