| *** irclogbot_0 has joined #senlin | 00:24 | |
| *** irclogbot_0 has quit IRC | 00:40 | |
| *** irclogbot_1 has joined #senlin | 01:28 | |
| *** irclogbot_1 has quit IRC | 01:48 | |
| *** __ministry has joined #senlin | 01:53 | |
| *** irclogbot_3 has joined #senlin | 02:48 | |
| *** sapd1 has quit IRC | 05:09 | |
| *** __ministry has quit IRC | 09:29 | |
| *** sapd1 has joined #senlin | 11:20 | |
| *** sapd1 has quit IRC | 11:36 | |
| dtruong | No, I haven't seen this problem. | 17:28 |
|---|---|---|
| dtruong | rm_work Were you able to figure the problem with the db_sync? | 17:32 |
| rm_work | yes | 17:35 |
| rm_work | too many engineers | 17:35 |
| rm_work | we'd had an upgrade run and a revert for some reason unrelated | 17:35 |
| rm_work | and then our CD tried to deploy the DB upgrade again? | 17:36 |
| rm_work | though I *thought* the upgrade manager script should have detected it was already on v15 and not tried? but it doesn't i guess? | 17:36 |
| dtruong | There is a migrate_version table in senlin DB that tracks the current DB version. | 17:41 |
| dtruong | If that somehow was reverted to an older version, the db_sync will try to upgrade again. | 17:42 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!