Closed cliffpracht closed 8 years ago
Hi,
So I made a fix to my forked branch, I was looking for some feedback as to if this is the right solution to this problem. We are not sure if there was a reason to using []ports.IP
originally instead of using interface{}
, which is what Gophercloud is initializing it as.
https://github.com/ebsco/terraform/commit/1de2fde147558fc10600638c29e9340651424d14
Seems like the right approach to me. Feel free to submit a PR! :smile:
@jimmycliff I ran your patch through the acceptance tests that utilize the openstack_networking_port_v2
resource and everything passes. If you'd like to submit a PR for this fix, I'd be happy to merge it. Or if you'd like, I can go ahead and take care of making a PR.
Thanks @jtopjian submitted PR
Awesome!
What version was this fixed in? 0.6.11 was cut after this fix was merged, but I still seem to have the same issue. Just as the original poster pointed out, I can neutron port create
; but attempting to do the same thing in vagrant fails even if I don't specify the fixed_ips.
@matthughes Ouch... sorry to hear you're still seeing this. The fix was included in 0.6.10, so 0.6.11 would include it, too.
Can you run TF_LOG=DEBUG terraform apply...
and post a sanitized version to a gist?
I think it's actually a different issue; not related to fixed_ips at all. I opened a new issue up in #5171
okie dokie :)
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.
HI,
It appears that there might be a bug in Terraform that stops users from using the openstack_networking_port_v2 resource if the tenant does not have privileges to create fixed_ips.
The resource call that I am trying to run is the following:
The tenant that I am connecting as does not have admin privileges or is not the network owner. The tenant has the ability to create ports on this network, but not the ability to specify fixed IPs. This is a snip of the policy file on the Openstack server
I can confirm this by running neutron directly from the command line using same tenant.
Running terraform apply I get the following error. Notice that I am not actually setting fixed_ip
Tracing the request for Terraform, this is what the POST request JSON looks like. Notice that fixed_ips is being sent as empty array:
The same POST using the neutron CLI looks like this.
So it appears that we are sending fixed_ip parameter (as well as security_id) when they are not specified. This causes the request to fail because the tenant does not have fixed_ip permissions.
Cliff