Using new dynamic metadata driver fails with a traceback:
ERROR nova.api.metadata.handler [req-d4df1623-dc4a-4e9c-b129-1e5dd76c59ac None None] Failed to get metadata for IP 10.0.0.3
TRACE nova.api.metadata.handler Traceback (most recent call last):
TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/handler.py", line 134, in _handle_remote_ip_request
TRACE nova.api.metadata.handler meta_data = self.get_metadata_by_remote_address(remote_address)
TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/handler.py", line 61, in get_metadata_by_remote_address
TRACE nova.api.metadata.handler data = base.get_metadata_by_address(address)
TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 660, in get_metadata_by_address
TRACE nova.api.metadata.handler ctxt)
TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 670, in get_metadata_by_instance_id
TRACE nova.api.metadata.handler return InstanceMetadata(instance, address)
TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 195, in __init__
TRACE nova.api.metadata.handler extra_md=extra_md, network_info=network_info)
TRACE nova.api.metadata.handler TypeError: __init__() got an unexpected keyword argument 'extra_md'
This is the configuration:
vendordata_providers = StaticJSON, DynamicJSON
vendordata_dynamic_targets = 'join@http://127.0.0.1:9999/v1/'
vendordata_driver = nova.api.metadata.vendordata_dynamic.DynamicVendorData
vendordata_dynamic_connect_timeout = 5
vendordata_dynamic_read_timeout = 30
vendordata_jsonfile_path = /etc/nova/cloud-config.json
What githash are you on here? Is there an easy way to replicate this?