It seems like commit https://github.com/openstack-infra/shade/commit/ba0e9451e664743d made a change that added `key=operator.itemgetter('created_at')`. This key doesn't seem to exist in all neutrons (at least in our liberty one) and I believe shade (and clients in general) are supposed to work across releases and clouds (so in our local jenkins where we use shade this borked).
The error that is happening (until we fixed pip requirements to a older release is):
....
File "/home/jenkins/workspace/redeploy_static_slaves@2/slaves/.venv/lib/python2.7/site-packages/shade/openstackcloud.py", line 5028, in add_ip_list
fixed_address=fixed_address)
File "/home/jenkins/workspace/redeploy_static_slaves@2/slaves/.venv/lib/python2.7/site-packages/shade/openstackcloud.py", line 4721, in _attach_ip_to_server
nat_destination=nat_destination)
File "/home/jenkins/workspace/redeploy_static_slaves@2/slaves/.venv/lib/python2.7/site-packages/shade/openstackcloud.py", line 4865, in _neutron_attach_ip_to_server
nat_destination=nat_destination)
File "/home/jenkins/workspace/redeploy_static_slaves@2/slaves/.venv/lib/python2.7/site-packages/shade/openstackcloud.py", line 4828, in _nat_destination_port
reverse=True):
KeyError: 'created_at'
This key seems to be added in mitaka(?) via https://specs.openstack.org/openstack/neutron-specs/specs/liberty/add-port-timestamp.html ? but it seems like the code should be made tolerant so that it can work with older clouds; so perhaps a key error should be caught and the older routine should be used.
Thoughts?
