User-Agent: Opera/9.80 (Windows NT 5.1; U; en) Presto/2.2.15 Version/10.10 Build Identifier: 3.4.2 Hi, I recently installed Bugzilla on a Debian box (Linux version 2.6.18-6-686-bigmem (Debian 2.6.18.dfsg.1-24etch4)) running MySQL 5.0.32. On running checksetup I got the following error message: DBD::mysql::db do failed: Can't create table './bugs/#sql-cad_28a17.frm' (errno: 150) [for Statement "ALTER TABLE keywords ADD CONSTRAINT fk_keywords_bug_id_bugs_bug_id FOREIGN KEY (bug_id) REFERENCES bugs(bug_id) ON UPDATE CASCADE ON DELETE CASCADE"] at Bugzilla/DB.pm line 515 Bugzilla::DB::bz_add_fk('Bugzilla::DB::Mysql=HASH(0x9458244)', 'keywords', 'bug_id', 'HASH(0x9475a24)') called at Bugzilla/DB.pm line 450 Bugzilla::DB::bz_setup_foreign_keys('Bugzilla::DB::Mysql=HASH(0x9458244)') called at Bugzilla/Install/DB.pm line 567 Bugzilla::Install::DB::update_table_definitions('HASH(0x8402450)') called at ./checksetup.pl line 191 I reran checksetup and then it continued without error messages. Reproducible: Didn't try
Thanks for the bug report. There is no Bugzilla 3.4.2--did you mean 3.2.4? In any case, error 150 just means that there's some invalid foreign key constraint, which Bugzilla actually checks for. The only remaining reasons that that would happen are bug 508181 or some customization you made to your database. In any case, if you have any trouble with Bugzilla as a result of this, the support list would be the place to go, probably: http://www.bugzilla.org/support/
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
> There is no Bugzilla 3.4.2--did you mean 3.2.4? whoops, I meant 3.4.1 > that would happen are bug 508181 or some customization you made to your > database. i think both do not apply as this was a fresh install with a newly created database.
(In reply to comment #2) > i think both do not apply as this was a fresh install with a newly created > database. Weird. Sounds like it was probably some random fluke then.
yeah, just thought i´d let you know (and for others to find the bug if that ever happens again)
You need to log in before you can comment on or make changes to this bug.