04:01:29 #startmeeting masakari 04:01:30 Meeting started Tue Sep 10 04:01:29 2019 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:33 The meeting name has been set to 'masakari' 04:01:38 Hi all for masakari 04:01:48 Hi 04:01:52 Hi all 04:01:53 tpatil: Hi 04:01:58 shilpasd: Hi 04:02:16 #topic Critical bugs and patches 04:02:33 Any critical bugs or patches need to discuss here? 04:03:30 observed zuul failure because of novaclient.exceptions.EndpointNotFound removal 04:03:44 on patch https://review.opendev.org/#/c/673526/ 04:04:28 this patch is for https://bugs.launchpad.net/horizon/+bug/1838417 04:04:29 Launchpad bug 1838417 in masakari "Notification related functional tests fails randomly due to KeyError" [Undecided,In progress] - Assigned to Shilpa Devharakar (shilpasd) 04:05:23 observed masakri refers novaclient version 9.1.0 and we have 15.0.0 running as latest 04:06:27 in requirements.txt, novaclient >=9.1.0 04:06:28 shilpasd: that novaclient version 9.1.0 is set as a requirement for masakari? 04:06:45 tpatil: thanks 04:08:03 so the question is do we need to upgrade the novaclient lower_constraints to 15.0.0 04:08:48 tpatil: thanks 04:09:15 looking at the code, there is no need to do that as it will always install the newer version 15.0.0 and even if 9.1.0 is installed, it won't cause issue as we are now using NotFound exception instead of EndpointNotFound 04:09:37 NotFound exception is present in 9.1.0 04:11:01 tpatil: got it. then no problem. 04:11:11 samP: OK, thanks 04:11:18 New bug : https://bugs.launchpad.net/masakari/+bug/1843035 04:11:19 Launchpad bug 1843035 in masakari "masakari sets node as "under maintenance" and does not evacuate" [Undecided,New] 04:11:39 tpatil: thanks. I wanted to bring this up 04:13:13 tpatil: can you please reproduce this issue? 04:14:30 first let me understand the steps 04:15:21 after nova-compute service and pacemaker remote is restarted, the processes are kill using -9 04:15:43 when the node comes up again, means user is reboot the compute node? 04:15:50 s/reboot/rebooting 04:17:40 I have posted this comment on the LP bug 04:18:44 it seems like user/operator bring it up manually 04:19:14 and, I can not access to the log files links in the LP bug 04:19:30 and after that, operator will set on_maintenance flag to False 04:20:58 If the on_maintenance flag is set to True, then evacuated won't be performed. 04:21:15 becoz of HostOnMaintenanceError 04:21:23 we have added this business rule 04:22:38 tpatil: correct. 04:22:52 and I think same error masakarihostmonitor must be logging as well as it's not able to send the notification successfully. 04:23:46 tpatil: why masakarihostmonitor? 04:24:20 you mean the masakarihostmonitor process in the on_maintenance node? 04:25:12 for this bug, I think bug reporter is imitating the scenario but in real case, hostmonitor will log this error from another compute node 04:26:18 it all depends on pacemaker cluster node status 04:29:02 Anyway, not evacuating in the on-maintenance mode it not a bug. That is how it works. 04:29:24 Correct 04:29:32 The question is whether repoter wants to change it or not. 04:30:14 I also want to check the masakari logs 04:30:54 Problem is, we don't have access to those 04:32:37 I left a comment for that 04:32:48 ok, thanks 04:35:03 Any other issues? 04:35:46 No 04:36:16 thanks 04:36:22 #topic Train work items 04:36:38 please share if you hae any update on train work items 04:37:21 regarding masakari documentation, internal review implementation is in progress, will upload patch to community gerrit today 04:37:32 shilpasd: thanks 04:38:06 shilpasd: what about masakarimonitors? 04:39:31 will try to upload for monitors by tomorrow 04:39:38 to community gerrit 04:40:35 shilpasd: Ok, Thanks 04:43:59 shilpasd: tpatil: thanks 04:44:15 Any other updates? 04:44:32 if not we could finish todays's meeting 04:45:10 No other updates from my side 04:45:24 tpatil: Thanks 04:45:45 OK then, let's finish today's meeting. 04:45:52 thanks all 04:45:57 Thanks all 04:46:10 #endmeeting