Hi Andre, It looks like this is fixed in 16.2.2, 21.1.2.14-patch1-2, and 22.1 (per xos0063769).
It seems to be harmless and is a result of an incorrect read of an install status field. As Jeremy suggested, since everything seems to be running fine on the new code, there doesn't seem to be a need to worry about it.