I have figured out it is indeed a misplaced link address: …-raspberrypi4-mender-convert-3.0.0.img.xz. I have changed it to …-raspberrypi3-mender-convert-3.0.0.img.xz and it works, so I have updated the tables with the correct link.
PS some file sizes and SHA256 were wrong - I fixed those. Moreover, I have added 2022-09-22 image in from Downloads | Mender documentation
I have checked 2023-05-03 img for RPi 3B+. At the moment of writing, it is the latest bullseye version available for RPI 3B+.
I have followed following flow to confirm the operational of the image:
The Mender service launches properly - confirmed
Bootloader environment tools are present on the device - confirmed (default U-Boot integration used)
Identify A/B partitions - confirmed
Confirm OS switch using bootloader variables - confirmed
Identify the transitions state
a) Confirm behavior for the ‘successful update’ case - confirmed
b) Confirm behavior for the ‘failed update and rollback’ case - confirmed
My setup at the time of testing:
Hosted mender 3.7.0
mender-artifact 3.11.0
mender-convert 4.1.0
mender-client 3.5.2 installed (!!!)
At the moment of writing, mender-client 4.0.0 is coming close to its release date and when using latest as mender-client version selector for mender-convert, it already uses 4.0.0 client. However, it seem that mender-convert tool is not yet ready to fully support mender-client 4.0.0 install yet - in my case, there were no mender packages installed after dumping the image to SD card. Hence, I have pinned the known-to-work version of mender-client to 3.5.2 to be installed during mender-convert. This is not the issue of the updated image. It is more of the issue of mender-client & mender-convert interaction.
Another side note - this image of RPi OS renamed boot partition to bootfs (this affects only when when SD card is connected via SD card adaptor). When SD card is plugged into an RPi, within RPi OS it is still mounted under /boot.
mender-convert does not care about this change (same as any other dependency within Mender eco-system), but I still find it worth mentioning as this step within manual will now fail as it has to point to RPI_BOOT="/media/$(whoami)/bootfs"
PS I am unsure of the procedure in place to generate a publicly shareable image with mender integrated - my current one has lots of modifications applied already, am not willing to share it.
Hey @dmitrijsan, the issue with Mender 4.0.0 is known, and we are currently working on a new version of mender-convert which will default to 3.5.2, since 4.0.0 is not quite ready to work with mender-convert yet. Pinning the version like you have done is indeed the best workaround, for now.
Thanks for confirming. Since it is not the issue of the RPi image itself, I am going to keep Raspberry Pi OS image from 2023-05-03 within the compatibility list as supported.