Bug in Omni block device wwid handling?

[brantgurga]

I've used Hyper-V in the past for trying Omni. Anyhow in a new hobby account in trial mode, Omni is displaying in the manually joined machines list: failed to marshal resource: json: error calling MarshalJSON for type runtime.protoMessage: proto: field specs.MachineStatusSpec.HardwareStatus.BlockDevice.wwid contains invalid UTF-8.
The talos image that booted and connected was 1.11.5 and the managed Omni instance is 1.3.2.
The requests are the ones made to (omni instance)/api/omni.resources.ResourceService/Watch

[brantgurga]

I was able to fetch the problematic resource and it looks like it is from the Hyper-V DVD drive.

                {
                    "buspath": "/LNXSYSTM:00/LNXSYBUS:00/ACPI0004:00/MSFT1000:00/6393d31a-9254-4dd2-857f-ea1e69677387/host0/target0:0:0/0:0:0:1",
                    "linuxname": "/dev/sr0",
                    "model": "Virtual DVD-ROM",
                    "name": "",
                    "readonly": false,
                    "serial": "",
                    "size": 346370048,
                    "systemdisk": false,
                    "transport": "storvsc_host",
                    "type": "CD",
                    "uuid": "",
                    "wwid": "t10.MSFT    s\\005\ufffdCw\\003TF\\224\\225}|\ufffdbJ}"
                }

[brantgurga]

I used SystemRescue 12.02 on this Hyper-V and a release one and when reading /sys/block/sr0/device/wwid it is present but gives a read error. On the newer canary build of windows in build 28000.1199, it produces the wwid string indicated above.

[brantgurga]

After fiddling with this and researching some other tickets, I couldn't directly delete the machinestatus resource in question, but deleting the link seemed to work. So this seems to have me back in a state where I can work with my instance till this issue gets addressed.