Tuesday, 2021-06-01

*** XinxinShen has joined #openstack-masakari00:53
*** suzhengwei has joined #openstack-masakari05:48
*** suzhengwei has quit IRC05:51
*** suzhengwei has joined #openstack-masakari05:52
*** XinxinShen_ has joined #openstack-masakari05:53
*** XinxinShen has quit IRC05:53
*** XinxinShen_ has left #openstack-masakari05:55
*** XinxinShen has joined #openstack-masakari05:55
*** jopdoro has joined #openstack-masakari06:01
jopdorojoin #openstack-masakari06:01
jopdoroHi06:02
*** jegor has joined #openstack-masakari06:02
jegorHi06:02
yoctozeptomeeting in a moment06:03
yoctozeptodealing with tech issues06:03
jegorOk06:03
*** jopdoro has quit IRC06:04
*** jegor is now known as jopdorp06:04
suzhengweihi06:05
yoctozeptook, sorry06:06
yoctozepto#startmeeting masakari06:06
opendevmeetMeeting started Tue Jun  1 06:06:14 2021 UTC and is due to finish in 60 minutes.  The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot.06:06
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:06
opendevmeetThe meeting name has been set to 'masakari'06:06
yoctozepto#topic Roll-call06:07
yoctozeptobot broke06:07
yoctozepto\o/06:07
jopdorp\o/ \O/06:07
yoctozeptohi jopdorp06:07
yoctozeptohi suzhengwei06:07
suzhengwei0/06:07
yoctozeptoglad to see you in the new network06:08
jopdorpoftc!06:08
yoctozepto#topic Agenda06:08
yoctozepto* Roll-call06:08
yoctozepto* Agenda06:08
yoctozepto* Announcements06:08
yoctozepto* Review action items from the last meeting06:08
yoctozepto* CI status06:08
yoctozepto* Backports pending reviews06:08
yoctozepto* Xena planning -> https://etherpad.opendev.org/p/masakari-xena-ptg06:08
yoctozepto* Open discussion06:08
yoctozepto#topic Announcements06:09
yoctozeptoit's kind of obvious but we moved IRC channels to the new network - OFTC - that we are currently on06:09
yoctozeptothis information probably makes more sense in the saved logs read externally because you clearly know it being here ;-)06:10
yoctozepto#topic Review action items from the last meeting06:10
yoctozeptothere were none06:10
yoctozepto#topic CI status06:10
yoctozeptoI saw it green recently06:10
yoctozepto#topic Backports pending reviews06:11
yoctozeptonone06:11
yoctozepto#topic Xena planning -> https://etherpad.opendev.org/p/masakari-xena-ptg06:11
yoctozeptook, this is the interesting part06:11
yoctozeptohave we got more progress?06:11
jopdorpnot from my side06:13
yoctozeptook06:13
suzhengweiupdate https://review.opendev.org/c/openstack/masakari/+/78838206:15
yoctozeptoI saw suzhengwei commented on my comment06:15
yoctozeptooh, right, that one06:16
yoctozeptoI have not read it yet06:16
suzhengweino hurry06:17
yoctozeptoread it06:17
yoctozeptobut I'm not sure if you agree with me or disagree06:18
yoctozeptowas there any issue with the flow I presented in my comment?06:18
suzhengweiMy opinion, no need wat for the result if it disable or force-down nova-compute service.06:19
suzhengweiThere is no asynchronous call in nova inside.06:20
yoctozeptowell, if we check if it's up and it is, then we should try checking for it going down; if nova still sees the host, then we could say either abort or force it down and continue (this could be up to the user's choice)06:21
suzhengweiThe return of calls to nova-api can show whether the status/state has changed sucessefully.06:21
suzhengweiwe check if it's up just because we are not sure it has been fenced.06:23
suzhengwei the nova-compute diable or not will not stop evacuation. but down or not matters.06:25
yoctozeptosuzhengwei: yes, we don't know if it's down precisely ;-)06:26
yoctozeptoalso06:26
yoctozeptoif nova thinks it's up and it's actually down, then it will fail disabling the service as well06:26
yoctozeptoI think disabling the service is an extra such that the host does not come into play if it gets back on and needs operator's intervention06:27
yoctozeptothe order of actions is unfortunate though, I pointed you at the relevant bug reports06:27
suzhengweiyep, we can disable the compute firstly, but I don't think need to wait. the enable_disable_service call returns show something.06:31
suzhengweiIt the call failed, it will raise exception.06:31
yoctozeptosuzhengwei: but it waits06:32
yoctozeptolast time I checked, there was some serious delay06:32
yoctozeptobecause the disable wanted to speak via mq to the nova-compute service06:32
suzhengweibut it is synchronous calls in nova inside. think that if nova-compute already down, which one to disable or force-down the compute service.06:37
suzhengweinot nova-compute, all in the nova-api.06:38
suzhengweiif it dellay, the call would respone dellay too.06:38
suzhengweidelay06:39
yoctozeptosuzhengwei: yeah, it's synchronously waiting for an answer on mq06:40
yoctozeptoif nova-api thinks nova-compute is up06:40
yoctozeptobut it's actually not06:40
yoctozeptothen disabling it is going to timeout06:40
yoctozeptotry it out locally06:41
yoctozeptojust without masakari, ensure nova-compute has just been confirmed to be up, then firewall that host away and try disabling the service in nova06:41
suzhengweiI am very sure.06:41
suzhengweiEven the compute node down. I can still disable or force-down it freely.06:42
yoctozeptoif nova knows it's down, then yes06:43
yoctozeptoif nova thinks it's up but it's not, timeout06:43
yoctozeptounless they changed that in recent series06:43
yoctozeptobecause that's what it was in ussuri for sure06:43
yoctozeptoI suggest you check and I will check as well06:46
suzhengweithe code in nova project. service_update_by_host_and_binary function in nova/compute/api.py06:49
suzhengweiIt just changes db in the nova-api process.06:50
yoctozeptosuzhengwei: but it finally calls https://github.com/openstack/nova/blob/5cf06bf33d8f187d444f812177946e134e4c9932/nova/compute/api.py#L586306:53
yoctozeptowhich has the unfortunate self.rpcapi.set_host_enabled06:53
yoctozeptoand it usually just timeouts06:54
suzhengweioh, i see. It need synchronous with pacement. But it save status first, then rpcapi.set_host_enabled.06:57
suzhengweiplacement06:57
yoctozeptosuzhengwei: yeah, I would say it's an edge situation on nova's side06:59
yoctozeptook, the point is we are disabling the service as a service for the operator and not because we require it06:59
yoctozeptoand we have to end the meeting06:59
yoctozeptothanks for the discussion, that was a fruitful meeting07:00
yoctozeptosee you next time07:00
yoctozepto#endmeeting07:00
opendevmeetMeeting ended Tue Jun  1 07:00:10 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:00
opendevmeetMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-06-01-06.06.html07:00
opendevmeetMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-06-01-06.06.txt07:00
opendevmeetLog:            http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-06-01-06.06.log.html07:00
jopdorpthanks!07:02
jopdorpsee you next time07:02
*** XinxinShen has quit IRC07:07
*** suzhengwei has quit IRC09:35
*** suzhengwei has joined #openstack-masakari09:57
*** suzhengwei has quit IRC10:58
*** suzhengwei has joined #openstack-masakari11:14
*** suzhengwei has quit IRC12:40
*** opendevreview has quit IRC14:44
*** suzhengwei has joined #openstack-masakari15:32
*** suzhengwei has quit IRC15:42

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!