1498922 - SQL foreign key error when trying to open "new bug" form

Status: RESOLVED FIXED

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Florian Pritz]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce:

Click on the "New Bug" button on the front page or open "../enter_bug.cgi" in the browser directly.

harmony/master 7556469b5c1ff1083c408c6d0ef6642122a42def; fresh database; NOT yet logged in as any user


Actual results:

DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`bugzilla`.`tokens`, CONSTRAINT `fk_tokens_userid_profiles_userid` FOREIGN KEY (`userid`) REFERENCES `profiles` (`userid`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement "INSERT INTO tokens (userid, issuedate, token, tokentype, eventdata)
        VALUES (?, NOW(), ?, ?, ?)"] at /srv/http/bugzilla/Bugzilla/DB.pm line 61.


Expected results:

Should get the new bug form

Comment 1

[Florian Pritz]

With 480e3572661cc856591e0aa11b5eb023338558ed:

DBD::mysql::db do failed: Cannot add or update a child row: a foreign key constraint fails (`bugzilla`.`tokens`, CONSTRAINT `fk_tokens_userid_profiles_userid` FOREIGN KEY (`userid`) REFERENCES `profiles` (`userid`) ON DELETE CASCADE ON UPDATE CASCADE) [for Statement "INSERT INTO tokens (userid, issuedate, token, tokentype, eventdata)
        VALUES (?, NOW(), ?, ?, ?)"] at /srv/http/bugzilla/Bugzilla/Token.pm line 546.

Comment 2

[Mark Côté [:mcote]]

This is likely a result of all the users having been logged out on Saturday during the deployment of a security fix.  If you appear to still be logged in, please log out and back in again.  I'm able to get to the enter_bug form so that should work for you.

Comment 3

[Florian Pritz]

That bug is about a local harmony install, not about BMO. Also Dylan fixed it already with commit a7bb5a65b71644d9efce5fed783ed545b9336548 if I'm not mistaken.

Comment 4

[Dylan Hardison [:dylan] (he/him)]

(In reply to Mark Côté [:mcote] from comment #2)
> This is likely a result of all the users having been logged out on Saturday
> during the deployment of a security fix.  If you appear to still be logged
> in, please log out and back in again.  I'm able to get to the enter_bug form
> so that should work for you.

This isn't about BMO, no worries. :)

Comment 5

[Dylan Hardison [:dylan] (he/him)]

(and this is fixed)