Bootstrap is failing with this error: PG::UndefinedTable: ERROR: relation "ai_agent_mcp_servers" does not exist more stuff: in /etc/nginx/conf.d/discourse.conf I, [2026-03-30T15:32:25.835970 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'LOAD_PLUGINS=0 bundle exec rake plugin:pull_co…

[image] pfaffman: it looks like Claude (that’s what I used) doesn’t get a timestamp (NOT COOL, Claude), but just a date stamp and then adds a counter :facepalm: We do have this instruction in AI-AGENTS.md: AI-AGENTS.md 61da54b54 - Use `bin/rails generate…

So, here comes a bug report that ask.discourse.com wrote, but first, I want to share this bit that it offered: I decided to let it be itself, and not “blunt and short”. :rofl: (I didn’t roll on the floor, but I did, truly, laugh out loud. This seems like a credible report and likely better than …

I had to know what I would sound like. . . . Sure — here’s a more pfaffman-style version: This looks like a `discourse-ai` migration bug. Bootstrap dies in: ```text /plugins/discourse-ai/db/migrate/20260319070000_add_selected_tool_names_to_ai_agent_mcp_servers.rb with: PG::UndefinedTable: ERRO…

[image] pfaffman: This looks like a migration ordering issue in discourse-ai, or a missing earlier migration that should create ai_agent_mcp_servers. plugins/discourse-ai/db/migrate/20260319000001_create_ai_agent_mcp_servers.rb 61da54b54 create_table :ai_…

Aha. Here’s what happened. It seems to be because we both used AI and it’s stupid and lazy. An alternative explanation is that it’s bad luck, but it looks like Claude (that’s what I used) doesn’t get a timestamp (NOT COOL, Claude), but just a date stamp and then adds a counter, so we both were worki…

And I ran this from in your repo to take advantage of your superior knowledge of the AI. And I’m now vindicated in knowing that a team of experts can’t do any better than I am! So, yeah, Claude, WHY NOT USE GENERATE MIGRATION!?!?!? I changed the migration version in the database like this: UPDATE…

Yeah this instruction is ignored quite often. I keep having to correct it. I can try adding a “how to do migrations” skill, but maybe the atomic fix here is a lint. Not sure.

[image] sam: maybe the atomic fix here is a lint Yeah, that might work. Since lint isn’t AI, it always listens. If it’s going to ignore the request to get rails to write the migration, maybe a rule that explicitly states what the migration id/filename should be would work. I’ll be on the lo…

My buddy does not have that much personality. I’m not sure whether I’m relieved or jealous! :rofl:

Bootstrap error: relation "ai_agent_mcp_servers" does not exist -- due to migration id collision

Support Self-hosting

Falco (Falco) April 2, 2026, 2:30pm 10

Just had to re-do a migration that was failing into this issue.

My buddy wasn’t happy about it tho

1 Like

Topic		Replies	Views
Dev migration error: Discourse AI Dev ai	8	148	July 31, 2025
Upgrade failed: ERROR: relation "idx_regular_post_search_data" already exists Self-hosting	3	648	September 20, 2020
Relation "scheduler_stats" does not exist Support	3	1394	August 7, 2016
Update failed for some reason? Self-hosting	1	671	March 30, 2022
Rake db:migrate error Support	5	608	September 16, 2022

Bootstrap error: relation "ai_agent_mcp_servers" does not exist -- due to migration id collision

Related topics