Hi kata,

 

I’m sending this email as a heads-up that we plan to deprecate the “BlockDeviceRescan” API action in the next Firecracker release.

 

The block device rescan already happens as part of patching a block device with a new host file path, so this API call is redundant.

 

Looking at your code, I see that you’re only using it here after patching a drive path. You should simply remove that block of code since Firecracker already internally initiates a rescan on the patched block device if there is a guest running.

 

Please let me know if you have other use-cases for the `BlockDeviceRescan` action that I have missed, or any other concerns.

 

Thanks,

Adrian.