hi team, we recently updated our metaflow version ...
# ask-metaflowb
bulky-portugal-95315
06/23/2025, 6:57 PMhi team, we recently updated our metaflow version to 2.5.0 and we seem to have lost metadata around the ec2-instance-id and ec2-instance-type for our batch jobs. Was this intended or moved somewhere else?
✅ 1
a
ancient-application-36103
06/23/2025, 7:13 PMwhich version did you move from?
b
bulky-portugal-95315
06/23/2025, 7:26 PMv2.4.13
a
ancient-application-36103
06/23/2025, 7:26 PMnothing should have changed
b
bulky-portugal-95315
06/23/2025, 7:28 PMwe updated metadata service images from
netflixoss/metaflow_metadata_service:v2.4.13netflixoss/metaflow_metadata_service:v2.5.0tasks_v3ec2-instance-idec2-instance-typebulky-portugal-95315
06/23/2025, 9:16 PMwe still see it in the UI for the old jobs, but it seems like it’s not being logged in the database for the new ones
a
ancient-application-36103
06/23/2025, 9:45 PMyou may want to check if this is executing as expected
👀 1
b
bulky-portugal-95315
06/23/2025, 9:49 PMthanks Savin, yeah we’ll dig in and see
s
square-wire-39606
06/24/2025, 5:03 PMthanks for the bug fix! it will go out in the next release
square-wire-39606
06/24/2025, 5:04 PMi wonder how this slipped through for such a long time
b
bulky-portugal-95315
06/24/2025, 5:20 PMyeah it was kind of surprising to find that IMDSv2 wasn’t working correctly, i guess most teams were still on IMDSv1 since it wasn’t being pushed as much
bulky-portugal-95315
06/24/2025, 5:20 PMwe migrated to IMDSv2 recently so this bit us on the same timeline, all versions or our extensions library, even old ones
🙌 1