Hi Bharat, Just create an empty schema called “magnum” before running the migrations. The tool assumes that the db is there. Thanks, Thodoris

On 25 Jun 2019, at 12:54, Bharat Kunwar <bharat@stackhpc.com> wrote:

Hi Theodoros,

Just replying to your message on IRC here as you appear offline.

...

if you don't care for what you have in the db i would do this: - stop both api and conductor - drop magnum db - checkout master - run the migrations (from master)

After getting this far, I tried running `magnum-db-manage upgrade` but I hit this:

sqlalchemy.exc.InternalError: (pymysql.err.InternalError) (1049, u"Unknown database 'magnum'") (Background on this error at: http://sqlalche.me/e/2j85)

...

- start the services

I can’t start the services either but that is probably due to lack of a database…

...

- create a cluster - checkout magnum_nodegroups - stop services - run migrations - start the services I know it's not great…

Would you mind letting me know where I’m going wrong?

Thanks

Bharat