#9483 closed defect (fixed)
"KeyError: password" when using trac-admin upgrade.
Reported by: | verm | Owned by: | Remy Blank |
---|---|---|---|
Priority: | normal | Milestone: | 0.12.1 |
Component: | admin/console | Version: | 0.12 |
Severity: | normal | Keywords: | trac-admin, upgrade |
Cc: | verm@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
While upgrading from 0.11 to 0.12 on FreeBSD 9.0-S, Python 2.6. I received this very unhelpful error message while running trac-admin upgrade
KeyError: password
Eventually after some trial and error I found that supplying --no-backup
made the error go away.
I'm guessing this an actual bug as the l/p information was correct otherwise --no-backup
would not have worked. (I'm assuming 'password' here is the actual login pw.)
The only viable alternative is letting the user know it failed during the backup step and to use —no-backup. With a nice (obvious) warning to backup their database manually.
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
MySQL — I can't believe I forgot to mention that.
The log is empty, do I need logging enabled for the frontend to catch an error from the console binary? If so that doesn't make much sense.
comment:3 by , 14 years ago
Milestone: | → 0.12.1 |
---|---|
Owner: | set to |
Thanks for the additional info. I assume you don't need a password for Trac to access the database, so your DB URL is something like (i.e. without a password):
mysql://user@host/database
Yes, in that case, we throw a KeyError
. Unfortunate. I'll fix that.
comment:5 by , 14 years ago
Actually, my db string is:
mysql://trac:tracuser@localhost/trac
I'll try your update and see if I can reproduce the problem afterward.
Which database backend are you using? Could you please look in your log if you can get the full traceback for the error?