Skip to content
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

Not finding Private IP During Bootstrap #146

Closed
elbandito opened this issue Oct 20, 2014 · 13 comments
Closed

Not finding Private IP During Bootstrap #146

elbandito opened this issue Oct 20, 2014 · 13 comments

Comments

@elbandito
Copy link
Contributor

I have a private cloud, and I'm trying to bootstrap an instance with its private IP address, but I keep getting the same "No IP address available for bootstrapping." error. I'm passing the --openstack-private-network and --bootstrap-network options. Maybe I've just been staring at it too long and need an extra set of eyes to point out the obvious. Here's the output in verbose mode:

> ko server create --node-name image --ssh-user ubuntu --openstack-ssh-key-id dev-test -i ~/Downloads/dev-test.pem --flavor 2 --image bb90d9fb-a73a-4631-945d-5f9b1ae4e657 -r "role[base]" --network-ids 718ef283-f9bf-48c2-83b4-11d94e14f6aa --openstack-private-network --bootstrap-network internal -E development -VV
DEBUG: openstack_username dev
DEBUG: openstack_auth_url https://myhost.com:5001/v2.0/tokens
DEBUG: openstack_tenant development
DEBUG: openstack_endpoint_type publicURL
DEBUG: openstack_insecure
DEBUG: Using fog version: 1.24.0
DEBUG: Create server params - server_def = {:name=>"image", :image_ref=>"bb90d9fb-a73a-4631-945d-5f9b1ae4e657", :flavor_ref=>"2", :security_groups=>["default"], :availability_zone=>nil, :metadata=>nil, :key_name=>"dev-test", :nics=>[{"net_id"=>"718ef283-f9bf-48c2-83b4-11d94e14f6aa"}]}

Waiting for server [wait time = 600]............
Instance ID        14d4befe-e4df-488a-850e-df95d3b61657
Name               image
Flavor             2
Image              bb90d9fb-a73a-4631-945d-5f9b1ae4e657
Keypair            dev-test
State              ACTIVE
Availability Zone  nova
DEBUG: Addresses {"internal"=>[{"OS-EXT-IPS-MAC:mac_addr"=>"fa:16:3e:0a:27:30", "version"=>4, "addr"=>"10.250.2.22", "OS-EXT-IPS:type"=>"fixed"}]}
DEBUG: Floating IP Address requested -1
DEBUG: Addresses {"internal"=>[{"OS-EXT-IPS-MAC:mac_addr"=>"fa:16:3e:0a:27:30", "version"=>4, "addr"=>"10.250.2.22", "OS-EXT-IPS:type"=>"fixed"}]}
DEBUG: Bootstrap Network: private
DEBUG: Bootstrap IP Address:
ERROR: No IP address available for bootstrapping.
FATAL: No IP address available for bootstrapping.
DEBUG: No IP address available for bootstrapping.
@jjasghar
Copy link
Contributor

Do you have a VPN or is that 10.x Addy route-able?

@elbandito
Copy link
Contributor Author

@jjasghar There's a VPN

@jjasghar
Copy link
Contributor

Ah OK, just starting from the ground up. Are you you using neutron or nova networking?

@elbandito
Copy link
Contributor Author

I believe our OpenStack service is setup to use Neutron. Don't know if this is a datapoint, but bootstrapping does work fine if I use floating IPs.

@jjasghar
Copy link
Contributor

Ah yeah that's a perfect data point. When I get to my laptop I'll write out the issue, you found a bug.

@elbandito
Copy link
Contributor Author

Sounds good! Let me know if can help out with anything!

There's one thing I'd like to verify the correct usage of. I'm using the same network for both the --network-ids and --bootstrap-network. The only difference is that for the --bootstrap-network, I'm specifying the name instead of the id. Is this ok?

Name      ID                                    Tenant                            Shared
internal  718ef283-f9bf-48c2-83b4-11d94e14f6aa  ee491d66b636499aa534afcc37d767fb  true

@elbandito
Copy link
Contributor Author

@jjasghar The issue appears to be here. We're not even considering the user defined network name, we're just setting it to private for all cases of network private being true.

@jjasghar
Copy link
Contributor

jjasghar commented Mar 7, 2015

is this still an issue? If so, I can pick up attempting to repo and resolve this.

@elbandito
Copy link
Contributor Author

I believe it is. I made a local change, which I've been testing, and it seems to be working fine. Just need to write a test case.

@jjasghar
Copy link
Contributor

Any chance you can push this upstream? I'm getting another issue with floating ips reported so it's very possible we'll have another knife-openstack release sooner then later.

@elbandito
Copy link
Contributor Author

Ok, let me take a look at it.

@elbandito
Copy link
Contributor Author

@jjasghar I'm about to take a look. Is this still needed?

@elbandito
Copy link
Contributor Author

@jjasghar just submitted a PR

elbandito added a commit to elbandito/knife-openstack that referenced this issue Jun 1, 2015
@jjasghar jjasghar removed Bug labels Jun 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants