This field has been replaced by orm_target_image_file.file_size, which stores the size for each rootfs file produced for a certain target.
This is not a bug. The image_size field, not currently used, is intended to cache the uncompressed target image file size (i.e. the largest image_size for the target) to facilitate disk size computations.
Verified.