Closed teancom closed 9 years ago
No offence taken at all. Thanks for the heads up -- I'll look into it shortly and get it resolved.
I really need to sit down and understand how the unit tests work from the other providers.
OK, the latest commit should fix this issue. I believe the logic in the network/networks conditional was incorrect and so the else
portion was never being hit.
Let me know if this works for you now. Sorry about that!
Oh, and just to clarify:
Commit ddeabee broke the ability to specify a network, which is required when you have more than one.
The network
block should be able to be specified multiple times. I haven't actually verified that, but that's the intention. I have access to a multi-network Neutron-based OpenStack environment that I'll be verifying this against within the next day or so.
I've updated the README to clarify how network
can be used.
Works like a champ. Fixed in f2b17c8. And yeah, I was going to look into unit tests myself. I'm no go programmer, but maybe I can help out with some sort of testing.
Awesome! Thanks again for the heads up. Please let me know of any more issues you run into.
At the moment, I'm stuck trying to figure out Floating IPs for nova-network. Floating IPs for Neutron should be easy enough as that support is now in gophercloud. I might end up writing a quick openstack_keypair
resource or similar to take my mind off it.
Let me start by saying 1) it looks like you're kicking butt and taking names and 2) please don't view this bug report as me complaining. I have absolutely read the README and understand this isn't beta (or even alpha) quality. Just trying to help you keep track of possible breakage as you move forward. Now that that's out of the way:
Commit ddeabee broke the ability to specify a network, which is required when you have more than one. This is still broken with ac390b7.
Using:
I now get back:
instead of: