c42-adam

I have confirmed downgrading to 3006.2 resolved the issue.

Still an issue in 3006.4, though it's no longer throwing a stack trace. It just returns an empty object instead of the correct data. ``` $ sudo salt-call grains.get dynamic:instance-identity...

Just wondering if we are going to see some movement on this. Some additional info: I verified that metadata is enabled on multiple affected instances, and that IMDSv2 is set...

This doesn't appear to be working for me with 3006.6. Testing with salt-call locally is still the same result as above. If I test from the salt master, it just...

> How did you install this minion? I used salt-bootstrap, I don't recall the exact command but it used onedir and it was probably installed to version 3004 or 3005,...

I used `apt purge salt-common salt-minion` and then went and manually removed /etc/apt/sources.list.d/salt.list, /var/run/salt /opt/Saltstack and /var/cache/salt. I left my /etc/salt folder alone since it was just minion config and...

> @c42-adam and @mdschmitt , these VM's, do they have IMDS set to v1 or v2? IMDSv2 is set to Optional, and I can successfully query IMDSv1 with curl from...

@mdschmitt I ended up abandoning the built-in metadata and implemented my own. I based it on this: https://github.com/bluprince13/aws-metadata-json/tree/master It pulls in things _slightly_ differently, for instance numbers instead of numbers...

@mdschmitt unfortunately because it was for work policy prevents me from sharing it. Sorry.