[chef] Re: Re: Re: Re: ERROR: No IP address available for bootstrapping.

["Ifeanyi P. Egwutuoha" < >]

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	115.146.95.90	melbourne-np	m1.small | 4GB RAM | 1 VCPU | 10GB Disk	adelta	Active	None	Running	Create Snapshot More
	adelta-3	115.146.85.56	melbourne-qh2	m1.small | 4GB RAM | 1 VCPU | 10GB Disk	adelta	Active	None	Running	Create Snapshot More

On Wed, Sep 25, 2013 at 11:44 PM, Matt Ray < " target="_blank"> > 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).
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 :: ">
mattray :: GitHub :: IRC :: Twitter

On Mon, Sep 23, 2013 at 5:48 PM, Ifeanyi P. Egwutuoha

< "> > 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 < "> > 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.
>>
>> 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 :: ">
>> mattray :: GitHub :: IRC :: Twitter
>>
>>
>> On Mon, Sep 23, 2013 at 12:00 AM, Ifeanyi P. Egwutuoha
>> < "> > 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
>> >
>
>