Winnie81

Since this issue blocks some of our testing, hope it could be fixed. Thanks a lot.

> Hi @Winnie81, > > I took the time to investigate this again. The change comes from this commit [util-linux/util-linux@c90a8f1](https://github.com/util-linux/util-linux/commit/c90a8f1a3cdf116e050708098f0188349b55abc3), part of util-linux 2.37. You will note that in both...

> I understand that on 2983.2.0 `sdb` does not show up in `lsblk` output after rescan. Please check if `ls -l /dev/sdb` still shows that the underlying device node exists...

> @Winnie81 > > I've just created an ESXI environment with a Flatcar 2983.2.0 VM and using LSILogicParallel controller. The attached harddrive is called sdb. > > After hot-removing the...

I'd like to confirm whether there is any update for this issue. Thanks a lot.

Hi @pothos , I saw this issue was closed. I'd like to confirm whether OVT could be updated when performing in-place upgrade of Flatcar? Thanks a lot.

> Yes, it's in Flatcar Beta/Alpha but not yet in Stable. Once it lands in Stable the migration will happen after two updates, only then the old contents get removed...

> Two upgrade cycles are needed so that both of the A/B partitions have a version where the OEM software is provided in a systemd-sysext image, only then the old...

> Yes, the old partition still relies on the old version living on the OEM partition as extracted binaries. If you want to force a migration you can run `flatcar-update`...

> Running `sudo flatcar-update -V 3815.0.0` should give you the newest version on both partitions then. Thanks for your update. It works.