Monday, 2019-12-09

*** irclogbot_0 has joined #senlin00:24
*** irclogbot_0 has quit IRC00:40
*** irclogbot_1 has joined #senlin01:28
*** irclogbot_1 has quit IRC01:48
*** __ministry has joined #senlin01:53
*** irclogbot_3 has joined #senlin02:48
*** sapd1 has quit IRC05:09
*** __ministry has quit IRC09:29
*** sapd1 has joined #senlin11:20
*** sapd1 has quit IRC11:36
dtruongNo, I haven't seen this problem.17:28
dtruongrm_work Were you able to figure the problem with the db_sync?17:32
rm_worktoo many engineers17:35
rm_workwe'd had an upgrade run and a revert for some reason unrelated17:35
rm_workand then our CD tried to deploy the DB upgrade again?17:36
rm_workthough 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
dtruongThere is a migrate_version table in senlin DB that tracks the current DB version.17:41
dtruongIf that somehow was reverted to an older version, the db_sync will try to upgrade again.17:42

Generated by 2.15.3 by Marius Gedminas - find it at!