Yes, this is a known issue that’s been around since release 3.0.15 of the image. It does not actually break anything with the node and can be safely ignored. It will be fixed in a forthcoming version of the asl3 package - it just didn’t make it into this round.
it was “fixed” in asl3-pi-appliance 1.9.0-3. A full fix will be released in the forthcoming 1.9.0-5. That file shouldn’t even exist and is safely deleted.