Nevermind, I had ran the migration and resulted on a faulty state. Evidently the schema was trying to do a dropcolumn on a non-existant column.

If your migrations are related between them, in example:

1. First migration create the posts table.
2. Second migration create the comments table with a foreign key that use the first posts table.

And later you create a migration that drop the table posts, you need first at all delete the messages table and them delete the posts table, or drop the foreign key index from the comments table and then delete the posts tables with the result of a orphan comments table that later could be related with another table.

Hope it helps you.