316379 - Sanity check doesn't like when bugs.rep_platform="" or bugs.op_sys=""

Status: NEW

(Bugzilla :: Bugzilla-General, defect)

Description

[Mike Miller]

User-Agent:       Opera/8.50 (Windows NT 5.1; U; en)
Build Identifier: 2.20

I just migrated from Bugzilla 2.18rc3 to 2.20.  The migration went very smoothly, the instructions were great.  :-)

The only issue I stumbled upon was that after the migration, Sanity_check in the section:

  Checking references to rep_platform.value 
  ... from bugs.rep_platform

found an error.  Spelunking into mysql, I found that there were instances where bugs.rep_platform was equal to "" (null string, not the NULL value).   To repair this, I inserted a platform of Unknown into the rep_platform table.  Then I ran the SQL:

  update bugs rep_platform="Unknown" where rep_platform="";

Now Sanity_check is happy once again.  Note that I ran Sanity_check in 2.18rc3 before the migration, and there were no errors.

I'm not sure if this is intended behavior or not, hence this report.

Reproducible: Didn't try

Steps to Reproduce:
I didn't try to reproduce it because my Bugzilla installation had already been migrated.

Comment 1

[Frédéric Buclin]

The same problem occurs with OSes:

Bad value "" found in bugs.op_sys

Moreover, it would help if the warnings would mention the affected bugs. This is something I would like to see fixed in 2.22 (or even 2.20).

Comment 2

[Frédéric Buclin]

The Bugzilla 3.0 branch is now locked to security bugs and dataloss fixes only. This bug doesn't fit into one of these two categories and is retargetted to 3.2 as part of a mass-change. To catch bugmails related to this mass-change, use lts081207 in your email client filter.

Comment 3

[Frédéric Buclin]

Bugzilla 3.2 is restricted to security bugs only. Moreover, this bug is either assigned to nobody or got no traction for several months now. Rather than retargetting it at each new release, I'm clearing the target milestone and the bug will be retargetted to some sensible release when someone starts fixing this bug for real (Bugzilla 3.8 more likely).