It wasn't a glitch. They clarified it on their twitter account. However, what is not known is if the update truly reflects the status of our application. As it stands, somebody whose file just got transferred to the local VO or somebody who is about to get his/her DM, both kind of applicants have received the background check update.
To elaborate further, from gcms notes we know that the local VO officer triggers the background check once he passes an applicant's eligibility. The internal status at this point is 'Recommend Pass'. What we need ircc to clarify is if the system update checked the internal 'Recommend Pass' status to update the background check or it simply read the external and inaccurate 'Not Applicable' status.
If its the former, then its good news. If not just another useless change in status semantics.