-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Openstack provider doesn't update subnet allocation_pools #10942
Comments
@cassianoleal Thank you for reporting this and sorry for the delay. I've just confirmed that the provider (and the underlying OpenStack library) does not support updating the allocation pools yet. I'll work on getting this added. |
Just faced the same issue. The workaround for me was to change the pool size via Horizon. |
Quick update: I've submitted a patch to Gophercloud to support this. Once it's merged, I'll get this into Terraform right away. |
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 there,
Terraform fails to update the
start
andend
properties ofallocation_pools
onopenstack_networking_network_v2
resources.Terraform Version
0.8.2
Affected Resource(s)
openstack_networking_subnet_v2.bugreport
Terraform Configuration Files
Debug Output
https://gist.github.com/cassianoleal/c0c55ca6b1479c971832650dc64927f4
Expected Behavior
Apply should have changed the
allocation_pools
for theopenstack_networking_subnet_v2
resource.Actual Behavior
Nothing, apparently.
allocation_pools
were left intact and subsequent plans show the intended changes again.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
allocation_pools
start
and/orend
valuesterraform apply
terraform plan
neutron subnet-show bugreport
Obs: After a manual update using
neutron subnet-update
the plan comes empty as expected.The text was updated successfully, but these errors were encountered: