# ERROR: No IP address available for bootstrapping

**URL:** <https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486>\
**Category:** Chef Infra (archive)\
**Created:** [September 23, 2013, 5:00am UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486 "2013-09-23T05:00:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ifeanyi\_P\_Egwutuoha](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ifeanyi\_P\_Egwutuoha](https://discourse.chef.io/u/Ifeanyi_P_Egwutuoha)\
**Post date:** [September 23, 2013, 5:00am UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/1 "2013-09-23T05:00:30Z")

</div>

I executed the following command to create an instance on openstack cloud  
but got this error:  
ERROR: No IP address available for bootstrapping.

chef-repo $ knife openstack server create --node-name node --image m1.small  
–ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb -i  
~/.ssh/adelta  
Instance Name: node  
Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d

Waiting for server…  
Flavor: 0  
Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
SSH Identity File: /home/abolap/.ssh/adelta  
SSH Keypair: adelta

ERROR: No IP address available for bootstrapping.

Note that the instance was created with public ip address?  
Any idea of the solution please?

Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Matt\_Ray\_OPSCODE](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/matt_ray_opscode/32/459_2.png) [@Matt\_Ray\_OPSCODE](https://discourse.chef.io/u/Matt_Ray_OPSCODE)\
**Post date:** [September 23, 2013, 2:12pm UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/2 "2013-09-23T14:12:27Z")

</div>

That sounds like the IP address the server handed back isn't called  
'public', it may be something else. Should you be using a floating IP  
or the private IP instead? Feel free to send me the output with -V for  
debug output and I'll offer other suggestions.

> <https://github.com/chef/knife-openstack/blob/main/lib/chef/knife/openstack_server_create.rb#L328>

Thanks,  
Matt Ray  
Cloud Integrations Product Lead :: Opscode  
512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
mattray :: GitHub :: IRC :: Twitter

On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
[ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:

> I executed the following command to create an instance on openstack cloud  
> but got this error:  
> ERROR: No IP address available for bootstrapping.
> 
> chef-repo $ knife openstack server create --node-name node --image m1.small  
> --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb -i  
> ~/.ssh/adelta  
> Instance Name: node  
> Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> 
> Waiting for server...................  
> Flavor: 0  
> Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> SSH Identity File: /home/abolap/.ssh/adelta  
> SSH Keypair: adelta
> 
> ERROR: No IP address available for bootstrapping.
> 
> Note that the instance was created with public ip address?  
> Any idea of the solution please?
> 
> Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Ifeanyi\_P\_Egwutuoha](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ifeanyi\_P\_Egwutuoha](https://discourse.chef.io/u/Ifeanyi_P_Egwutuoha)\
**Post date:** [September 23, 2013, 10:48pm UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/3 "2013-09-23T22:48:24Z")

</div>

I am not using floating ip nor private ip. I can see the public ip  
(115.146.xxx.xxx) assigned from dashboard.  
However none of the -V outputs show the ip-address.

The outputs are:  
~/chef-repo $ knife openstack group list -V  
Name Protocol From To CIDR Description  
default tcp 22 22 0.0.0.0/0 default  
http tcp 80 80 0.0.0.0/0 Allow HTTP/S  
http tcp 443 443 0.0.0.0/0 Allow HTTP/S  
http tcp 8080 8080 0.0.0.0/0 Allow HTTP/S  
http tcp 8081 8081 0.0.0.0/0 Allow HTTP/S  
http tcp 8009 8009 0.0.0.0/0 Allow HTTP/S  
http tcp 8443 8443 0.0.0.0/0 Allow HTTP/S  
http tcp 3306 3306 0.0.0.0/0 Allow HTTP/S  
icmp icmp -1 -1 0.0.0.0/0 Allow ICMP (eg. ping)  
ssh tcp 22 22 0.0.0.0/0 Allow SSH

~/chef-repo$ knife openstack server list -V  
Instance ID Name Public IP  
Private IP Flavor Image Keypair State  
8a3bbf8b-70cf-431f-94c8-38fd5dbf4872  
adelta-3 0  
279d6bba-a287-4bff-a162-40f7d99125f1 adelta active  
e54c82d1-b4d6-41ea-9b70-241014c71fa2  
node 0  
e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb adelta active

~/chef-repo$ knife openstack flavor list -V  
ID Name Virtual CPUs RAM Disk  
0 m1.small 1 4096 MB 10 GB  
1 m1.medium 2 8192 MB 10 GB  
2 m1.xlarge 8 32768 MB 10 GB  
3 m1.xxlarge 16 65536 MB 10 GB  
4 m1.large 4 16384 MB 10 GB

Regards, Ifeanyi

On Tue, Sep 24, 2013 at 12:12 AM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:

> That sounds like the IP address the server handed back isn't called  
> 'public', it may be something else. Should you be using a floating IP  
> or the private IP instead? Feel free to send me the output with -V for  
> debug output and I'll offer other suggestions.
> 
> [knife-openstack/lib/chef/knife/openstack\_server\_create.rb at main · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L328)
> 
> Thanks,  
> Matt Ray  
> Cloud Integrations Product Lead :: Opscode  
> 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> mattray :: GitHub :: IRC :: Twitter
> 
> On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
> [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> 
> > I executed the following command to create an instance on openstack cloud  
> > but got this error:  
> > ERROR: No IP address available for bootstrapping.
> > 
> > chef-repo $ knife openstack server create --node-name node --image  
> > m1.small  
> > --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb -i  
> > ~/.ssh/adelta  
> > Instance Name: node  
> > Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> > 
> > Waiting for server...................  
> > Flavor: 0  
> > Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > SSH Identity File: /home/abolap/.ssh/adelta  
> > SSH Keypair: adelta
> > 
> > ERROR: No IP address available for bootstrapping.
> > 
> > Note that the instance was created with public ip address?  
> > Any idea of the solution please?
> > 
> > Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Ifeanyi\_P\_Egwutuoha](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ifeanyi\_P\_Egwutuoha](https://discourse.chef.io/u/Ifeanyi_P_Egwutuoha)\
**Post date:** [September 25, 2013, 4:32am UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/4 "2013-09-25T04:32:48Z")

</div>

Any suggestion on this please

---------- Forwarded message ----------  
From: Ifeanyi P. Egwutuoha [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com)  
Date: Tue, Sep 24, 2013 at 8:48 AM  
Subject: Re: [chef] Re: ERROR: No IP address available for bootstrapping.  
To: "[chef@lists.opscode.com](mailto:chef@lists.opscode.com)" [chef@lists.opscode.com](mailto:chef@lists.opscode.com)

I am not using floating ip nor private ip. I can see the public ip  
(115.146.xxx.xxx) assigned from dashboard.  
However none of the -V outputs show the ip-address.

The outputs are:  
~/chef-repo $ knife openstack group list -V  
Name Protocol From To CIDR Description  
default tcp 22 22 0.0.0.0/0 default  
http tcp 80 80 0.0.0.0/0 Allow HTTP/S  
http tcp 443 443 0.0.0.0/0 Allow HTTP/S  
http tcp 8080 8080 0.0.0.0/0 Allow HTTP/S  
http tcp 8081 8081 0.0.0.0/0 Allow HTTP/S  
http tcp 8009 8009 0.0.0.0/0 Allow HTTP/S  
http tcp 8443 8443 0.0.0.0/0 Allow HTTP/S  
http tcp 3306 3306 0.0.0.0/0 Allow HTTP/S  
icmp icmp -1 -1 0.0.0.0/0 Allow ICMP (eg. ping)  
ssh tcp 22 22 0.0.0.0/0 Allow SSH

~/chef-repo$ knife openstack server list -V  
Instance ID Name Public IP  
Private IP Flavor Image Keypair State  
8a3bbf8b-70cf-431f-94c8-38fd5dbf4872  
adelta-3 0  
279d6bba-a287-4bff-a162-40f7d99125f1 adelta active  
e54c82d1-b4d6-41ea-9b70-241014c71fa2  
node 0  
e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb adelta active

~/chef-repo$ knife openstack flavor list -V  
ID Name Virtual CPUs RAM Disk  
0 m1.small 1 4096 MB 10 GB  
1 m1.medium 2 8192 MB 10 GB  
2 m1.xlarge 8 32768 MB 10 GB  
3 m1.xxlarge 16 65536 MB 10 GB  
4 m1.large 4 16384 MB 10 GB

Regards, Ifeanyi

On Tue, Sep 24, 2013 at 12:12 AM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:

> That sounds like the IP address the server handed back isn't called  
> 'public', it may be something else. Should you be using a floating IP  
> or the private IP instead? Feel free to send me the output with -V for  
> debug output and I'll offer other suggestions.
> 
> [knife-openstack/lib/chef/knife/openstack\_server\_create.rb at main · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L328)
> 
> Thanks,  
> Matt Ray  
> Cloud Integrations Product Lead :: Opscode  
> 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> mattray :: GitHub :: IRC :: Twitter
> 
> On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
> [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> 
> > I executed the following command to create an instance on openstack cloud  
> > but got this error:  
> > ERROR: No IP address available for bootstrapping.
> > 
> > chef-repo $ knife openstack server create --node-name node --image  
> > m1.small  
> > --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb -i  
> > ~/.ssh/adelta  
> > Instance Name: node  
> > Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> > 
> > Waiting for server...................  
> > Flavor: 0  
> > Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > SSH Identity File: /home/abolap/.ssh/adelta  
> > SSH Keypair: adelta
> > 
> > ERROR: No IP address available for bootstrapping.
> > 
> > Note that the instance was created with public ip address?  
> > Any idea of the solution please?
> > 
> > Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Matt\_Ray\_OPSCODE](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/matt_ray_opscode/32/459_2.png) [@Matt\_Ray\_OPSCODE](https://discourse.chef.io/u/Matt_Ray_OPSCODE)\
**Post date:** [September 25, 2013, 1:44pm UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/5 "2013-09-25T13:44:56Z")

</div>

Looking at the output of the "knife openstack server list" we see the  
"Public IP" and "Private IP" columns with empty entries. Were these  
created in the dashboard or with knife openstack? Inside the server  
that gets handed back from the API is a hash of networks and IP  
addresses, we naively assume they will be called "public" and  
"private", but I expect they must be something different in your  
network (a known bug that we're working on soon).  
[[KNIFE-231] and [KNIFE-277] workaround by baylisscg · Pull Request #30 · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/pull/30) has a temporary fix  
you can try, or if you want you can contact me off-list and I can  
debug it and verify a work-around for you until we have a more  
permanent fix available.

Thanks,  
Matt Ray  
Cloud Integrations Product Lead :: Opscode  
512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
mattray :: GitHub :: IRC :: Twitter

On Mon, Sep 23, 2013 at 5:48 PM, Ifeanyi P. Egwutuoha  
[ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:

> I am not using floating ip nor private ip. I can see the public ip  
> (115.146.xxx.xxx) assigned from dashboard.  
> However none of the -V outputs show the ip-address.
> 
> The outputs are:  
> ~/chef-repo $ knife openstack group list -V  
> Name Protocol From To CIDR Description  
> default tcp 22 22 0.0.0.0/0 default  
> http tcp 80 80 0.0.0.0/0 Allow HTTP/S  
> http tcp 443 443 0.0.0.0/0 Allow HTTP/S  
> http tcp 8080 8080 0.0.0.0/0 Allow HTTP/S  
> http tcp 8081 8081 0.0.0.0/0 Allow HTTP/S  
> http tcp 8009 8009 0.0.0.0/0 Allow HTTP/S  
> http tcp 8443 8443 0.0.0.0/0 Allow HTTP/S  
> http tcp 3306 3306 0.0.0.0/0 Allow HTTP/S  
> icmp icmp -1 -1 0.0.0.0/0 Allow ICMP (eg. ping)  
> ssh tcp 22 22 0.0.0.0/0 Allow SSH
> 
> ~/chef-repo$ knife openstack server list -V  
> Instance ID Name Public IP  
> Private IP Flavor Image Keypair State  
> 8a3bbf8b-70cf-431f-94c8-38fd5dbf4872 adelta-3  
> 0 279d6bba-a287-4bff-a162-40f7d99125f1 adelta active  
> e54c82d1-b4d6-41ea-9b70-241014c71fa2 node  
> 0 e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb adelta active
> 
> ~/chef-repo$ knife openstack flavor list -V  
> ID Name Virtual CPUs RAM Disk  
> 0 m1.small 1 4096 MB 10 GB  
> 1 m1.medium 2 8192 MB 10 GB  
> 2 m1.xlarge 8 32768 MB 10 GB  
> 3 m1.xxlarge 16 65536 MB 10 GB  
> 4 m1.large 4 16384 MB 10 GB
> 
> Regards, Ifeanyi
> 
> On Tue, Sep 24, 2013 at 12:12 AM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:
> 
> > That sounds like the IP address the server handed back isn't called  
> > 'public', it may be something else. Should you be using a floating IP  
> > or the private IP instead? Feel free to send me the output with -V for  
> > debug output and I'll offer other suggestions.
> > 
> > [knife-openstack/lib/chef/knife/openstack\_server\_create.rb at main · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L328)
> > 
> > Thanks,  
> > Matt Ray  
> > Cloud Integrations Product Lead :: Opscode  
> > 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> > mattray :: GitHub :: IRC :: Twitter
> > 
> > On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
> > [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> > 
> > > I executed the following command to create an instance on openstack  
> > > cloud  
> > > but got this error:  
> > > ERROR: No IP address available for bootstrapping.
> > > 
> > > chef-repo $ knife openstack server create --node-name node --image  
> > > m1.small  
> > > --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb -i  
> > > ~/.ssh/adelta  
> > > Instance Name: node  
> > > Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> > > 
> > > Waiting for server...................  
> > > Flavor: 0  
> > > Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > > SSH Identity File: /home/abolap/.ssh/adelta  
> > > SSH Keypair: adelta
> > > 
> > > ERROR: No IP address available for bootstrapping.
> > > 
> > > Note that the instance was created with public ip address?  
> > > Any idea of the solution please?
> > > 
> > > Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Ifeanyi\_P\_Egwutuoha](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ifeanyi\_P\_Egwutuoha](https://discourse.chef.io/u/Ifeanyi_P_Egwutuoha)\
**Post date:** [September 25, 2013, 9:03pm UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/6 "2013-09-25T21:03:06Z")

</div>

Thanks Matt,

What got created in the dashboard is ip address (without private nor public  
address as a heading) as soon below:

Instance Name IP Address Zone Size Keypair Status Task Power State Actions  
node[https://dashboard.rc.nectar.org.au/project/instances/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/](https://dashboard.rc.nectar.org.au/project/instances/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/)

- 115.146.95.90

melbourne-npm1.small | 4GB RAM | 1 VCPU | 10GB DiskadeltaActiveNoneRunning  
Create Snapshot[https://dashboard.rc.nectar.org.au/project/images\_and\_snapshots/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/create](https://dashboard.rc.nectar.org.au/project/images_and_snapshots/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/create)More  
[https://dashboard.rc.nectar.org.au/project/instances/#](https://dashboard.rc.nectar.org.au/project/instances/#)  
adelta-3[https://dashboard.rc.nectar.org.au/project/instances/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/](https://dashboard.rc.nectar.org.au/project/instances/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/)

- 115.146.85.56

melbourne-qh2m1.small | 4GB RAM | 1 VCPU | 10GB DiskadeltaActiveNoneRunning  
Create Snapshot[https://dashboard.rc.nectar.org.au/project/images\_and\_snapshots/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/create](https://dashboard.rc.nectar.org.au/project/images_and_snapshots/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/create)More  
[https://dashboard.rc.nectar.org.au/project/instances/#](https://dashboard.rc.nectar.org.au/project/instances/#)

[https://dashboard.rc.nectar.org.au/project/instances/#](https://dashboard.rc.nectar.org.au/project/instances/#)

On Wed, Sep 25, 2013 at 11:44 PM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:

> Looking at the output of the "knife openstack server list" we see the  
> "Public IP" and "Private IP" columns with empty entries. Were these  
> created in the dashboard or with knife openstack? Inside the server  
> that gets handed back from the API is a hash of networks and IP  
> addresses, we naively assume they will be called "public" and  
> "private", but I expect they must be something different in your  
> network (a known bug that we're working on soon).  
> [[KNIFE-231] and [KNIFE-277] workaround by baylisscg · Pull Request #30 · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/pull/30) has a temporary fix  
> you can try, or if you want you can contact me off-list and I can  
> debug it and verify a work-around for you until we have a more  
> permanent fix available.
> 
> Thanks,  
> Matt Ray  
> Cloud Integrations Product Lead :: Opscode  
> 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> mattray :: GitHub :: IRC :: Twitter
> 
> On Mon, Sep 23, 2013 at 5:48 PM, Ifeanyi P. Egwutuoha  
> [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> 
> > I am not using floating ip nor private ip. I can see the public ip  
> > (115.146.xxx.xxx) assigned from dashboard.  
> > However none of the -V outputs show the ip-address.
> > 
> > The outputs are:  
> > ~/chef-repo $ knife openstack group list -V  
> > Name Protocol From To CIDR Description  
> > default tcp 22 22 0.0.0.0/0 default  
> > http tcp 80 80 0.0.0.0/0 Allow HTTP/S  
> > http tcp 443 443 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8080 8080 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8081 8081 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8009 8009 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8443 8443 0.0.0.0/0 Allow HTTP/S  
> > http tcp 3306 3306 0.0.0.0/0 Allow HTTP/S  
> > icmp icmp -1 -1 0.0.0.0/0 Allow ICMP (eg. ping)  
> > ssh tcp 22 22 0.0.0.0/0 Allow SSH
> > 
> > ~/chef-repo$ knife openstack server list -V  
> > Instance ID Name Public IP  
> > Private IP Flavor Image Keypair State  
> > 8a3bbf8b-70cf-431f-94c8-38fd5dbf4872 adelta-3  
> > 0 279d6bba-a287-4bff-a162-40f7d99125f1 adelta active  
> > e54c82d1-b4d6-41ea-9b70-241014c71fa2 node  
> > 0 e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb adelta active
> > 
> > ~/chef-repo$ knife openstack flavor list -V  
> > ID Name Virtual CPUs RAM Disk  
> > 0 m1.small 1 4096 MB 10 GB  
> > 1 m1.medium 2 8192 MB 10 GB  
> > 2 m1.xlarge 8 32768 MB 10 GB  
> > 3 m1.xxlarge 16 65536 MB 10 GB  
> > 4 m1.large 4 16384 MB 10 GB
> > 
> > Regards, Ifeanyi
> > 
> > On Tue, Sep 24, 2013 at 12:12 AM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:
> > 
> > > That sounds like the IP address the server handed back isn't called  
> > > 'public', it may be something else. Should you be using a floating IP  
> > > or the private IP instead? Feel free to send me the output with -V for  
> > > debug output and I'll offer other suggestions.
> 
> [knife-openstack/lib/chef/knife/openstack\_server\_create.rb at main · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L328)
> 
> > > Thanks,  
> > > Matt Ray  
> > > Cloud Integrations Product Lead :: Opscode  
> > > 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> > > mattray :: GitHub :: IRC :: Twitter
> > > 
> > > On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
> > > [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> > > 
> > > > I executed the following command to create an instance on openstack  
> > > > cloud  
> > > > but got this error:  
> > > > ERROR: No IP address available for bootstrapping.
> > > > 
> > > > chef-repo $ knife openstack server create --node-name node --image  
> > > > m1.small  
> > > > --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > > > -i  
> > > > ~/.ssh/adelta  
> > > > Instance Name: node  
> > > > Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> > > > 
> > > > Waiting for server...................  
> > > > Flavor: 0  
> > > > Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > > > SSH Identity File: /home/abolap/.ssh/adelta  
> > > > SSH Keypair: adelta
> > > > 
> > > > ERROR: No IP address available for bootstrapping.
> > > > 
> > > > Note that the instance was created with public ip address?  
> > > > Any idea of the solution please?
> > > > 
> > > > Regards, Ifeanyi

---

<div class="post-metadata">

**Author:** ![Ifeanyi\_P\_Egwutuoha](https://avatars.discourse-cdn.com/v4/letter/i/a4c791/32.png) [@Ifeanyi\_P\_Egwutuoha](https://discourse.chef.io/u/Ifeanyi_P_Egwutuoha)\
**Post date:** [September 25, 2013, 9:10pm UTC](https://discourse.chef.io/t/error-no-ip-address-available-for-bootstrapping/4486/7 "2013-09-25T21:10:31Z")

</div>

Thanks Matt,

What got created in the dashboard is ip address (without private nor public  
address as a heading) as soon below:

_Instance Name_ _IP Address_ _Zone_ _Size_ _Keypair_ _Status_ _Task_ _Power  
State_ _Actions_  
node[https://dashboard.rc.nectar.org.au/project/instances/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/](https://dashboard.rc.nectar.org.au/project/instances/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/)  
115.146.95.90 melbourne-np m1.small | 4GB RAM | 1 VCPU | 10GB Disk adelta  
Active None Running Create  
Snapshot[https://dashboard.rc.nectar.org.au/project/images\_and\_snapshots/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/create](https://dashboard.rc.nectar.org.au/project/images_and_snapshots/5cf6aac4-f16a-4a22-8be3-72ba7b1bb832/create)More  
[https://dashboard.rc.nectar.org.au/project/instances/#](https://dashboard.rc.nectar.org.au/project/instances/#)  
adelta-3[https://dashboard.rc.nectar.org.au/project/instances/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/](https://dashboard.rc.nectar.org.au/project/instances/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/)  
115.146.85.56 melbourne-qh2 m1.small | 4GB RAM | 1 VCPU | 10GB Disk adelta  
Active None Running Create  
Snapshot[https://dashboard.rc.nectar.org.au/project/images\_and\_snapshots/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/create](https://dashboard.rc.nectar.org.au/project/images_and_snapshots/8a3bbf8b-70cf-431f-94c8-38fd5dbf4872/create)More  
[https://dashboard.rc.nectar.org.au/project/instances/#](https://dashboard.rc.nectar.org.au/project/instances/#)

Any idea pleas?

Regards, Ifeanyi

On Wed, Sep 25, 2013 at 11:44 PM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:

> Looking at the output of the "knife openstack server list" we see the  
> "Public IP" and "Private IP" columns with empty entries. Were these  
> created in the dashboard or with knife openstack? Inside the server  
> that gets handed back from the API is a hash of networks and IP  
> addresses, we naively assume they will be called "public" and  
> "private", but I expect they must be something different in your  
> network (a known bug that we're working on soon).  
> [[KNIFE-231] and [KNIFE-277] workaround by baylisscg · Pull Request #30 · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/pull/30) has a temporary fix  
> you can try, or if you want you can contact me off-list and I can  
> debug it and verify a work-around for you until we have a more  
> permanent fix available.
> 
> Thanks,  
> Matt Ray  
> Cloud Integrations Product Lead :: Opscode  
> 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> mattray :: GitHub :: IRC :: Twitter
> 
> On Mon, Sep 23, 2013 at 5:48 PM, Ifeanyi P. Egwutuoha  
> [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> 
> > I am not using floating ip nor private ip. I can see the public ip  
> > (115.146.xxx.xxx) assigned from dashboard.  
> > However none of the -V outputs show the ip-address.
> > 
> > The outputs are:  
> > ~/chef-repo $ knife openstack group list -V  
> > Name Protocol From To CIDR Description  
> > default tcp 22 22 0.0.0.0/0 default  
> > http tcp 80 80 0.0.0.0/0 Allow HTTP/S  
> > http tcp 443 443 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8080 8080 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8081 8081 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8009 8009 0.0.0.0/0 Allow HTTP/S  
> > http tcp 8443 8443 0.0.0.0/0 Allow HTTP/S  
> > http tcp 3306 3306 0.0.0.0/0 Allow HTTP/S  
> > icmp icmp -1 -1 0.0.0.0/0 Allow ICMP (eg. ping)  
> > ssh tcp 22 22 0.0.0.0/0 Allow SSH
> > 
> > ~/chef-repo$ knife openstack server list -V  
> > Instance ID Name Public IP  
> > Private IP Flavor Image Keypair State  
> > 8a3bbf8b-70cf-431f-94c8-38fd5dbf4872 adelta-3  
> > 0 279d6bba-a287-4bff-a162-40f7d99125f1 adelta active  
> > e54c82d1-b4d6-41ea-9b70-241014c71fa2 node  
> > 0 e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb adelta active
> > 
> > ~/chef-repo$ knife openstack flavor list -V  
> > ID Name Virtual CPUs RAM Disk  
> > 0 m1.small 1 4096 MB 10 GB  
> > 1 m1.medium 2 8192 MB 10 GB  
> > 2 m1.xlarge 8 32768 MB 10 GB  
> > 3 m1.xxlarge 16 65536 MB 10 GB  
> > 4 m1.large 4 16384 MB 10 GB
> > 
> > Regards, Ifeanyi
> > 
> > On Tue, Sep 24, 2013 at 12:12 AM, Matt Ray [matt@opscode.com](mailto:matt@opscode.com) wrote:
> > 
> > > That sounds like the IP address the server handed back isn't called  
> > > 'public', it may be something else. Should you be using a floating IP  
> > > or the private IP instead? Feel free to send me the output with -V for  
> > > debug output and I'll offer other suggestions.
> 
> [knife-openstack/lib/chef/knife/openstack\_server\_create.rb at main · chef/knife-openstack · GitHub](https://github.com/opscode/knife-openstack/blob/master/lib/chef/knife/openstack_server_create.rb#L328)
> 
> > > Thanks,  
> > > Matt Ray  
> > > Cloud Integrations Product Lead :: Opscode  
> > > 512.731.2218 :: [matt@opscode.com](mailto:matt@opscode.com)  
> > > mattray :: GitHub :: IRC :: Twitter
> > > 
> > > On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha  
> > > [ifeanyeg@gmail.com](mailto:ifeanyeg@gmail.com) wrote:
> > > 
> > > > I executed the following command to create an instance on openstack  
> > > > cloud  
> > > > but got this error:  
> > > > ERROR: No IP address available for bootstrapping.
> > > > 
> > > > chef-repo $ knife openstack server create --node-name node --image  
> > > > m1.small  
> > > > --ssh-user ubuntu --flavor 0 -I e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > > > -i  
> > > > ~/.ssh/adelta  
> > > > Instance Name: node  
> > > > Instance ID: e8a99bc7-873b-4750-abf2-f3fd569b4c7d
> > > > 
> > > > Waiting for server...................  
> > > > Flavor: 0  
> > > > Image: e3a0dd4d-8d36-4a85-a9ce-8d7c4ccfa4fb  
> > > > SSH Identity File: /home/abolap/.ssh/adelta  
> > > > SSH Keypair: adelta
> > > > 
> > > > ERROR: No IP address available for bootstrapping.
> > > > 
> > > > Note that the instance was created with public ip address?  
> > > > Any idea of the solution please?
> > > > 
> > > > Regards, Ifeanyi