Open B1Sandmann opened 7 years ago
Hi Folks,
I am observing equally the same issue. kitchen 1.16 kitchen-openstack 3.5.0 any thoughts? workarounds?
Thanks in advance
same issue here
We finally got it to work when using the name of the network instead of the ID. If it's intended to only work with the name it should be better documented. Example of the relevant config that works for us:
network_ref: # the internal network
- 74109d28-130d-4500-b806-299026417c2a
allocate_floating_ip: true
floating_ip_pool: FloatingIP-external-project-01 # the external network
We didn't state a public or private ip order so either the default is okay or it's not relevant. I'm still not quite sure I understand the public/privat_ip_order anyways.
@B1Sandmann can you put in a PR to make the documentation better? Ideally this will help out @rbabyuk-vs and @k0da too. Thanks!
When trying to run tests in our internal setup test-kitchen isn't able to get a floating IP from a pool of floating IPs. Instead I get an error that there are no floating IPs available in the pool but there are many IPs available. The external network however is a shared one as well as the internal one so it might behave different than a normal setup where external network, internal network and router are part of the project. It does however work with a fixed floating IP, but as we would like to run multiple tests in parallel the pool feature would be a huge help.
All this is with kitchen 1.16 and kitchen-openstack 3.1.4 and 3.1.5 as well.
The .kitchen.yml (slightly anonymized)
The debug log output (slightly anonymized):
If I try the same with
allocate_floating_ip: true
added in the .kitchen.yml I get another error about a undefined method: