Wednesday, 2019-07-31

*** ricolin has joined #openstack-powervm01:01
*** ricolin has quit IRC01:31
*** ricolin has joined #openstack-powervm08:40
*** dikonoor has joined #openstack-powervm08:43
*** anuragmahanto243 has joined #openstack-powervm08:53
anuragmahanto243#startmeeting09:01
openstackanuragmahanto243: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'09:01
anuragmahanto243#startmeeting openstack-powervm09:01
openstackMeeting started Wed Jul 31 09:01:53 2019 UTC and is due to finish in 60 minutes.  The chair is anuragmahanto243. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: openstack-powervm)"09:01
openstackThe meeting name has been set to 'openstack_powervm'09:01
*** VedaAnnayappa4 has joined #openstack-powervm09:07
VedaAnnayappa4Hi Anurag09:07
VedaAnnayappa4what the current status of the CI, looks like it has broken again?09:07
anuragmahanto243#VedaAnnayappa4 Yes, on monday I was seeing the devstack services failing , i tried restarting the devstack services, but keystone was always failing09:09
anuragmahanto243so then I re-deployed the control node and management nodes.09:10
*** MujahidAli has joined #openstack-powervm09:10
MujahidAli+109:10
MujahidAlijoined09:10
anuragmahanto243yesterday, I could see in nodepool logs the templates were forming.09:11
anuragmahanto243but today , I recheck the nodepool log and hit "Max retries exceeded with url: /crumbIssuer/api/json (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f39080f2690>:"09:12
VedaAnnayappa4#anuragmahanto243 is the mysql right state?09:13
VedaAnnayappa4also if there any firewall that is blocking the call09:13
anuragmahanto243#VedaAnnayappa4 yes mysql service status is fine.09:14
VedaAnnayappa4#MujahidAli  had you encountered these issues before.. in your experience, why are the system so unstable09:15
MujahidAliI think it's problem with mysql.09:16
MujahidAliI looked into the logs and found that mysql reached maximum connection, the problem might occurred due to excessive restart of mysql or all the ports exhausted for mysql.09:17
VedaAnnayappa4how can we resolve this day-in day-out issues of reaching the max connection?09:18
VedaAnnayappa4can we have some cleanup solution is there is any dangling connections?09:19
VedaAnnayappa4if*09:19
VedaAnnayappa4what is the main cause of mysql reaching the max limit, is there any leak that is not caught ?09:20
anuragmahanto243#VedaAnnayappa4 restarted mysql service once after playbook run. I encounter the issue while 2nd-template creation.09:24
VedaAnnayappa4#MujahidAli #anuragmahanto243 then in that case it should not reach the max limit.. what is the current limit, is there any scope to increase it?09:25
MujahidAliI think it's a problem with MYSQL09:25
MujahidAliIt need to be updated09:26
VedaAnnayappa4#MujahidAli do u mean that it need to be updated to latest version?09:27
MujahidAliwe need to update, but before doing that we need to make sure that our current version of nodepool is not broken by updating it.09:28
anuragmahanto243#VedaAnnayappa4 our current is "mysql  Ver 14.14 Distrib 5.7.27" and latest is 8.0, we are 3 versions far.09:29
anuragmahanto243#MujahidAli any work around for , current mysql issue.09:30
VedaAnnayappa4#anuragmahanto243 then thats a quite old versions that we are using it. this might also have an impacts on other modules and components09:31
MujahidAliyes09:31
MujahidAlibut if we upgrade it then it might break the other running services.09:31
VedaAnnayappa4so looks like its quite a dead lock situation and to be handled carefully.09:33
*** dikonoor has quit IRC09:36
anuragmahanto243#MujahidAli how can I solve the current mysql issue.09:37
MujahidAliGoogle is the solution to almost every problem :)09:38
MujahidAliI think we need to manually cleanup the connections09:38
MujahidAliand then see if that helps.09:39
anuragmahanto243Sure, I will do this (y) .  Any suggestions on a permanent solution.09:41
MujahidAliPermanent solution should be: Upgrade nodepool, jenkins, zuul and mysql to the version that community is using.09:43
MujahidAliYou can try upgrading all of the above services on staging env and see if that worked then you are good to replicate the same on prod.09:44
VedaAnnayappa4fine.. lets target it stage by stage.. Anurag, try manual cleanup.. we will sync up next week for positive signs.09:46
anuragmahanto243sure09:46
VedaAnnayappa4any other topics for discussion09:46
MujahidAlinothing from me.09:46
anuragmahanto243nothing more from myside09:47
anuragmahanto243#endmeeting openstack-powervm09:49
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."09:49
openstackMeeting ended Wed Jul 31 09:49:40 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_powervm/2019/openstack_powervm.2019-07-31-09.01.html09:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_powervm/2019/openstack_powervm.2019-07-31-09.01.txt09:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_powervm/2019/openstack_powervm.2019-07-31-09.01.log.html09:49
*** VedaAnnayappa4 has quit IRC10:04
*** MujahidAli has quit IRC10:10
*** anuragmahanto243 has quit IRC10:29
*** ricolin_ has joined #openstack-powervm11:01
*** ricolin has quit IRC11:03
*** ricolin_ is now known as ricolin12:50
*** efried is now known as efried_rollin15:57
*** ricolin has quit IRC16:50
*** altlogbot_3 has quit IRC18:16
*** altlogbot_0 has joined #openstack-powervm18:20
*** efried_rollin is now known as efried19:47

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!