Comment 6 for bug 1841104

Hello @mmahalwa!

Your json looks to have an extra layer around it. I believe that your issue is that you are feeding in your meta data with the testing@ name in your nova.conf.

As I interpret the metadata docs, testing@ would be metadata to be consumed by a service called 'testing' (or, realistically, not at all.) If I run a similar test with cloud-init@ instead it seems to work as expected.

From nova.conf:

[api]
vendordata_providers=DynamicJSON
vendordata_dynamic_targets=cloud-init@http://localhost:8780

On the affected VM:

curl http://169.254.169.254/openstack/latest/vendor_data2.json
{"cloud-init": "#cloud-config\npackage_upgrade: True\npackages:\n - black\nfqdn: cloud-overridden-by-vendordata2.example.org."}

This seems like the right behavior to me but I'm open to suggestions if you think that the <name> value in nova.conf is intended to have a different meaning.

-Andrew