Reliably build the subnode_ip_pair

Since the change I9617dafff83f800ed75b4478c7040301b0c944a1 there is
now 2 private network interfaces, so using the networks list to return
subnode_ip_pair now returns 3 entries, which breaks the reproducer.

This change returns the IP addresses from the floating IP, so that any
changes to the subnode networking won't cause issues here again.

Change-Id: I3f20e34e03874cfbd4701c70f9818141568b4d55
This commit is contained in:
Steve Baker 2018-06-15 10:53:30 +12:00
parent 1340ff513f
commit 1329dc1fd1
1 changed files with 3 additions and 1 deletions

View File

@ -52,4 +52,6 @@ resources:
outputs:
subnode_ip_pair:
description: IP addresses of subnode in network
value: { get_attr: [ subnode, networks, {{ private_net_name }} ] }
value:
- get_attr: [subnode_floating_ip, fixed_ip_address]
- get_attr: [subnode_floating_ip, floating_ip_address]