Closed Bug 68567 Opened 24 years ago Closed 23 years ago

Upgrade from 2.10 to 2.11 with sanity check finds errors.

Categories

(Bugzilla :: Bugzilla-General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: tanner, Assigned: justdave)

Details

I upgraded from 2.10 to 2.11 and ran the sanity check and got the following errors: OK, now running sanity checks. Checking references to keyworddefs.id ... from keywords.keywordid Checking references to fielddefs.fieldid ... from bugs_activity.fieldid Checking references to bugs.bug_id ... from bugs_activity.bug_id Bad value 350 found in bugs_activity.bug_id ... from attachments.bug_id ... from cc.bug_id ... from longdescs.bug_id ... from dependencies.blocked ... from dependencies.dependson ... from votes.bug_id ... from keywords.bug_id Checking references to profiles.userid ... from bugs.reporter ... from bugs.assigned_to ... from bugs.qa_contact ... from attachments.submitter_id ... from bugs_activity.who ... from cc.who ... from votes.who ... from longdescs.who ... from namedqueries.userid Checking references to profiles.login_name ... from components.initialowner Bad value bugs@real-time.com found in components.initialowner Checking passwords Checking groups Checking version/products Bug(s) found with invalid product/version: Food For Hungry/ Checking milestone/products Checking components/products Checking profile logins Checking cached vote counts Checking keywords table Checking cached keywords Sanity check completed. Running this same under 2.10 I do not get these errors.
Your report didn't say... did you run ./checksetup.pl after the update?
a) you don't have a bug #350. b) bugs@real-time.com doesn't have an account on your system These are things that, in those places, I think are new checks that were added to sanitycheck.cgi since 2.10 came out. It's quite likely these errors were already in your database and the 2.10 version didn't check for them. I know this for a fact for the email address checks for initialqa and initialowner. 2.10 didn't check to make sure those were legal.
I did run ./checksetup.pl after the upgrade. Manually go through the database and fix these errors then?
Probably you had a bug 350 at one time and you deleted it. The only way to fix that one will be with raw SQL in the database, to remove the references to it from the bugs_activity table. As for the bad email address, you can fix that from editcomponents.cgi if you know which component that email address is an initialowner for. You just need to make sure that component has a valid login name for someone who is on your bugzilla system.
Dave, I wouldn't say for sure that 350 existed. We've seen circumstances where people typed an invalid bug number and stuff got created for it. But the fact that it is bugs_activity is a little indicative of your suggestion. If the reporter agrees that this bug was deleted then we can close this out, because there really isn't any bug here that hasn't already been fixed other than that bug deletion should remove references to itself as necessary.
tanner@real-time.com, have you managed to clean up these errors? As far as I can see, there's nothing for us to do here.
I'll mark this RESOLVED INVALID in a month if no reply is received from the reporter, since there's been no bugs identified here.
Resolved as per above.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.