I found this StackOverflow post (https://stackoverflow.com/questions/31684664/liquibase-generatechangelog-missing-columns-statements-in-mariadb) and after reading it it occurred to me that the updates being done involve dropping a column in a table that is used by the one view in the database.
I tested this out, I create 2 databases from the original change log file and applied the diff changelog file to both databases. I dropped the view on one database and left it in the other database. I executed the generateChangeLog commands against both databases. I was able to generate a changelog file as expected from the database where the view was dropped. With the database with the old version of the view still in place, I generated the changelog file where the createTable tags were missing the column tags.
So the old view referencing recently dropped columns caused the issue. I am all good now.