04:00:15 <samP> #startmeeting masakari
04:00:16 <openstack> Meeting started Tue Mar 12 04:00:15 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:19 <openstack> The meeting name has been set to 'masakari'
04:00:22 <samP> Hi all
04:00:30 <tpatil> Hi
04:00:53 <samP> #topic High priority items
04:01:28 <samP> python-masakariclient 5.4.0 released
04:02:13 <samP> This release is for the stein. Branch will created later
04:03:52 <samP> We have about 2 weeks for other projects for their RCs
04:04:11 <samP> #topic Critical bugs and patches
04:04:32 <samP> Any critical bugs or patches need to discuss here?
04:04:59 <tpatil> # link : https://bugs.launchpad.net/masakari/+bug/1819422
04:04:59 <openstack> Launchpad bug 1819422 in masakari "Get Notification for API version 1.1 returns KeyError: 'progress_details'" [Undecided,In progress] - Assigned to Shilpa Devharakar (shilpasd)
04:05:12 <tpatil> Patch is uploaded : https://review.openstack.org/642462
04:05:31 <tpatil> There are few minor comments on this patch which will be fixed today
04:05:43 <tpatil> We should merge this patch soon
04:06:01 <tpatil> Also during regression testing, we have found one more bug which Shilpa will report in LP soon
04:06:40 <tpatil> If the recovery_flow is reserved, then it fails to execute task as it attempts to persists Host object and it fails
04:06:51 <tpatil> Shilpa is working on fixing this issue
04:08:24 <samP> tpatil: got it. I will review first patch as soon as it updates
04:09:35 <samP> second problem you mentioned above, is it happen every time where recovery_flow=reserved
04:09:37 <samP> ?
04:10:20 <tpatil> yes
04:11:38 <samP> that means, recovery_flow=reserved does not work at all, correct.
04:11:51 <samP> am I correct?
04:12:17 <tpatil> Yes, We will fix this issue soon
04:12:20 <samP> In that case, we must fix that before release. and need to backport as well.
04:12:24 <tpatil> Maybe today or tomorrow
04:12:43 <samP> tpatil: Sure, thanks.
04:13:09 <tpatil> When are you planning to cut stable/stein for masakari project?
04:14:50 <samP> Currently, I am planning to do it on 3/22
04:15:01 <samP> with the RC1
04:15:18 <tpatil> ok, we will fix this issue before that for sure
04:15:59 <samP> tpatil: if time is not enough, we can fix the master and backport to Stein. Because, this it critical issue
04:16:37 <samP> s/it/'is a'
04:16:47 <tpatil> We have already found out a solution to fix this issue
04:17:38 <samP> tpatil: great. then no problem at all
04:17:43 <samP> thank you.
04:18:49 <samP> Any other critical issues?
04:19:18 <tpatil> Still working on
04:19:23 <tpatil> regression testing
04:19:45 <samP> tpatil: no problem
04:21:31 <samP> if any, please bring them up anytime in this meeting
04:21:38 <samP> #topic Stein Work Items
04:21:39 <tpatil> Sure
04:21:49 <samP> Please share if you have any update on this
04:22:04 <tpatil> 1) Add progress details for recovery workflow
04:22:41 <tpatil> Dependency on openstacksdk, now 0.26.0 is released so we should merge dashboard patch soon
04:22:44 <tpatil> #link : https://review.openstack.org/#/c/640755/
04:23:35 <tpatil> I would like to thanks openstacksdk team to accept our patch at the last minute and release a newer version of openstacksdk.
04:24:24 <samP> tpatil: done.
04:24:35 <tpatil> samP: Thanks
04:24:57 <tpatil> 2)  Functional tests
04:25:09 <samP> tpatil: Thanks openstacksdk team!
04:25:24 <samP> Thanks openstacksdk team!
04:25:40 <tpatil> I will update patch to add functional tests to check recovery workflow details
04:25:43 <tpatil> #link : https://review.openstack.org/#/c/642223
04:27:06 <tpatil> From functional tests point of view, segments, hosts and notifications functional tests (Process/VM) are covered
04:27:25 <samP> tpatil: got it.
04:29:24 <tpatil> 3) Add devstack support for masakari-monitors
04:29:34 <tpatil> #link : https://review.openstack.org/#/c/638577/
04:29:48 <tpatil> Gate job is failing, working on fixing this issue
04:30:16 <tpatil> if we can find a fix for gate job, then we can install and deploy all monitors except host monitor
04:32:31 <samP> I think same error occur in Masakari 3rd party CI and Honjo-san is re-run the CI for fix this.
04:33:19 <samP> I will ask Honjo-san share if he have any info about his
04:33:24 <samP> s/his/this
04:33:38 <tpatil> samP: Yes, that will help
04:34:32 <samP> As you said, if can't fix this issue before release, then it is OK to remove host monitor
04:34:58 <tpatil> In the above patch, host monitor is not included at all
04:35:21 <tpatil> but still the gate job is failing
04:35:30 <tpatil> we want to install monitors only on nodes where compute service is running
04:36:02 <tpatil> we have made required changes in the masakari plugin but still it fails to install some neutron agent
04:36:06 <tpatil> on the compute node
04:36:11 <tpatil> looking into the sissue
04:37:11 <samP> tpatil: got it.
04:38:36 <tpatil> I have uploaded a new PS for checking  recovery workflow details
04:38:55 <tpatil> Once the gate job passes, please review and approve this patch : https://review.openstack.org/#/c/642223/
04:39:36 <samP> tpatil: sure, I will do that
04:39:52 <tpatil> samP: Thank you
04:43:43 <samP> Any other updates?
04:44:21 <samP> if not we can finish today's meeting
04:44:27 <tpatil> samP: No, That's all from my end
04:45:49 <samP> tpatil: thank you!
04:45:58 <samP> noting from my end.
04:46:11 <samP> Let's finish today's meeting
04:46:52 <tpatil> Ok
04:47:13 <samP> Please user #openstack-masakari IRC@free node or
04:47:41 <samP> openstack-discuss@lists.openstack.org for further discussions.
04:47:49 <samP> Thank you all!
04:47:52 <samP> #endmeeting