undefined method `public_ip_addresses' for {}:Hash

[equick]

Using the kitchen-openstack-2.0.0 I get this error:

-----> Starting Kitchen (v1.4.2) -----> Creating ...
OpenStack instance with ID of <37027f3b-6405-46bd-9add-ddb12a891714> is ready. >>>>>> Server (37027f3b-6405-46bd-9add-ddb12a891714) not reachable. Destroying server...
OpenStack instance <37027f3b-6405-46bd-9add-ddb12a891714> destroyed. >>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed >>>>>> Message: Failed to complete #create action: [undefined method public_ip_addresses' for {}:Hash] >>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details >>>>>> Also try running kitchen diagnose --all for configuration

I wonder if you've run into the same issue as the one mentioned here?

https://groups.google.com/forum/#!topic/foreman-users/e0JWlxTSuy0

[jjasghar]

what version of the gem are you using?

[equick]

ruby 2.1.6p336 (2015-04-13 revision 50298) [x86_64-linux]

[jjasghar]

kitchen-openstack gem

[equick]

oh sorry

$ kitchen-openstack gem
-bash: kitchen-openstack: command not found

[equick]

It was definitely kitchen-openstack-2.0.0

[jjasghar]

what version of chef-dk are you using?

[equick]

chefdk-0.7.0-1.el6.x86_64

[jjasghar]

Do you have floating ips enabled? Are you running neutron?

[jjasghar]

I'm pretty sure that comes from fog, what version of fog are you running?

kitchen-openstack/lib/kitchen/driver/openstack.rb

Line 294 in 64d8f5a

pub = server.public_ip_addresses

[equick]

I'm not sure about the floating ips but in the openstack console when I go to Allocate IP to project, it says no floating ip pools available. Also not sure how to check if neutron is running but can look into that.

Gem list says that I have fog (1.33.0)

[jjasghar]

yeah so the public ips are pulled from the floaiting ip pool:

A specific floating_ip or the ID of a floating_ip_pool can be provided to bind a floating IP to the node. Any floating IP will be the IP used for Test Kitchen's SSH calls to the node.

floating_ip: [A SPECIFIC FLOATING IP TO ASSIGN]
floating_ip_pool: [AN OPENSTACK POOL NAME TO ASSIGN THE NEXT IP FROM]

If you don't have any ips available this error will be thrown. If you have private ip routing you can get in via that and skip it completely.

In some complex network scenarios you can have several IP addresses designated as public or private. Use public_ip_order or private_ip_order to control which one to use for further SSH connection. Default is 0 (first one)

For example if you have openstack istance that has network with several IPs assigned like

+--------------------------------------+------------+--------+------------+-------------+----------------------------------+
| ID                                   | Name       | Status | Task State | Power State | Networks                         |
+--------------------------------------+------------+--------+------------+-------------+----------------------------------+
| 31c98de4-026f-4d12-b03f-a8a35c6e730b | kitchen    | ACTIVE | None       | Running     | test=10.0.0.1, 10.0.1.1   |

to use second 10.0.1.1 IP address you need to specify

  private_ip_order: 1

assuming that test network is configured as private.

The network_ref option can be specified as an exact id, an exact name, or as a regular expression matching the name of the network. You can pass one

network_ref: MYNET1
or many networks

network_ref:
  - MYNET1
  - MYNET2

[equick]

Thanks for that. Mine is specified as
`network_ref: MYNET1
And this has just one network address 10.123.53.0/24.

How would I configure it not to use public ips?

[jjasghar]

A little bit farther down the readme.

The openstack_network_name is used to select IP address for SSH connection. It's recommended to specify this option in case of multiple networks used for instance to provide more control over network connectivity.

[equick]

Ahh sorry didn't realise you were quoting the README before. I may have misunderstood because I configured openstack_network_name the same as network_ref in my .kitchen.yml (for example):

network_ref: MYNET1
openstack_network_name: MYNET1

But got the following error:

$ kitchen create -----> Starting Kitchen (v1.4.2)
-----> Creating <default-centos-65>... OpenStack instance with ID of <610cb2c2-ee88-4e0d-ac64-de5be664983e> is ready.
>>>>>> Server (610cb2c2-ee88-4e0d-ac64-de5be664983e) not reachable. Destroying server... OpenStack instance <610cb2c2-ee88-4e0d-ac64-de5be664983e> destroyed.
>>>>>> ------Exception------- >>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [undefined methodaddresses' for {}:Hash]
>>>>>> ---------------------- >>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try runningkitchen diagnose --all` for configuration

[jjasghar]

Ah yeah so it seems you're OpenStack cloud is pretty radically different then everything we've tested on.

can you put the whole .kitchen/logs/kitchen.log in a gist? I need to see more of that error.

Then can you take a step back go back to your original problem and get me the gist of that too? I'd like to compare them.