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.
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.
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] providers= DynamicJSON dynamic_ targets= cloud-init@http:// localhost: 8780
vendordata_
vendordata_
On the affected VM:
curl http:// 169.254. 169.254/ openstack/ latest/ vendor_ data2.json config\ npackage_ upgrade: True\npackages:\n - black\nfqdn: cloud-overridde n-by-vendordata 2.example. org."}
{"cloud-init": "#cloud-
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