Wednesday, 2013-12-18

*** gdubreui has quit IRC00:02
*** markmcclain has joined #openstack-neutron00:05
*** carl_baldwin has quit IRC00:15
*** banix has quit IRC00:17
*** dave_tucker has quit IRC00:17
*** yfujioka has joined #openstack-neutron00:26
openstackgerritShiv Haris proposed a change to openstack/neutron: Testing  https://review.openstack.org/6127300:29
*** iwamoto has joined #openstack-neutron00:34
*** dave_tucker has joined #openstack-neutron00:37
*** djbkd has quit IRC00:40
*** SumitNaiksatam has joined #openstack-neutron00:41
*** networkstatic has quit IRC00:43
*** yamahata has joined #openstack-neutron00:47
*** klindgren_ has quit IRC00:49
*** gdubreui has joined #openstack-neutron00:50
*** mlavalle has quit IRC00:57
*** dave_tucker has quit IRC01:01
*** dave_tucker has joined #openstack-neutron01:09
*** dhellmann has joined #openstack-neutron01:10
*** dhellmann has left #openstack-neutron01:11
jog0anteaya: can you make sure this one gets hunted down https://bugs.launchpad.net/neutron/+bug/124425501:22
* anteaya clicks01:25
*** dave_tucker has left #openstack-neutron01:26
anteayajog0: this is the fingerprint I have for it: http://bit.ly/1i05EwL01:27
anteayawalk with me for a minute on this one01:27
*** dt has joined #openstack-neutron01:27
jog0anteaya: you can see the fingerprint here status.openstack.org/elastic-recheck/01:27
anteayahow do we have 39 failures all at the same time for this fingerprint?01:27
jog0anteaya: I know nothing about that bug01:27
jog0just that we are seeing it and its stalled01:27
*** dt has left #openstack-neutron01:28
*** ashaikh has quit IRC01:28
anteayahelp me with the logstash here for a minute01:28
anteayaso on 2013-12-1601:28
anteayathere are 39 hits with teh exact same timestamp01:28
anteayacan you confirm?01:28
*** dave_tucker has joined #openstack-neutron01:28
jog0checking01:28
anteayathe first 5 hits all have the same build_uuid e7f0fb8a68b84bad8f26b502fff7654501:29
anteayathose 39 hits01:31
anteayaonly have 3 unique build_uuids01:31
anteayaso does this mean that there are actually only 3 hits for that bug at the time?01:31
anteayathe build_uuid is a unique identifier for that job run, is it not?01:32
jog0anteaya: look and the build_change01:32
*** dave_tucker has left #openstack-neutron01:32
jog0they are all for https://review.openstack.org/#/c/59787/01:32
* anteaya clicks the build change01:32
jog0so this bug may not be in gate after all01:32
*** dave_tucker has joined #openstack-neutron01:33
*** dave_tucker is now known as dave_tucker_zzz01:33
jog0I need to head out, can you update that bug with our findings01:34
anteayajog0: same build here http://bit.ly/1cPJycf01:35
anteayawhat did we find?01:35
anteayamultiple hits for the same build_change?01:35
anteayais this a bug, or expected logstash behaviour?01:35
anteayaI don't know01:35
jog0anteaya: that this has only been seen in one patch set https://review.openstack.org/#/c/59787/01:36
anteayacan do01:36
jog0anteaya: and yeah expected behavior01:36
jog0I'll explain tomorrow01:36
anteayaso perhaps the patch is the issue?01:36
anteayaand thanks01:36
jog0in short logstash treats each line in a log file as a seperate item01:36
anteayaah01:38
anteayabuild_change is my new best friend01:38
*** dave_tucker_zzz is now known as dave_tucker01:38
anteayahappy next item on your calendar01:38
anteayatty tomorrow01:38
*** dzyu has joined #openstack-neutron01:39
jog0o/01:40
*** dave_tucker is now known as dave_tucker_zzz01:41
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Corrected PEP8 issues Made corrections to apiObj  https://review.openstack.org/6279201:44
anteayajog0 commented02:01
anteayajog0: all hits for that bug right now are from a single patch02:04
anteayaI also commented on the patch, since it might indeed be the source of a problem02:04
anteayaand the tests might indeed be failing appropriately02:04
*** banix has joined #openstack-neutron02:08
*** dave_tucker_zzz has quit IRC02:08
*** dave_tucker has joined #openstack-neutron02:14
*** dave_tucker is now known as dave_tucker_zzz02:15
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Corrected PEP8 issues  https://review.openstack.org/6279202:15
*** dave_tucker_zzz is now known as dave_tucker02:16
*** krast has joined #openstack-neutron02:23
*** dave_tucker is now known as dave_tucker_zzz02:23
*** gdubreui has quit IRC02:26
*** vkozhukalov has joined #openstack-neutron02:54
*** gdubreui has joined #openstack-neutron03:00
*** haleyb has quit IRC03:03
*** nati_uen_ has quit IRC03:04
*** alexpilotti has quit IRC03:11
*** networkstatic has joined #openstack-neutron03:16
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Added A10 LBaaS Driver to branch.  https://review.openstack.org/6246403:30
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Corrected PEP8 issues Made corrections to apiObj  https://review.openstack.org/6279203:30
marunbeagles: ping03:39
*** jp_at_hp has quit IRC03:49
*** harlowja is now known as harlowja_away03:51
*** ljjjustin has joined #openstack-neutron03:54
openstackgerritMicheal Thompson proposed a change to openstack/neutron: modified:   .gitignore modified:   neutron/services/loadbalancer/drivers/a10networks/a10_api_2_1/core/a10logger.py modified:   neutron/services/loadbalancer/drivers/a10networks/a10_api_2_1/core/apiObj.py modified:   neutron/services/loadbalancer/drive  https://review.openstack.org/6280303:56
*** terry_howe has left #openstack-neutron03:56
*** layer427expert has joined #openstack-neutron03:57
layer427expertis there anyone who can answer a question about git review?03:57
dkehnI'll try03:58
*** terry_howe has joined #openstack-neutron03:59
layer427expertSo a couple of things I am trying to setup an automated system for testing and commit03:59
layer427expertcan we go to another channel?03:59
dkehn?03:59
dkehnwhats up03:59
dkehnsure04:00
layer427expertSorry the issues is when I commit and then review I notice that my changes are going in as04:00
layer427expertnew commits when I am trying to patch.04:00
dkehnis this after you do the inital commit04:01
layer427expertyes04:01
dkehnare you using the --amend to keep the same CHAGE_ID04:01
dkehnchange_id04:01
dkehnchange-is04:01
dkehnchange-id, crap04:01
layer427expertya04:01
*** ashaikh has joined #openstack-neutron04:01
layer427expertthen he walks away04:01
layer427expertno I am missing that04:02
layer427expertthanks04:02
layer427expertI know it was something simple... thanks for the help..04:02
*** aymenfrikha has quit IRC04:03
*** suresh12 has quit IRC04:03
dkehnso after you do the inital commit and the git review, you will notice a change-id: see https://review.openstack.org/#/c/58860/, after that point you just do a git commit -a --amend which will keep the change-id, and you don't need to change anything in the commit04:03
layer427expertOIC....04:04
dkehnlayer427expert: np, I'm off to bed04:04
openstackgerritDave Cahill proposed a change to openstack/neutron: Midonet plugin: Fix source NAT  https://review.openstack.org/6280504:04
layer427expertythank gn04:04
*** inara has quit IRC04:14
*** chandankumar has joined #openstack-neutron04:15
*** julim has quit IRC04:18
*** inara has joined #openstack-neutron04:22
*** jecarey has quit IRC04:26
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Added A10 LBaaS Driver to branch.  https://review.openstack.org/6246404:28
*** yfried has joined #openstack-neutron04:34
*** layer427expert has quit IRC04:54
*** bashok has joined #openstack-neutron04:56
*** krast_ has joined #openstack-neutron05:06
*** krast has quit IRC05:07
*** csd_ has quit IRC05:16
*** jecarey has joined #openstack-neutron05:16
*** csd_ has joined #openstack-neutron05:17
*** yfried has quit IRC05:18
*** garyk has quit IRC05:19
*** rohit404 has quit IRC05:20
*** rohit404 has joined #openstack-neutron05:22
*** gdubreui has quit IRC05:28
openstackgerritDazhao Yu proposed a change to openstack/neutron: Calculate stateless IPv6 address  https://review.openstack.org/5618405:33
*** rpodolyaka1 has joined #openstack-neutron05:34
*** layer427expert has joined #openstack-neutron05:35
*** rpodolyaka1 has left #openstack-neutron05:43
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 issues hopefully. Corrected Cookie issue  https://review.openstack.org/6246405:50
*** nati_ueno has joined #openstack-neutron05:51
rohit404anyone here know what's the use case of multi-provider network extension ?05:52
*** jecarey has quit IRC05:53
marunsalv-orlando: ping05:56
openstackgerritBerezovsky Irena proposed a change to openstack/neutron: Change default eswitchd port to avoid conflict  https://review.openstack.org/6020305:56
*** csd_ has quit IRC05:57
*** csd_ has joined #openstack-neutron05:58
*** csd_ has quit IRC06:00
*** csd_ has joined #openstack-neutron06:01
*** ashaikh has quit IRC06:02
*** suresh12 has joined #openstack-neutron06:04
*** banix has quit IRC06:13
*** vkozhukalov has quit IRC06:15
*** vkozhukalov has joined #openstack-neutron06:15
*** csd_ has quit IRC06:22
*** csd_ has joined #openstack-neutron06:23
*** Jianyong has joined #openstack-neutron06:24
*** yfried has joined #openstack-neutron06:32
openstackgerritDazhao Yu proposed a change to openstack/neutron: Calculate stateless IPv6 address  https://review.openstack.org/5618406:34
*** alex_klimov has joined #openstack-neutron06:36
openstackgerritJenkins proposed a change to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6281206:37
*** csd_ has quit IRC06:37
*** csd_ has joined #openstack-neutron06:39
*** dkehn has quit IRC06:40
*** rwsu_ has quit IRC06:41
*** dkehn has joined #openstack-neutron06:42
*** csd__ has joined #openstack-neutron06:42
*** csd_ has quit IRC06:44
*** amritanshu_RnD has joined #openstack-neutron06:49
*** vkozhukalov has quit IRC06:52
*** dims has quit IRC06:55
*** layer427expert has quit IRC06:59
*** garyk has joined #openstack-neutron07:07
*** layer427expert has joined #openstack-neutron07:09
*** ljjjustin has quit IRC07:09
*** ljjjustin has joined #openstack-neutron07:11
*** wenjianhn has joined #openstack-neutron07:23
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974307:27
*** ljjjustin has quit IRC07:34
yfriedbeagles: here?07:39
*** dims_ has joined #openstack-neutron07:43
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 issues hopefully. Corrected Cookie issue  https://review.openstack.org/6246407:44
*** rohit404 has quit IRC07:48
*** rohit404 has joined #openstack-neutron07:49
*** suresh12 has quit IRC07:53
openstackgerritXiang Hui proposed a change to openstack/neutron: Raise the RuntimeError encountered when adding port  https://review.openstack.org/5895408:02
*** layer427expert has quit IRC08:02
*** jlibosva has joined #openstack-neutron08:06
*** iwamoto has quit IRC08:13
*** fouxm has joined #openstack-neutron08:14
*** fouxm has quit IRC08:19
*** fouxm has joined #openstack-neutron08:20
*** SushilKM has joined #openstack-neutron08:22
openstackgerritTomoko Inoue proposed a change to openstack/neutron: Can't create a firewall for admin tenant when at least one other tenant has a firewall.  https://review.openstack.org/6260008:22
salv-orlandomarun: still around?08:23
marunsalv-orlando: yes08:23
marunsalv-orlando: your ovs l2 patch works very well08:24
marunsalv-orlando: i'm not sure there's as much performance improvement to be had from the dhcp agent, i'm afraid.08:25
marunsalv-orlando: it's looking like the main benefit of a refactor will be increasing resiliency to failure08:25
marunsalv-orlando: in your testing of the l2 agent, how do you usually test?  with real vm's (how many) or fakevirt?08:26
salv-orlandol2 agent needs real vms08:26
salv-orlandomarun: if the tap is not created (as the fake_virt driver does), nothing happens on the l2 agent08:27
openstackgerritOleg Bondarev proposed a change to openstack/neutron: Mock looping_call in metadata agent tests  https://review.openstack.org/6282208:27
marunsalv-orlando: shame we don't have a way to fake it.08:28
marunsalv-orlando: how many vm's can you boot simultaneously?08:28
openstackgerritTomoko Inoue proposed a change to openstack/neutron: Can't create a firewall for admin tenant when at least one other tenant has a firewall.  https://review.openstack.org/6260008:30
*** vkozhukalov has joined #openstack-neutron08:31
salv-orlandomarun: my limit is the size of my testbed; the one I am using currently does not allow me to go beyond 10.08:35
salv-orlandobut I think if I have time over the weekend I can add a few compute nodes and get up to 40-5008:35
*** ygbo has joined #openstack-neutron08:35
marunsalv-orlando: I can boot 40 no problem.  Around 50 it becomes problematic - nova starts reporting connection errors in contacting neutron08:37
*** roeyc has joined #openstack-neutron08:37
marunsalv-orlando: but at least now all the vm's that are marked 'active' are actually active08:38
salv-orlandoare you enabling multiple api workers?08:39
marunsalv-orlando: yes, 408:39
marunsalv-orlando: ah, nuts.  i'm wrong :(08:40
marunsalv-orlando: i thought i'd set it in local.conf but I guess not.08:40
salv-orlandomarun: nova does network configuration asynchronously, so it bombs neutron with requests; I wondeer why the large_ops jobs with the fake driver succeeds for 150 whereas the same operation with a real driver fails for 50 vms08:41
salv-orlandonova/neutron calls are the same regardless of the virt driver. The extra load might be because of l2 agent callbacks calling into the server?08:41
marunsalv-orlando: it may be.  i was seeing elevated load on the l2 agent as the number of vm's rose08:43
salv-orlandomarun: the load gets big for processing the taps, mostly for doing iptables-{save|restore}, ovs-vsctl and ovs-ofctl. But the code in trunk currently triggers a good deal of callbacks from the agent to the server, which also increase, unnecessarily the load on the server. For instance refresh_firewall is always invoked when handling port_update and it always gets all the security group rules which apply to a given list of devices08:46
marunsalv-orlando: ah, that sounds like a good target for further optimization then08:48
salv-orlandoand if you look at trunk you'll find out the l2 agent is now pretty much notified on almost every change. This is a bug, I think, and I have a patch for it. The patch has 2 +2 already, but since it failed during verify08:48
*** amuller has joined #openstack-neutron08:48
salv-orlandoI am not running more checks to ensure it is not the patch adding more bugs08:48
salv-orlandomarun: this patch -> https://review.openstack.org/#/c/58860/08:48
openstackgerritSylvain Afchain proposed a change to openstack/neutron: Add param and iptables rules to protect dnsmasq ports  https://review.openstack.org/6199408:54
kruskaklianteaya: I think I figured out how to run my Jenkins test now, I need to export the GERRIT_REFSPEC in my execut-shell command, then do, typically: git fetch https://review.openstack.org/openstack/neutron $GERRIT_REFSPEC && git checkout FETCH_HEAD before staring my unit tests08:54
*** jlibosva has quit IRC09:10
*** ihrachyshka has quit IRC09:10
*** markmcclain has quit IRC09:10
*** salv-orlando has quit IRC09:10
*** unicell has quit IRC09:10
*** openstackgerrit has quit IRC09:11
*** enikanorov__ has quit IRC09:11
*** vkozhukalov has quit IRC09:11
*** alex_klimov has quit IRC09:11
*** Jianyong has quit IRC09:11
*** bashok has quit IRC09:11
*** briancline has quit IRC09:11
*** otherwiseguy has quit IRC09:11
*** zigo has quit IRC09:11
*** morganfainberg has quit IRC09:11
*** rohit404 has quit IRC09:11
*** wenjianhn has quit IRC09:11
*** garyk has quit IRC09:11
*** nati_ueno has quit IRC09:11
*** krast_ has quit IRC09:11
*** HenryG has quit IRC09:11
*** marios has quit IRC09:11
*** dims_ has quit IRC09:11
*** csd__ has quit IRC09:11
*** dkehn has quit IRC09:11
*** yfried has quit IRC09:11
*** dzyu has quit IRC09:11
*** yfujioka has quit IRC09:11
*** AndreyGrebenniko has quit IRC09:11
*** pashi_ has quit IRC09:11
*** jianingy_afk has quit IRC09:11
*** thansen has quit IRC09:11
*** _cerberus_ has quit IRC09:11
*** sdague has quit IRC09:11
*** ivoks has quit IRC09:11
*** metral has quit IRC09:11
*** inara has quit IRC09:11
*** Qlawy has quit IRC09:11
*** pasquier-s has quit IRC09:11
*** terry_howe has quit IRC09:11
*** doude_ has quit IRC09:11
*** jog0 has quit IRC09:11
*** MichielHN has quit IRC09:11
*** mrsnivvel has quit IRC09:11
*** obondarev has quit IRC09:11
*** harlowja_away has quit IRC09:11
*** lifeless has quit IRC09:11
*** kashyap has quit IRC09:11
*** roeyc has quit IRC09:11
*** ywu has quit IRC09:11
*** dsockwell has quit IRC09:11
*** skraynev has quit IRC09:11
*** Mierdin has quit IRC09:11
*** chandankumar has quit IRC09:11
*** dave_tucker_zzz has quit IRC09:11
*** rdo has quit IRC09:11
*** fcoj has quit IRC09:11
*** rkukura has quit IRC09:11
*** benner has quit IRC09:11
*** ekarlso has quit IRC09:11
*** amritanshu_RnD has quit IRC09:11
*** networkstatic has quit IRC09:11
*** yamahata has quit IRC09:11
*** kruskakli has quit IRC09:11
*** mattymo has quit IRC09:11
*** larsks has quit IRC09:11
*** sgran has quit IRC09:11
*** fouxm has quit IRC09:11
*** mordred has quit IRC09:11
*** pbeskow_ has quit IRC09:11
*** sc68cal has quit IRC09:11
*** pvo has quit IRC09:11
*** ajo has quit IRC09:11
*** EmilienM has quit IRC09:11
*** russellb has quit IRC09:11
*** yongli has quit IRC09:11
*** akamyshnikova_ has quit IRC09:11
*** lari__ has quit IRC09:11
*** Makdaam has quit IRC09:11
*** aryan has quit IRC09:11
*** cburgess has quit IRC09:11
*** dosaboy has quit IRC09:11
*** christophk has quit IRC09:11
*** zhhuabj has quit IRC09:11
*** angryjesters has quit IRC09:11
*** roaet has quit IRC09:11
*** gizmoguy_ has quit IRC09:11
*** Apsu has quit IRC09:11
*** decede has quit IRC09:11
*** markvoelker has quit IRC09:11
*** ogelbukh has quit IRC09:11
*** annegentle_ has quit IRC09:11
*** enikanorov has quit IRC09:11
*** jhurlbert has quit IRC09:11
*** nijaba has quit IRC09:11
*** amuller has quit IRC09:11
*** ygbo has quit IRC09:11
*** SushilKM has quit IRC09:11
*** SumitNaiksatam has quit IRC09:11
*** ijw has quit IRC09:11
*** mtreinish has quit IRC09:11
*** yamahata__ has quit IRC09:11
*** marun has quit IRC09:11
*** JoeHazzers has quit IRC09:11
*** asadoughi has quit IRC09:11
*** anteaya has quit IRC09:11
*** lowkey has quit IRC09:11
*** terry_howe has joined #openstack-neutron09:13
*** jpich has joined #openstack-neutron09:13
*** majopela has joined #openstack-neutron09:13
*** amuller has joined #openstack-neutron09:13
*** roeyc has joined #openstack-neutron09:13
*** ygbo has joined #openstack-neutron09:13
*** vkozhukalov has joined #openstack-neutron09:13
*** SushilKM has joined #openstack-neutron09:13
*** fouxm has joined #openstack-neutron09:13
*** jlibosva has joined #openstack-neutron09:13
*** rohit404 has joined #openstack-neutron09:13
*** dims_ has joined #openstack-neutron09:13
*** wenjianhn has joined #openstack-neutron09:13
*** garyk has joined #openstack-neutron09:13
*** amritanshu_RnD has joined #openstack-neutron09:13
*** csd__ has joined #openstack-neutron09:13
*** dkehn has joined #openstack-neutron09:13
*** alex_klimov has joined #openstack-neutron09:13
*** yfried has joined #openstack-neutron09:13
*** Jianyong has joined #openstack-neutron09:13
*** nati_ueno has joined #openstack-neutron09:13
*** krast_ has joined #openstack-neutron09:13
*** bashok has joined #openstack-neutron09:13
*** inara has joined #openstack-neutron09:13
*** chandankumar has joined #openstack-neutron09:13
*** dave_tucker_zzz has joined #openstack-neutron09:13
*** dzyu has joined #openstack-neutron09:13
*** yamahata has joined #openstack-neutron09:13
*** SumitNaiksatam has joined #openstack-neutron09:13
*** yfujioka has joined #openstack-neutron09:13
*** markmcclain has joined #openstack-neutron09:13
*** briancline has joined #openstack-neutron09:13
*** salv-orlando has joined #openstack-neutron09:13
*** ihrachyshka has joined #openstack-neutron09:13
*** ijw has joined #openstack-neutron09:13
*** Mierdin has joined #openstack-neutron09:13
*** HenryG has joined #openstack-neutron09:13
*** otherwiseguy has joined #openstack-neutron09:13
*** mtreinish has joined #openstack-neutron09:13
*** yamahata__ has joined #openstack-neutron09:13
*** unicell has joined #openstack-neutron09:13
*** marun has joined #openstack-neutron09:13
*** marios has joined #openstack-neutron09:13
*** zhhuabj has joined #openstack-neutron09:13
*** openstackgerrit has joined #openstack-neutron09:13
*** enikanorov__ has joined #openstack-neutron09:13
*** thansen has joined #openstack-neutron09:13
*** mordred has joined #openstack-neutron09:13
*** gizmoguy_ has joined #openstack-neutron09:13
*** jianingy_afk has joined #openstack-neutron09:13
*** metral has joined #openstack-neutron09:13
*** ivoks has joined #openstack-neutron09:13
*** pashi_ has joined #openstack-neutron09:13
*** AndreyGrebenniko has joined #openstack-neutron09:13
*** sdague has joined #openstack-neutron09:13
*** zigo has joined #openstack-neutron09:13
*** morganfainberg has joined #openstack-neutron09:13
*** _cerberus_ has joined #openstack-neutron09:13
*** rdo has joined #openstack-neutron09:13
*** Qlawy has joined #openstack-neutron09:13
*** yongli has joined #openstack-neutron09:13
*** pasquier-s has joined #openstack-neutron09:13
*** akamyshnikova_ has joined #openstack-neutron09:13
*** doude_ has joined #openstack-neutron09:13
*** Apsu has joined #openstack-neutron09:13
*** annegentle_ has joined #openstack-neutron09:13
*** skraynev has joined #openstack-neutron09:13
*** decede has joined #openstack-neutron09:13
*** markvoelker has joined #openstack-neutron09:13
*** mattymo has joined #openstack-neutron09:13
*** jog0 has joined #openstack-neutron09:13
*** MichielHN has joined #openstack-neutron09:13
*** dsockwell has joined #openstack-neutron09:13
*** mrsnivvel has joined #openstack-neutron09:13
*** ogelbukh has joined #openstack-neutron09:13
*** lowkey has joined #openstack-neutron09:13
*** obondarev has joined #openstack-neutron09:13
*** harlowja_away has joined #openstack-neutron09:13
*** enikanorov has joined #openstack-neutron09:13
*** lifeless has joined #openstack-neutron09:13
*** jhurlbert has joined #openstack-neutron09:13
*** kashyap has joined #openstack-neutron09:13
*** pbeskow_ has joined #openstack-neutron09:13
*** angryjesters has joined #openstack-neutron09:13
*** fcoj has joined #openstack-neutron09:13
*** lari__ has joined #openstack-neutron09:13
*** rkukura has joined #openstack-neutron09:13
*** dosaboy has joined #openstack-neutron09:13
*** kruskakli has joined #openstack-neutron09:13
*** benner has joined #openstack-neutron09:13
*** ekarlso has joined #openstack-neutron09:13
*** ywu has joined #openstack-neutron09:13
*** JoeHazzers has joined #openstack-neutron09:13
*** sc68cal has joined #openstack-neutron09:13
*** pvo has joined #openstack-neutron09:13
*** Makdaam has joined #openstack-neutron09:13
*** aryan has joined #openstack-neutron09:13
*** asadoughi has joined #openstack-neutron09:13
*** roaet has joined #openstack-neutron09:13
*** larsks has joined #openstack-neutron09:13
*** sgran has joined #openstack-neutron09:13
*** cburgess has joined #openstack-neutron09:13
*** nijaba has joined #openstack-neutron09:13
*** ajo has joined #openstack-neutron09:13
*** EmilienM has joined #openstack-neutron09:13
*** russellb has joined #openstack-neutron09:13
*** christophk has joined #openstack-neutron09:13
*** anteaya has joined #openstack-neutron09:13
*** Mierdin has quit IRC09:13
marunsalv-orlando: i'm still seeing pretty high cpu usage on the agent, even with the patch09:13
salv-orlandomarun: that patch is not final - look at the todos09:14
openstackgerritHyunsun Moon proposed a change to openstack/neutron: Fix port binding host is set None when port update  https://review.openstack.org/6282909:14
salv-orlandomarun: I am talking about the l2 agent patch09:14
marunsalv-orlando: ah, right.09:14
EmilienMi'm currently working on puppet-neutron, and try to understand the changes made over the last days about security group configuration. Is the firewall_driver should be configured on both plugin & agent ?09:14
EmilienMmy concern is https://review.openstack.org/#/c/62535 - where a guy tries to configure firewall_driver on ml2.ini, but I thought this flag was only for the agent (OVS or LB)09:15
salv-orlandomarun: basically what happens now is that even if update a port changing its name, it reprocesses the vif (unnecessarily) and reapplies filters (even more unnecessarily). When you boot a vm there are both port-create and port-update calls from nova (that's another thing arosen is optimising), thus the high load.09:16
*** jlibosva has quit IRC09:16
*** ihrachyshka has quit IRC09:16
*** markmcclain has quit IRC09:16
*** salv-orlando has quit IRC09:16
*** unicell has quit IRC09:16
*** openstackgerrit has quit IRC09:16
*** enikanorov__ has quit IRC09:16
*** vkozhukalov has quit IRC09:16
*** alex_klimov has quit IRC09:16
*** Jianyong has quit IRC09:16
*** bashok has quit IRC09:16
*** briancline has quit IRC09:16
*** otherwiseguy has quit IRC09:16
*** zigo has quit IRC09:16
*** morganfainberg has quit IRC09:16
*** terry_howe has quit IRC09:16
*** rohit404 has quit IRC09:16
*** wenjianhn has quit IRC09:16
*** garyk has quit IRC09:16
*** nati_ueno has quit IRC09:16
*** krast_ has quit IRC09:16
*** HenryG has quit IRC09:16
*** marios has quit IRC09:16
*** dims_ has quit IRC09:16
*** csd__ has quit IRC09:16
*** dkehn has quit IRC09:16
*** yfried has quit IRC09:16
*** dzyu has quit IRC09:16
*** yfujioka has quit IRC09:16
*** AndreyGrebenniko has quit IRC09:16
*** pashi_ has quit IRC09:16
*** jianingy_afk has quit IRC09:16
*** thansen has quit IRC09:16
*** _cerberus_ has quit IRC09:16
*** sdague has quit IRC09:16
*** ivoks has quit IRC09:16
*** metral has quit IRC09:16
*** inara has quit IRC09:16
*** Qlawy has quit IRC09:16
*** pasquier-s has quit IRC09:16
*** doude_ has quit IRC09:16
*** jog0 has quit IRC09:16
*** MichielHN has quit IRC09:16
*** mrsnivvel has quit IRC09:16
*** obondarev has quit IRC09:16
*** harlowja_away has quit IRC09:16
*** lifeless has quit IRC09:16
*** kashyap has quit IRC09:16
*** roeyc has quit IRC09:16
*** ywu has quit IRC09:16
*** majopela has quit IRC09:16
*** dsockwell has quit IRC09:16
*** skraynev has quit IRC09:16
*** chandankumar has quit IRC09:16
*** dave_tucker_zzz has quit IRC09:16
*** rdo has quit IRC09:16
*** fcoj has quit IRC09:16
*** rkukura has quit IRC09:16
*** benner has quit IRC09:16
*** ekarlso has quit IRC09:16
*** jpich has quit IRC09:16
*** amritanshu_RnD has quit IRC09:16
*** yamahata has quit IRC09:16
*** kruskakli has quit IRC09:16
*** mattymo has quit IRC09:16
*** larsks has quit IRC09:16
*** sgran has quit IRC09:16
*** fouxm has quit IRC09:16
*** mordred has quit IRC09:16
*** pbeskow_ has quit IRC09:16
*** sc68cal has quit IRC09:16
*** pvo has quit IRC09:16
*** ajo has quit IRC09:16
*** EmilienM has quit IRC09:16
*** russellb has quit IRC09:16
*** yongli has quit IRC09:16
*** akamyshnikova_ has quit IRC09:16
*** lari__ has quit IRC09:16
*** Makdaam has quit IRC09:16
*** aryan has quit IRC09:16
*** cburgess has quit IRC09:16
*** dosaboy has quit IRC09:16
*** christophk has quit IRC09:16
*** zhhuabj has quit IRC09:16
*** angryjesters has quit IRC09:16
*** roaet has quit IRC09:16
*** gizmoguy_ has quit IRC09:16
*** Apsu has quit IRC09:16
*** decede has quit IRC09:16
*** markvoelker has quit IRC09:16
*** ogelbukh has quit IRC09:16
*** annegentle_ has quit IRC09:16
*** enikanorov has quit IRC09:16
*** jhurlbert has quit IRC09:16
*** nijaba has quit IRC09:16
*** amuller has quit IRC09:16
*** ygbo has quit IRC09:16
*** SushilKM has quit IRC09:16
*** SumitNaiksatam has quit IRC09:16
*** ijw has quit IRC09:16
*** mtreinish has quit IRC09:17
*** yamahata__ has quit IRC09:17
*** marun has quit IRC09:17
*** JoeHazzers has quit IRC09:17
*** asadoughi has quit IRC09:17
*** anteaya has quit IRC09:17
*** lowkey has quit IRC09:17
*** matrohon has quit IRC09:17
*** alex_klimov has joined #openstack-neutron09:22
*** rohit404 has joined #openstack-neutron09:22
*** matrohon has joined #openstack-neutron09:22
*** terry_howe has joined #openstack-neutron09:22
*** jpich has joined #openstack-neutron09:22
*** majopela has joined #openstack-neutron09:22
*** amuller has joined #openstack-neutron09:22
*** roeyc has joined #openstack-neutron09:22
*** ygbo has joined #openstack-neutron09:22
*** vkozhukalov has joined #openstack-neutron09:22
*** SushilKM has joined #openstack-neutron09:22
*** fouxm has joined #openstack-neutron09:22
*** jlibosva has joined #openstack-neutron09:22
*** dims_ has joined #openstack-neutron09:22
*** wenjianhn has joined #openstack-neutron09:22
*** garyk has joined #openstack-neutron09:22
*** amritanshu_RnD has joined #openstack-neutron09:22
*** csd__ has joined #openstack-neutron09:22
*** dkehn has joined #openstack-neutron09:22
*** yfried has joined #openstack-neutron09:22
*** Jianyong has joined #openstack-neutron09:22
*** nati_ueno has joined #openstack-neutron09:22
*** krast_ has joined #openstack-neutron09:22
*** bashok has joined #openstack-neutron09:22
*** inara has joined #openstack-neutron09:22
*** chandankumar has joined #openstack-neutron09:22
*** dave_tucker_zzz has joined #openstack-neutron09:22
*** dzyu has joined #openstack-neutron09:22
*** yamahata has joined #openstack-neutron09:22
*** SumitNaiksatam has joined #openstack-neutron09:22
*** yfujioka has joined #openstack-neutron09:22
*** markmcclain has joined #openstack-neutron09:22
*** briancline has joined #openstack-neutron09:22
*** salv-orlando has joined #openstack-neutron09:22
*** ihrachyshka has joined #openstack-neutron09:22
*** ijw has joined #openstack-neutron09:22
*** HenryG has joined #openstack-neutron09:22
*** otherwiseguy has joined #openstack-neutron09:22
*** mtreinish has joined #openstack-neutron09:22
*** yamahata__ has joined #openstack-neutron09:22
*** unicell has joined #openstack-neutron09:22
*** marun has joined #openstack-neutron09:22
*** marios has joined #openstack-neutron09:22
*** zhhuabj has joined #openstack-neutron09:22
*** openstackgerrit has joined #openstack-neutron09:22
*** enikanorov__ has joined #openstack-neutron09:22
*** thansen has joined #openstack-neutron09:22
*** mordred has joined #openstack-neutron09:22
*** gizmoguy_ has joined #openstack-neutron09:22
*** jianingy_afk has joined #openstack-neutron09:22
*** metral has joined #openstack-neutron09:22
*** ivoks has joined #openstack-neutron09:22
*** pashi_ has joined #openstack-neutron09:22
*** AndreyGrebenniko has joined #openstack-neutron09:22
*** sdague has joined #openstack-neutron09:22
*** zigo has joined #openstack-neutron09:22
*** morganfainberg has joined #openstack-neutron09:22
*** _cerberus_ has joined #openstack-neutron09:22
*** rdo has joined #openstack-neutron09:22
*** Qlawy has joined #openstack-neutron09:22
*** yongli has joined #openstack-neutron09:22
*** pasquier-s has joined #openstack-neutron09:22
*** akamyshnikova_ has joined #openstack-neutron09:22
*** doude_ has joined #openstack-neutron09:22
*** Apsu has joined #openstack-neutron09:22
*** annegentle_ has joined #openstack-neutron09:22
*** skraynev has joined #openstack-neutron09:22
*** decede has joined #openstack-neutron09:22
*** markvoelker has joined #openstack-neutron09:22
*** mattymo has joined #openstack-neutron09:22
*** jog0 has joined #openstack-neutron09:22
*** MichielHN has joined #openstack-neutron09:22
*** dsockwell has joined #openstack-neutron09:22
*** mrsnivvel has joined #openstack-neutron09:22
*** ogelbukh has joined #openstack-neutron09:22
*** lowkey has joined #openstack-neutron09:22
*** obondarev has joined #openstack-neutron09:22
*** harlowja_away has joined #openstack-neutron09:22
*** enikanorov has joined #openstack-neutron09:22
*** lifeless has joined #openstack-neutron09:22
*** jhurlbert has joined #openstack-neutron09:22
*** kashyap has joined #openstack-neutron09:22
*** pbeskow_ has joined #openstack-neutron09:22
*** angryjesters has joined #openstack-neutron09:22
*** fcoj has joined #openstack-neutron09:22
*** lari__ has joined #openstack-neutron09:22
*** rkukura has joined #openstack-neutron09:22
*** dosaboy has joined #openstack-neutron09:22
*** kruskakli has joined #openstack-neutron09:22
*** benner has joined #openstack-neutron09:22
*** ekarlso has joined #openstack-neutron09:22
*** ywu has joined #openstack-neutron09:22
*** JoeHazzers has joined #openstack-neutron09:22
*** sc68cal has joined #openstack-neutron09:22
*** pvo has joined #openstack-neutron09:22
*** Makdaam has joined #openstack-neutron09:22
*** aryan has joined #openstack-neutron09:22
*** asadoughi has joined #openstack-neutron09:22
*** roaet has joined #openstack-neutron09:22
*** larsks has joined #openstack-neutron09:22
*** sgran has joined #openstack-neutron09:22
*** cburgess has joined #openstack-neutron09:22
*** nijaba has joined #openstack-neutron09:22
*** ajo has joined #openstack-neutron09:22
*** EmilienM has joined #openstack-neutron09:22
*** russellb has joined #openstack-neutron09:22
*** christophk has joined #openstack-neutron09:22
*** anteaya has joined #openstack-neutron09:22
salv-orlandomarun: ovs does not know anything about IP info, as the IP is actually in the guests. I was thinking of adding some intelligence to port_updated notifications09:22
marunsalv-orlando: ah, right.09:22
EmilienMmatrohon: the guy was not able to run SG using ML2 without the trick09:22
marunsalv-orlando: yes, I vote for better notifications.09:22
salv-orlandonow it dumps all the details, and that's not a great idea. since it is the same problem that caused the l3 agent to go crazy during havana09:22
marunsalv-orlando: fyi, with your patches I can now boot 40 vm's at a time without error.  50 errors out like crazy, though.09:22
salv-orlandoWhy don't you post your errors somewhere?09:22
salv-orlandomarun: to cut a long story short, I was thinking of augmenting the notification with a few flags that tell what kind of change we are looking at. Something like (port_id, admin_state_change, mac_ip_config_change)09:23
marunsalv-orlando: that would only seem to make sense.  if we have the info the agent will need, why not send it directly?09:24
openstackgerritmouad benchchaoui proposed a change to openstack/neutron: Make the metadata namespace proxy transparent  https://review.openstack.org/2813709:24
marunsalv-orlando: ack, my errors are again my stupidity.  quotas too low and duplicate ports being created per vm09:25
salv-orlandosending the actual info, like the new ips, is actually dangerous; this caused us troubles with the l3 agent; nati-ueno spotted indeed an issue were there where two changes to the same floating IP in the API (say X and Y, with X -> Y) and then the l3 agent applied Y -> X09:25
marunsalv-orlando: i remember seeing on the bug about why duplicate ports were being created.  that's a nova issue?09:25
marunsalv-orlando: so ordering of amqp messages isn't reliable by default?09:26
salv-orlandoin the queue, yes09:26
salv-orlandoonce you pick it from the queue and process it with event let not09:26
salv-orlandois there anything reliable about eventlet?09:27
marunsalv-orlando: it is if we use it correctly09:27
marunsalv-orlando: i think it's just as annoying as real threads in that regard09:27
marunsalv-orlando: instead of managing access to shared data, we have to manage execution paths much more carefully09:27
marunsalv-orlando: but for example, the preliminary work I've done for the dhcp agent is to simply collect notifications and stuff them into a local queue09:28
*** zoresvit has joined #openstack-neutron09:28
marunsalv-orlando: probably a better option is just dispensing with the lame oslo rpc dispatch mechanism entirely, but i wanted something minimally invasive for now09:28
marunsalv-orlando: once things are in a local queue, we can process the queue with only a single greenthread and be guaranteed ordering consistency09:29
openstackgerritSimon Pasquier proposed a change to openstack/neutron: neutron-rootwrap-xen-dom0 handles data from stdin  https://review.openstack.org/6234609:29
marunsalv-orlando: and, when a resync is required, coordination becomes easy as opposed to using explicit file-based locks09:30
salv-orlandoit's fine to choose something minimally invasive; pushing events in LIFO queue should guarantee ordering consistency as long as we can be reasonably sure they are pushed in the same order as they're picked from the queue.09:31
salv-orlandomarun: therefore the rpc callback should probably have a critical section inside?09:31
salv-orlandosorry not the rpc callback, the function called by the rpc message09:31
marunsalv-orlando: the rpc callback just pushes to a queue.  there should be no blocking io that would relinquish control to another greenthread09:32
marunsalv-orlando: and then all the notifications are simply called serially09:32
salv-orlandomarun: I got that, but if you have multiple concurrent notifications, the rpc callback also pushes concurrently in the que09:32
* salv-orlando queue09:33
marunsalv-orlando: uh, there's no such thing as concurrency in eventlet09:33
marunsalv-orlando: and control only ever switches if a greenthread gives up control09:33
salv-orlandomarun: or if some routine you've called has been monkey patched by eventlet and yields09:34
salv-orlandobut if you just add to a queue, I think it's sage09:34
salv-orlandosafe09:34
marunsalv-orlando: I agree, I don't mean to argue.  You're right that one has to take care to avoid relinquishing control during something important.09:34
marunsalv-orlando: I'd be happy to see eventlet put in the bin, frankly.  It seriously violates the 'explicit is better than implicit' mantra of python.09:35
salv-orlandomarun: I'm never in a mood for an argument :) I'm just saying that eventlet to same extent encourages bad concurrent programming patters09:35
salv-orlandopatterns09:35
marunsalv-orlando: I couldn't agree more.09:35
marunsalv-orlando: at least with real threading or process-based concurrency one knows that one is handling something dangerous, and work carefully to avoid problems.09:36
salv-orlandoso ideally I would code as if you're using pthreads anyway, and don't bother that eventlet is not really concurrent09:36
marunsalv-orlando: eventlet encourages 'not my problem'09:36
openstackgerritSushil Kumar proposed a change to openstack/python-neutronclient: Updates .gitignore  https://review.openstack.org/6218009:37
marunsalv-orlando: well, it's been important for me to know that only a single thread executes at a time.09:37
marunsalv-orlando: combined with the knowledge of how control is given up, eventlet is no longer a black box for me.09:37
marunsalv-orlando: The lack of good synchronization primitives for eventlet has lead to pervasive use of utils.synchronize, which in my book indicates a failure to think the problem through in most cases.09:38
*** roeyc has quit IRC09:39
marunsalv-orlando: in real threading, using a synchronization primitive would make sense, but in eventlet I have yet to see a compelling reason.09:39
salv-orlandothere might be a reason only when you need to process larger routines which should not be interrupted and make a call which could yield09:40
salv-orlandothink about the l2 agent, which might yield in treat_vif_port. I think the following sequence of event is possible:09:41
salv-orlandoA) the main rpc_loop finds a port, gets device details from server, and finds out the port if administratively down, then reaches treat_vif_port09:42
salv-orlandoB) the main rpc_loop yields to port_update notification for bringing that same port up, and yields to some other thread (maybe the state report thing), before doing treat_vif_port09:43
marunsalv-orlando: again, bad design09:43
salv-orlandoC) control goes back to the port_update thread which treats the port on the agent assigning the local vlan and bringing it up09:43
salv-orlandomarun: gotcha, I got your point.09:43
salv-orlandobasically you're saying if you do the design correctly you probably won't need to deal with explicit synchronization09:44
marunsalv-orlando: That was my conjecture, but I'm wrong.09:44
marunsalv-orlando: :)09:45
marunsalv-orlando: I do think it would be better for notifications to be locally queued and processed by a single event loop.09:45
salv-orlandomeh: we could talk about this for ages, but perhaps it's better we just look at problems and find the most efficient and reliable way to process them.09:45
marunsalv-orlando: actually, i think i still am right.09:45
marunsalv-orlando: no, wrong.09:46
marunsalv-orlando: as you say, its complicated09:46
salv-orlandomarun: I agree with you; I was just musing on the opportunities for using shared resource locking primitives with eventlet as well09:46
salv-orlandoa single loop is the most efficient way, agreed. period.09:46
openstackgerritZhang Hua proposed a change to openstack/neutron: Clean up ML2 Manager  https://review.openstack.org/6135109:46
marunsalv-orlando: Having a single event loop in one greenthread and another greenthread queueing notifications makes sense to me.  I guess the key point to understand is that things break down if the eventloop ever spawns new greenthreads that it doesn't wait for.09:48
marunsalv-orlando: ala the dhcp agent fix that went in to wait for the pool of threads doing the syncing.  without that wait, things just don't work.09:48
*** jroovers has joined #openstack-neutron09:48
marunsalv-orlando: so fyi, the breakage I was seeing with 50 vm's was more PEBKAC09:49
marunsalv-orlando: port quota was set at 50, and duplicate ports were being created as per that bug09:49
marunsalv-orlando: increasing the quota and trying again09:49
salv-orlandomarun: so you are still seeing the duplicate ports. I never understood whether that was more a neutron or a nova bug. But if that's still happening, the bug should be reopened.09:50
openstackgerritArmando Migliaccio proposed a change to openstack/neutron: Add migration support from agent to NSX dhcp/metadata services  https://review.openstack.org/5132509:50
marunsalv-orlando: I think it's a nova/neutron integration problem, as per the comment on the bug https://bugs.launchpad.net/neutron/+bug/116044209:51
openstackgerritYves-Gwenael Bourhis proposed a change to openstack/neutron: Make dnsmasq aware of all names  https://review.openstack.org/5293009:51
marunsalv-orlando: Ian Well's comment about it being nova rescheduling makes the most sense09:52
marunsalv-orlando: it is re-opened, and jlibosva is assigned to work on it09:52
salv-orlandomarun: just seen that09:52
marunsalv-orlando: so what to set the status to - triaged?09:53
marunsalv-orlando: or confirmed?09:53
salv-orlandoif you know the root cause, is triaged imho09:55
marunok09:55
*** Jianyong has left #openstack-neutron10:04
*** dzyu has quit IRC10:06
*** krast_ has quit IRC10:10
marunjlibosva: ping10:12
*** dhellmann has joined #openstack-neutron10:15
*** jp_at_hp has joined #openstack-neutron10:19
*** salv-orlando has quit IRC10:23
*** dave_tucker_zzz is now known as dave_tucker10:28
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Process port_update notifications in the main agent loop  https://review.openstack.org/6196410:30
*** nati_ueno has quit IRC10:34
*** dave_tucker is now known as dave_tucker_zzz10:35
*** jp_at_hp has quit IRC10:37
*** yamahata has quit IRC10:42
*** yamahata__ has quit IRC10:42
*** yamahata__ has joined #openstack-neutron10:42
*** yamahata__ has quit IRC10:43
*** yamahata__ has joined #openstack-neutron10:43
*** dave_tucker_zzz is now known as dave_tucker10:43
openstackgerritJianing Yang proposed a change to openstack/neutron: Implement basic functionalities for port forwarding  https://review.openstack.org/6051210:44
*** safchain has joined #openstack-neutron10:44
*** yfujioka has quit IRC10:45
*** dave_tucker is now known as dave_tucker_zzz10:47
*** jecarey has joined #openstack-neutron10:52
*** nati_ueno has joined #openstack-neutron11:13
*** jp_at_hp has joined #openstack-neutron11:19
*** jp_at_hp has quit IRC11:19
*** jp_at_hp has joined #openstack-neutron11:19
*** dave_tucker_zzz is now known as dave_tucker11:20
*** dave_tucker is now known as dave_tucker_zzz11:30
yfriedbeagles: I have some questions about floating_ip_tracker11:31
*** dave_tucker_zzz is now known as dave_tucker11:32
*** pcm has joined #openstack-neutron11:33
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974311:35
*** pcm has quit IRC11:35
*** pcm has joined #openstack-neutron11:36
*** dave_tucker is now known as dave_tucker_zzz11:39
*** dave_tucker_zzz is now known as dave_tucker11:46
*** marun has quit IRC11:48
openstackgerritJianing Yang proposed a change to openstack/neutron: Implement basic functionalities for port forwarding  https://review.openstack.org/6051211:48
*** bashok has quit IRC11:49
*** rohit404 has quit IRC11:54
*** dave_tucker is now known as dave_tucker_zzz11:55
*** afazekas_ has joined #openstack-neutron12:01
*** aymenfrikha has joined #openstack-neutron12:06
*** yfried has quit IRC12:07
*** yfried has joined #openstack-neutron12:08
*** salv-orlando has joined #openstack-neutron12:16
*** rohit404 has joined #openstack-neutron12:18
*** jamespage has joined #openstack-neutron12:21
openstackgerritSylvain Afchain proposed a change to openstack/neutron: L3 Agent can handle many external networks  https://review.openstack.org/5935912:23
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974312:30
*** yfried has quit IRC12:32
*** Abhishek has joined #openstack-neutron12:34
*** yfried has joined #openstack-neutron12:45
ijwmarun: I see i was being talked about12:46
ijwmarun: salv-orlando: that was arosen's idea about what was going on, I think, tell him to bloody well move the port-create call12:47
ijwIf we only used port-update in nova-compute, and only ever passed ports (not networks) to nove-compute, the code would be less racy and simultaneously simpler.12:47
ijwThe only question is whether or how you could unwind the port-create if the scheduling fails12:48
salv-orlandoarosen is working on that indeed. technically if the port has not been yet wired, undoing is easy12:48
ijwYeah, it's more that it's nova that knows the unwinding is required (or you do it in the background) but I rememebr working through the logic for that, maybe on the mailing list12:49
salv-orlandoor you don't even need to undo. The port is merely an entry on the db, and as long as scheduling is not done, the host binding part isn't populated12:49
ijwThat much is true, but it's automatically created and will persist forever if you don't clean it up12:49
salv-orlandoijw: you're correct this happens currently because nova creates the ports for neutron after scheduling12:49
salv-orlandoarose wants to move the logical bits of providing the network resource to before the scheduling12:50
ijwMind, maybe we were going to get shot of it in nova delete.  There was logic to this but it's been a while12:50
salv-orlandos/arose/arosen12:50
ijwDefinitely the right answer.  Is he going to have time for it?12:50
ijwIt's been on his to-do list for a while.12:50
ijwAlso, on a more important topic, you around for a Christmas pint next week?12:51
*** yfried has quit IRC12:55
*** aymenfrikha has quit IRC13:00
*** aymenfrikha has joined #openstack-neutron13:01
*** jroovers has quit IRC13:09
*** aymenfrikha has quit IRC13:13
jlibosvaanteaya: Hi, is there a way how can I connect to machine that is running the grenade gate test? to see whether the problem is the same I have locally?13:21
openstackgerritDarragh O'Reilly proposed a change to openstack/neutron: linuxbridge-agent: process port update notifications in the main loop  https://review.openstack.org/6287513:26
*** clev has joined #openstack-neutron13:29
*** dhellmann has left #openstack-neutron13:31
*** yfried has joined #openstack-neutron13:32
*** alagalah has joined #openstack-neutron13:34
beaglesyfried: fire away13:38
*** banix has joined #openstack-neutron13:38
*** banix has quit IRC13:40
*** jlibosva has quit IRC13:43
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974313:47
beaglesyfried: actually brb.. gotta do a quick errand13:48
*** beagles is now known as beagles_brb13:48
*** jpich has quit IRC13:52
yfriedbeagles_brb: In the FLIP_tracker - you're waiting for the FLIP to show up on the VMs DB (~ nova show <VM>) which takes a lot of time. isn't it enough to check the neutron DB?13:52
*** jpich has joined #openstack-neutron13:53
openstackgerritA change was merged to openstack/neutron: fix --excluded of meter-label-rule-create is not working  https://review.openstack.org/6134413:53
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974313:55
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Process port_update notifications in the main agent loop  https://review.openstack.org/6196413:55
*** amotoki has joined #openstack-neutron13:55
*** mattymo has quit IRC13:55
*** mattymo has joined #openstack-neutron13:55
*** julim has joined #openstack-neutron13:58
*** aymenfrikha has joined #openstack-neutron14:00
*** jroovers has joined #openstack-neutron14:04
*** jorisroovers has joined #openstack-neutron14:06
*** ashaikh has joined #openstack-neutron14:08
*** jroovers has quit IRC14:09
jorisrooversCould someone have a look at https://review.openstack.org/#/c/62867/ for me? Thanks14:09
*** jlibosva has joined #openstack-neutron14:10
*** nati_ueno has quit IRC14:10
*** ijw has quit IRC14:12
*** roeyc has joined #openstack-neutron14:13
*** ijw has joined #openstack-neutron14:13
*** peristeri has joined #openstack-neutron14:13
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172114:19
*** yfujioka has joined #openstack-neutron14:21
*** jorisroovers has quit IRC14:25
*** jlibosva has quit IRC14:27
*** richardboswell2 has joined #openstack-neutron14:28
*** wenjianhn has quit IRC14:29
*** otherwiseguy has quit IRC14:37
*** ashaikh has quit IRC14:38
anteayakruskakli: awesome, thanks for the feedback14:38
anteayakruskakli: there is a meeting for people working on third party tests, the meeting it on Thursday at 2200 utc in #openstack-meeting-alt, it would be wonderful if you could attend and share at the meeting what you just shared with me14:39
*** jlibosva has joined #openstack-neutron14:41
*** tongli has joined #openstack-neutron14:43
openstackgerritOleg Bondarev proposed a change to openstack/neutron: LBaaS: agent monitoring and instance rescheduling  https://review.openstack.org/5974314:44
*** dims_ has quit IRC14:44
openstackgerritDarragh O'Reilly proposed a change to openstack/neutron: linuxbridge-agent: process port updates in the main loop  https://review.openstack.org/6287514:47
*** insanidade has joined #openstack-neutron14:47
insanidadehi all. where do I find the recorded webinars from yesterday's PTL meeting?14:48
anteayajlibosva: I can ask fungi to access a running vm, you will have to tell him what commands you want him to run on it, I am asssuming you want the vm to be running your patch when you access it?14:48
*** dims_ has joined #openstack-neutron14:48
anteayajlibosva: please join #openstack-infra if you haven't already and I will see about getting that coordinated14:49
jlibosvaanteaya: ok, thanks.14:49
*** SushilKM has quit IRC14:49
anteayainsanidade: http://eavesdrop.openstack.org/meetings/project/2013/14:49
jlibosvaanteaya: I want to see the tags of ports in ovs. When I deploy devstack stable/havana on my ubuntu, I see instances have tags 2 while dhcp and router is 114:50
anteayainsanidade: there are no webinars, all openstack meetings take place on irc, in #openstack-meeting and #openstack-meeting-alt so they can be logged14:50
anteayawe are an opensource project and we use opensource tools14:51
anteayajlibosva: let's see what is on fungi's agenda already14:51
*** aveiga has joined #openstack-neutron14:53
*** djbkd has joined #openstack-neutron14:54
*** pcm is now known as Guest9999714:55
*** pcm_ has joined #openstack-neutron14:57
insanidadeanteaya: I mean those: http://www.openstack.org/blog/ (see first post)14:58
insanidadeare they webinars ?14:58
anteayaah summit talks14:59
anteayathe PTL meets every Tuesday, yesterday and the meetings are logged on irc14:59
insanidadeyeah. I'd like to see yesterday's discussion but can't find where its recording was made available15:00
*** yfujioka has quit IRC15:01
*** amuller has quit IRC15:02
yfriedbeagles_brb: are you back?15:03
*** beagles_brb is now known as beagles15:04
beaglesyikes15:04
beaglesyeah15:04
beaglessorry15:04
beagleswent down a rat hole15:04
yfriedbeagles: how do I post links to lines in the master branch?15:04
*** akamyshnikova has joined #openstack-neutron15:04
*** terry_howe has left #openstack-neutron15:05
beaglesgood question...15:05
beaglesyou could just tell me the lines you are referring to :)15:05
*** terry_howe has joined #openstack-neutron15:05
yfriedbeagles: http://git.openstack.org/cgit/openstack/tempest/tree/tempest/scenario/test_network_basic_ops.py#n5615:06
dkehnbeagles: did you ever get devstack to run straight from trunk, without migration issues? Just asking before I go there15:06
yfriedbeagles: so you are fetching the server data from nova to check if floating ip has reached it15:06
beaglesdkehn: I did a couple of fresh ones in the last few days and it was cool15:06
yfriedbeagles: right?15:06
beaglesyfried: yup15:06
dkehnbeagles: great thx15:07
yfriedbeagles: why?15:07
beaglesyfried: why checking if it reaches it or why ask each time?15:07
*** alex_klimov has quit IRC15:07
beaglesyfried: if the latter.. well, you have to for the former to make sense :)15:07
yfriedbeagles: In my experience you should be able to reach the VM well before the FLIP has updated nova's DB15:08
yfriedbeagles: why not look at neutron's DB - ie port list15:08
beaglesyfried: the former, it is meant as a control point15:08
yfriedbeagles: I'm asking because it seems to crush often in case of stress in the gate15:09
beaglesyfried: because the  logic I was using was meant to be independent of neutron... ie it would be applicable to nova-networking as well as neutron15:10
beaglesyfried: two things about that15:10
yfriedso I'm guessing it reaches timeout before VM is update15:10
mesteryQuestion for people: I'm having trouble running unit tests on the latest Neutron. I am on Fedora 20, but what I see fail is something like this: http://paste.openstack.org/raw/55321/15:10
mesteryAnyone seen anything like that recently?15:10
mesteryI'm running them with: tox -v -epy27 neutron.tests.unit.ml2.test_mechanism_ncs (as an example)15:11
anteayainsanidade: margie callard wrote the blog post: http://www.openstack.org/foundation/staff15:11
beaglesyfried: pinging would timeout as well on the gate... and it would be interpreted as a failure in neutron, whereas it could simply be load15:11
anteayainsanidade: you can email her and ask, personally I have no idea15:11
beaglesyfried: if nova has the floating ip, an ping fails then it is definitely the network implementation that has screwed up15:11
yfriedbeagles: https://review.openstack.org/#/c/55101/ https://review.openstack.org/#/c/62697/15:11
yfriedcheck out these 2 patches15:12
yfriedthe first is my test, creating 2 VMs with FLIP15:12
yfriedthe second adds your check to the test15:12
yfriedthe second fails half of the time15:13
yfriedthe first runs without issues15:13
beaglesyfried: interesting.. because it was the reverse for me15:14
beaglesyfried: in my own environment that is15:14
anteayavote for J: http://lists.openstack.org/pipermail/openstack/2013-December/004029.html15:14
beaglesyfried: there is another facet to this...15:14
insanidadeanteaya: thanks :)15:15
beaglesyfried: is it a bug if the floating IP does not appear in the nova list in a timely fashion... that being said, the check could be moved until after the connectivity tests and still be valid15:15
yfriedbeagles: do you know if the gate VMs (the VMs that run the devstack gate) are created by openstack as well? if so - you have an issue of very slow FLIP propagation, and even slower DB update15:15
anteayamestery: did unit tests work for you previously on the same environment using the same command syntax?15:16
mesteryanteaya: Apologies, I have just now realized they pass without some local changes. Rookie mistake. :(15:16
* mestery crawls back into his hole.15:16
anteayait happens15:16
yfriedbeagles: why do you need the check if the connection is validated?15:16
mestery:)15:16
anteayadon't do that, stay with us15:16
beaglesyfried:  what?15:16
* mestery could have sworn he checked that last night.15:16
anteayamorning eyes15:17
anteayahappens to everybody15:17
beaglesyfried: I don't understand the question I think15:17
anteayainsanidade: let us know what you find out15:17
yfriedbeagles: the last one?15:17
beaglesyfried: oh, if the floating IP appears in the list?15:18
yfriedbeagles: let me restart -15:18
yfriedbeagles: you said that we can move the tracker check to after the connectivity check. am I right?15:19
beaglesyfried: you could if you felt it was invalid to put it before pinging.. which would be contrary to its original purpose, which was to add a control point to add sanity to the connectivity checks.15:19
*** ashaikh has joined #openstack-neutron15:19
beaglesyfried: bear with me and I'll elaborate on my thinking...15:20
beaglesyfried: so basically what we are trying to do is perform functional.. and in some cases very rudimentary system tests (which the scenarios seem to be)...15:21
beaglesyfried: automating these things means we have to take the highly asynchronous nature of the system into account...15:22
beaglesyfried: for example, even though an initiating call might be synchronous, the resultant changes on the system may be initiated in an asynchronous fashion...15:22
beaglesyfried: which means what feedback you do get may be misleading... the ACTIVE state on a VM for example...15:23
beaglesyfried: so for system tests to be directed at testing functionality there has to be a "settling phase" to the test in which you verify certain control points...15:23
beaglesyfried: testing functionality before settling occurs results in red-herring chases because errors will point to functions failing...15:24
beaglesyfried: that is not to say time limits are verbotten, it is just that the time limits are on the control points in the settling phase...15:24
pbeskow_\15:24
beaglesyfried: so if the settling doesn't occur, the system is still bugged, but it isn't in the functionality, it is in the settling of the asynchronous setup operations...15:25
beaglesyfried: in this particular case, ping was used as a control point and I changed it to a round trip outcome...15:25
beaglesyfried: if pinging failed after the round trip then neutron is for certain to blame (with the current implementation)...15:26
beaglesyfried: if the control point of waiting  for the floating IP fails, the issue is a performance issue with propagating the floating ip...15:26
beaglesyfried: admittedly what would be best is for there to be some other way to have such a control point... like some kind of feedback that system changes have been applied15:27
beaglesyfried that would be perfect15:27
*** amritanshu_RnD has quit IRC15:27
yfriedbeagles: I followed until the last post15:28
beaglesyfried, I think in a meeting yesterday one of the QA guys warned of using the word non-determinism to apply to timing errors that are in fact race conditions....15:28
beaglesyfried: which is valid in a sense, but the race condition is where? the implementation or the test or both...15:29
*** otherwiseguy has joined #openstack-neutron15:29
beaglesyfried: pragmatically from a testing view it makes no difference, from our perspective it is all of the difference in the world in where we focus energy15:29
beaglesyfried: ok.... last post15:29
beaglesyfried: so basically what I was referring to is that in almost every case where we rely on feedback from openstack to know when to continue a test there is an inherent uncertainty because the information is premature...15:30
beaglesyfried: eg. the active status on a VM... sure the virt driver says it is active, but the vm might be fscking or something... it isn't really ready for anything, including connecting to it...15:31
beaglesyfried: if there were someway to *know* that the VM was ready before trying the next step in that case, everything would be gravy...15:31
beaglesyfried: the same goes for changes that are made by neutron15:31
beaglesyfried: I haven't come up with a good way to do that.. but I think about it all the time15:33
*** roeyc has quit IRC15:33
beaglesyfried: there is something interesting, did you say your test always passes without the check?15:35
yfriedbeagles: yes15:35
yfriedyou see the patch log15:36
beaglesyfried: network_basic_ops as well?15:36
*** fouxm has quit IRC15:36
yfriedI never had issues with network_basic_ops before your change or after15:36
beaglesyfried: interesting... it was failing a lot for me when I wrote that15:37
yfriedbeagles: locally or on the gate?15:37
beaglesyfried: locally15:37
yfriedwhere you using more that a single VM\FLIP?15:38
beaglesyfried: nope15:38
*** csd__ has quit IRC15:39
*** carl_baldwin has joined #openstack-neutron15:40
*** vkozhukalov has quit IRC15:40
yfriedbeagles: do you know if anyone else had the same issue as you?15:41
yfriedbeagles: anyway - since network tests are done with neutron, I think waiting for nova DB isn't the answer. it might work on your system or for a single VM test, but on a more complicated test it fails15:41
beaglesyfried: network_basic_ops  timing out?15:41
yfriedbeagles: yeah15:41
*** clev has quit IRC15:42
beaglesyfried: re the test.. I was under the impression that this was  failing for people.. certainly ping timeouts were known to occur15:43
beaglesyfried: regarding the whether to wait or not... I'm fine either way as long as everybody else is, but I say this...15:44
beaglesyfried: the fact that floating IP doesn't show up is a bug15:44
beaglesyfried: if we want a separate test, then cool... but we should test for it15:44
*** jdev789 has joined #openstack-neutron15:45
*** mlavalle has joined #openstack-neutron15:45
*** fouxm has joined #openstack-neutron15:45
mlavalleenikanorov: ping15:45
yfriedbeagles: maybe we should put a bigger timeout?15:46
yfried*longer15:46
beaglesyfried: not a big fan of longer timeouts... we need a better check for failure...15:46
ijwIf this is the timing out test, then arguably if it's missing a timeout that large it *is* a failure15:46
yfriedbeagles: any Ideas?15:47
*** dkehn has quit IRC15:48
beaglesyfried: its tough.. the best checks are system introspective and not implemenation agnostic.. eg. checking the firewall rules or whether the VM is even accessible via its private IP15:49
beaglesyfried: and at some point you start muddying the waters between what is acceptable from tempest tests15:49
yfriedbeagles: we can't do the 2nd due to netns. what about the first?15:49
beaglesyfried: same thing.. the rules are in a ns15:50
*** dkehn has joined #openstack-neutron15:50
beagles1s15:50
mlavalleyfried: thanks for the patch sets…. I will take a look on them around my lunch time (i'm in UTC -6)15:53
yfriedmlavalle: the 2nd fails even thought the first works. if you are able to see why I would love to konw15:55
yfriedknow15:55
mlavalleyfried: ok, I'll try find out….15:55
yfriedbeagles: I need to leave. maybe we should move this conv to the mailing list?15:56
mlavalleyfried: how are you located in relationship to UTC? + 2? + 3?15:56
beaglesyfried: sure... quick question if I can15:56
beaglesyfried: is this failing most of the time in your environment or at the gate?15:56
yfriedmlavalle: UTC+215:57
mlavalleso, enjoy dinner :-)15:57
* beagles proceeds to kill firefox15:58
yfriedmlavalle: I have a long bus ride before and kid to put to bed, but tnx15:58
beaglesyfried: the reason I ask is that I'm only seeing one such failure on the gate.. but I'm still looking in case I missed it15:58
*** banix has joined #openstack-neutron15:59
yfriedbeagles: haven't seen this locally. I'm guessing it's a stress issue, or maybe devstack just takes longer to assign FLIP and the 2nd VM sometimes hits the threshold.16:00
yfriedbeagles: could you add the timeout value to the log so we can see if the tests that do pass are anywhere near the threshold?16:01
yfriedbeagles: because we are looking at it as a pass/fail, but if everything is hitting close to the timeout this is a bug and we need to know16:02
yfriedbeagles: what I'm asking is - since your patch tracks the time it takes for the FLIP to hit the DB, can we log it to the debug logs and see this for all the neutron gate tests for a day?16:03
yfriedyfried: I'd do it myself if I knew how16:03
beaglesyfried: I'm thinking that that information is already there.. just checking on it16:04
beaglesyfried: my firefox is not happy with me16:04
*** jdev789 has quit IRC16:04
yfriedbeagles: I really need to go now. too bad I can't continue this on my phone but kit-kat killed my IRC app. can you please post this issue and your findings to the mailing list so we can carry this offline and also have more eyes on it?16:05
*** ihrachyshka has quit IRC16:05
beaglesyfried: no it's cool.. and will do! cheers16:05
yfriedbeagles: tnx.16:06
*** Abhishek has quit IRC16:07
*** jlibosva has quit IRC16:08
yfriedbeagles: check this out: http://logs.openstack.org/01/55101/34/check/check-tempest-dsvm-neutron/7bb7612/console.html16:08
yfriedbeagles: nm. false alarm. bye now16:09
*** ihrachyshka has joined #openstack-neutron16:09
beaglesyfried: :) cheers ... fwiw the calls are more frequent than I anticipated... every second16:09
beaglesthat's kinda silly.. when you are wating on steady state, the wait intervals have to be reasonable enough to allow steadying.. hammering is only going to make things worse16:10
*** SushilKM__ has joined #openstack-neutron16:10
yfriedmlavalle: sdague: I just lost your reviews due to rebase and bug. can you please re post them https://review.openstack.org/#/c/55101/16:10
beaglesI guess it must be modified from the default in the upstream env16:11
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172116:12
* beagles thinks on that a minute16:13
*** yamahata has joined #openstack-neutron16:13
*** yfried has quit IRC16:15
*** clev has joined #openstack-neutron16:18
*** Abhishek has joined #openstack-neutron16:20
*** markmcclain has quit IRC16:25
openstackgerritSean M. Collins proposed a change to openstack/neutron: Create a new attribute for subnets, to store v6 dhcp options  https://review.openstack.org/5298316:26
*** SushilKM__ has quit IRC16:27
*** roeyc has joined #openstack-neutron16:28
openstackgerritAvishay Balderman proposed a change to openstack/neutron: LBaaS L7 model (WIP)  https://review.openstack.org/6172116:33
*** SushilKM__ has joined #openstack-neutron16:35
*** fouxm has quit IRC16:39
*** fouxm has joined #openstack-neutron16:40
*** fouxm has quit IRC16:44
openstackgerritSvetlana Dobogoeva proposed a change to openstack/neutron: Added unit tests for module neutron/plugins/nicira/api_client/client.py  https://review.openstack.org/5994816:50
openstackgerritSvetlana Dobogoeva proposed a change to openstack/neutron: Added unit tests for module neutron/plugins/nicira/api_client/client.py  https://review.openstack.org/5994816:56
*** kashyap has left #openstack-neutron16:58
*** fouxm has joined #openstack-neutron17:01
*** eezhova has joined #openstack-neutron17:03
openstackgerritA change was merged to openstack/neutron: ml2: gre, vxlan type driver can leak segment_id  https://review.openstack.org/6169417:04
openstackgerritA change was merged to openstack/neutron: Change default eswitchd port to avoid conflict  https://review.openstack.org/6020317:06
*** dosaboy has quit IRC17:07
openstackgerritA change was merged to openstack/neutron: Imported Translations from Transifex  https://review.openstack.org/6281217:07
openstackgerritA change was merged to openstack/neutron: Midonet plugin: Fix source NAT  https://review.openstack.org/6280517:07
*** dosaboy has joined #openstack-neutron17:08
*** rwsu has joined #openstack-neutron17:08
*** ygbo has quit IRC17:08
*** dosaboy has quit IRC17:11
*** dosaboy has joined #openstack-neutron17:11
*** suresh12 has joined #openstack-neutron17:13
*** fouxm has quit IRC17:15
*** fouxm has joined #openstack-neutron17:15
*** fouxm has quit IRC17:15
anteayaeezhova: hello17:19
eezhovahi17:20
anteayamlavalle: ping17:20
enikanorovmlavalle: pong17:20
*** SushilKM__ has quit IRC17:20
anteayais ann online as well?17:20
akamyshnikovaanteaya, hi, I'm here too17:20
*** SushilKM has joined #openstack-neutron17:20
anteayaakamyshnikova: great17:20
anteayaglad to meet you both17:20
mlavalleenikanorov; I want to follow up on your offer of 2 developers17:20
anteayamlavalle: here they are17:20
anteayaeezhova: and akamyshnikova17:21
eezhovaso am I17:21
anteayaso I wanted to ensure that you meet mlavalle17:21
anteayaso that he can review your patches17:21
anteayaand he can talk to you about any blockages you are facing in your work17:21
anteayacan you share the urls of your current neutron tempest patches, please?17:22
eezhovahttps://review.openstack.org/#/c/58697/17:22
eezhovahttps://review.openstack.org/#/c/59729/17:22
eezhovahttps://review.openstack.org/#/c/62662/17:22
akamyshnikovahttps://review.openstack.org/6111817:23
akamyshnikovahttps://review.openstack.org/6262017:23
eezhovamine are scenario tests for load balancer17:23
mlavalleeezhova and akamyshinikova: very nice meeting you. I'll take a look on those reviews and keep track of them17:24
mlavalledo you have any questions at this point in time?17:24
akamyshnikovaI haven't resolve all comments to my patches. I continue working on them tomorrow17:24
mlavalleif you add me (minsel) to the reviewers, they will show up in my gerrit page17:25
mlavalleI can do that myself, though…. don't worry about ir17:27
eezhovawell, the only thing that concerns me now is that there is a bug in neutron that was discovered while I was writing the test for health monitor. There is a proposed fix but since it hasn't been reviewed this bug blocks my changes.17:27
enikanoroveezhova: does it block the basic scenario?17:28
eezhovano, just the the succeeding patches17:28
enikanorovok. i think the first one is ready17:30
mlavalleeezhova, akamyshnikova: I added myself to your patch sets…. I'll track them and you can always ping me here…. Right now I have to run to a meeting. Very glad to meet you17:31
eezhovaokay, thank you17:31
akamyshnikovamlavalle, thank you!17:31
mlavalleenikanorov: thanks for the follow up17:31
anteayaeezhova: what patch is the proposed bug fix you need?17:32
eezhovahttps://review.openstack.org/#/c/61673/17:33
anteayaif you have patches you need merged for your work, be sure to post those patches in the channel to mlavalle's attention and mine so we can follow them up so you can do your work17:33
* anteaya clicks17:33
enikanorovbugfixes for the advance features are not getting much attention recently17:34
*** vkozhukalov has joined #openstack-neutron17:34
anteayaenikanorov: it is hard for all the reviewers to review17:35
anteayaif the patch is blocking gate bugs or tempest tests, I will do my best to get reviewers on them17:35
enikanorovyeah, i know since i'm one of them17:35
anteayagate and tempest are my priorities17:35
anteayayes17:36
anteayaobondarev: are you available?17:36
anteayaobondarev: can you update 61673 with a comment providing some clarity on the outcome of your discussion with enikanorov about your patch17:36
anteayait will help reviewers to review17:37
enikanorovobondarev has adressed the issues that i pointed out on review in a separate patch17:37
enikanorovso i'm ok with this review17:38
*** krast has joined #openstack-neutron17:38
*** jp_at_hp has quit IRC17:41
*** garyk has quit IRC17:42
anteayaenikanorov: can you take a moment and state as such in a comment on review 61673?17:43
enikanorovok17:44
anteayaas a reviewer, it just seems like the discussion was never resolved, so it is hard for me to say "yes I am comfortable with this patch"17:44
anteayathanks17:44
*** chandankumar has quit IRC17:45
enikanorovthe thing is that we working closely with obondarev so we discuss things in person often17:46
*** suresh12 has quit IRC17:56
*** amotoki has quit IRC17:56
*** jpich has quit IRC17:56
*** clev has quit IRC17:56
*** mlavalle has quit IRC17:56
*** pcm_ has quit IRC17:56
*** rohit404 has quit IRC17:56
*** yamahata__ has quit IRC17:56
*** unicell has quit IRC17:56
*** openstackgerrit has quit IRC17:56
*** enikanorov__ has quit IRC17:56
*** Abhishek has quit IRC17:56
*** aveiga has quit IRC17:56
*** mattymo has quit IRC17:56
*** briancline has quit IRC17:56
*** zigo has quit IRC17:56
*** morganfainberg has quit IRC17:56
*** vkozhukalov has quit IRC17:56
*** peristeri has quit IRC17:56
*** jecarey has quit IRC17:56
*** terry_howe has quit IRC17:56
*** HenryG has quit IRC17:56
*** marios has quit IRC17:56
*** afazekas_ has quit IRC17:56
*** safchain has quit IRC17:56
*** jamespage has quit IRC17:56
*** AndreyGrebenniko has quit IRC17:56
*** pashi_ has quit IRC17:56
*** jianingy_afk has quit IRC17:56
*** dosaboy has quit IRC17:56
*** eezhova has quit IRC17:56
*** yamahata has quit IRC17:56
*** ihrachyshka has quit IRC17:56
*** thansen has quit IRC17:56
*** _cerberus_ has quit IRC17:56
*** sdague has quit IRC17:56
*** ivoks has quit IRC17:56
*** metral has quit IRC17:56
*** inara has quit IRC17:57
*** Qlawy has quit IRC17:57
*** pasquier-s has quit IRC17:57
*** doude_ has quit IRC17:57
*** jog0 has quit IRC17:57
*** MichielHN has quit IRC17:57
*** mrsnivvel has quit IRC17:57
*** obondarev has quit IRC17:57
*** harlowja_away has quit IRC17:57
*** lifeless has quit IRC17:57
*** ywu has quit IRC17:57
*** carl_baldwin has quit IRC17:57
*** tongli has quit IRC17:57
*** ijw has quit IRC17:57
*** salv-orlando has quit IRC17:57
*** majopela has quit IRC17:57
*** dsockwell has quit IRC17:57
*** skraynev has quit IRC17:57
*** dkehn has quit IRC17:57
*** otherwiseguy has quit IRC17:57
*** dims_ has quit IRC17:57
*** julim has quit IRC17:57
*** matrohon has quit IRC17:57
*** dave_tucker_zzz has quit IRC17:57
*** rdo has quit IRC17:57
*** fcoj has quit IRC17:57
*** rkukura has quit IRC17:57
*** benner has quit IRC17:57
*** ekarlso has quit IRC17:57
*** krast has quit IRC17:57
*** rwsu has quit IRC17:57
*** banix has quit IRC17:57
*** kruskakli has quit IRC17:57
*** larsks has quit IRC17:57
*** sgran has quit IRC17:57
*** ashaikh has quit IRC17:57
*** richardboswell2 has quit IRC17:57
*** mordred has quit IRC17:57
*** pbeskow_ has quit IRC17:57
*** sc68cal has quit IRC17:57
*** pvo has quit IRC17:57
*** ajo has quit IRC17:57
*** EmilienM has quit IRC17:57
*** russellb has quit IRC17:57
*** yongli has quit IRC17:57
*** akamyshnikova_ has quit IRC17:57
*** lari__ has quit IRC17:57
*** Makdaam has quit IRC17:57
*** aryan has quit IRC17:57
*** cburgess has quit IRC17:57
*** christophk has quit IRC17:57
*** zhhuabj has quit IRC17:57
*** angryjesters has quit IRC17:57
*** roaet has quit IRC17:57
*** gizmoguy_ has quit IRC17:57
*** Apsu has quit IRC17:57
*** decede has quit IRC17:57
*** markvoelker has quit IRC17:57
*** ogelbukh has quit IRC17:57
*** annegentle_ has quit IRC17:57
*** enikanorov has quit IRC17:57
*** jhurlbert has quit IRC17:57
*** nijaba has quit IRC17:57
*** SushilKM has quit IRC17:57
*** roeyc has quit IRC17:57
*** akamyshnikova has quit IRC17:57
*** aymenfrikha has quit IRC17:57
*** zoresvit has quit IRC17:57
*** SumitNaiksatam has quit IRC17:57
*** djbkd has quit IRC17:57
*** alagalah has quit IRC17:57
*** mtreinish has quit IRC17:57
*** insanidade has quit IRC17:57
*** JoeHazzers has quit IRC17:57
*** asadoughi has quit IRC17:57
*** anteaya has quit IRC17:57
*** lowkey has quit IRC17:57
*** openstack has joined #openstack-neutron18:02
-hobana.freenode.net- [freenode-info] why register and identify? your IRC nick is how people know you. http://freenode.net/faq.shtml#nicksetup18:02
*** openstack has joined #openstack-neutron18:06
*** akamyshnikova has quit IRC18:09
*** harlowja_away is now known as harlowja18:09
*** mestery has joined #openstack-neutron18:12
*** beagles has joined #openstack-neutron18:12
*** changbl has joined #openstack-neutron18:12
*** roeyc has quit IRC18:13
*** yfried has joined #openstack-neutron18:13
*** SushilKM has quit IRC18:13
*** Abhishek has quit IRC18:15
*** Abhishek has joined #openstack-neutron18:17
*** nati_ueno has joined #openstack-neutron18:22
*** eezhova has left #openstack-neutron18:22
*** majopela has quit IRC18:23
*** majopela has joined #openstack-neutron18:24
*** suresh12 has joined #openstack-neutron18:25
*** majopela has quit IRC18:26
*** Mierdin has joined #openstack-neutron18:27
*** jpich has quit IRC18:38
*** djbkd has left #openstack-neutron18:44
*** markmcclain has joined #openstack-neutron18:45
*** salv-orlando_ has joined #openstack-neutron18:49
*** salv-orlando has quit IRC18:50
*** salv-orlando_ is now known as salv-orlando18:50
*** mlavalle has joined #openstack-neutron18:50
*** SushilKM has joined #openstack-neutron18:50
*** afazekas_ has quit IRC18:59
terry_howemarkmcclain or salv-orlando_ do you guys know if the DHCP agent to network is one-to-one, one-to-many or many-to-many19:01
markmcclainterry_howe: each agent manages the dnsmasq instances for multiple networks19:03
terry_howethanks19:04
*** Abhishek has quit IRC19:07
anteayaenikanorov: this bug is now #2 in the gate and rising: https://bugs.launchpad.net/nova/+bug/125489019:08
*** yfried has quit IRC19:09
anteayaenikanorov: have you had a chance to look at it at all?19:09
*** richardboswell2 has quit IRC19:09
anteayadims_: you also are on this bug, any thoughts you might be able to share with enikanorov?19:09
enikanorovanteaya: i've looked into other one yet. will switch19:09
anteayaenikanorov: which other one?19:10
*** yfried has joined #openstack-neutron19:10
*** yfried has quit IRC19:10
*** SumitNaiksatam has joined #openstack-neutron19:12
enikanorovhttps://bugs.launchpad.net/neutron/+bug/121048319:12
enikanorovI've managed to repro this one like once in 50 test runs. haven't managed to identify the root cause of the race19:12
anteaya:(19:13
*** rohit404 has quit IRC19:13
anteayacan you update the report for 1210483 before you switch19:13
anteayathey are both in the gate19:13
*** networkstatic has quit IRC19:13
anteayalet me dig into 1210483 some more on logstash and see if I can get you something helpful19:14
anteayaand thank you19:14
*** yfried has joined #openstack-neutron19:14
anteaya*they are both on the elastic-recheck page indicating they are affecting the gate19:16
enikanorovfor 1210483 logs doesn't produce anything specific except tempest failure itself, that's the problem. looks like it's some imternal timing issue between several calls from nova to neutron19:26
yfriedbeagles: did you happen to send a mail about our discussion? I can't see it19:36
anteayaenikanorov: okay, I am going through logstash now to see if I can find something more helpful19:38
enikanorovanteaya: ok19:39
anteayaenikanorov: do you think there needs to be an increase in logging somewhere to get more accurate information?19:39
enikanorovanteaya: I'm thinking about it... once i find something which will help to identify the issue I'll may be push a patch or something. currently I'm just going to continue with code analysis19:41
*** ajo is now known as zz_ajo19:42
anteayaenikanorov: okay, yes if you need better logging to get to the bottom of 1210483, please submit a patch19:43
anteayajog0: are you available?19:44
anteayaI have come across something odd in logstash and I am hoping you are able to help me understand it19:44
*** insanida1e has joined #openstack-neutron19:45
*** insanidade has quit IRC19:48
dims_anteaya, i did not find out much, need to look again19:49
anteayadims_: great thanks enikanorov is also working on it, #2 bug in the gate and rising19:50
anteayaif you are able to work together, that would be awesome19:50
*** zz_ajo is now known as ajo19:55
*** SumitNaiksatam has quit IRC19:57
*** dave_tucker_zzz is now known as dave_tucker19:57
*** otherwiseguy has quit IRC20:00
salv-orlandoRandom question for all the people that every day run the l3 agent. If I ask you something like "what the highest frequency of router updated messages your l3 agent can handle safely, where safely mean they are all processed within a minute?" would there be somebody with an answer?20:01
salv-orlandoor at least "how long on average does it take to process a router"?20:01
*** ashaikh has quit IRC20:07
openstackgerritAmir Sadoughi proposed a change to openstack/python-neutronclient: Added --source-port-range-min, --source-port-range-max  https://review.openstack.org/6213020:12
beaglesyfried: not yet20:13
yfriedbeagles: ok20:13
beaglesyfried: fwiw though you can see how long it took for the checks to pass in the tempest.log20:14
beaglesyfried: what I also noticed that the check is cycling every second... that's too fast IMO20:14
beaglesyfried: because it results in a query to nova which is just causing a load on something that is already loaded20:15
beaglesyfried: well... probably calls neutron too20:15
beaglesyfried: so .. that needs to be backed off, because that is just making the situation worse20:15
*** SumitNaiksatam has joined #openstack-neutron20:19
*** dave_tucker is now known as dave_tucker_zzz20:20
*** ashaikh has joined #openstack-neutron20:20
*** dave_tucker_zzz is now known as dave_tucker20:22
openstackgerritA change was merged to openstack/neutron: ml2/type_gre: Adds missing clear_db to test_type_gre.py  https://review.openstack.org/6253020:27
*** vkozhukalov has quit IRC20:28
*** gizmoguy_ is now known as gizmoguy20:31
*** networkstatic has joined #openstack-neutron20:43
*** dave_tucker is now known as dave_tucker_zzz20:53
salv-orlandofellow neutron core dev: a +A might be welcome here - https://review.openstack.org/#/c/58860/20:55
salv-orlandothis patch was already approved, but I blocked it since it failed the gate for bug 1253896. After verifying the logs and several rechecks I think it's safe to send it again through the gare20:56
*** ajo is now known as zz_ajo20:56
*** marun has joined #openstack-neutron20:56
*** aveiga has quit IRC21:17
*** geekinutah has joined #openstack-neutron21:17
*** clev has quit IRC21:21
*** mlavalle has quit IRC21:22
*** mlavalle has joined #openstack-neutron21:29
*** otherwiseguy has joined #openstack-neutron21:32
anteayaotherwiseguy: hey there21:33
openstackgerritCyril Roelandt proposed a change to openstack/python-neutronclient: Sync with oslo  https://review.openstack.org/6299121:34
jog0anteaya: pong21:34
otherwiseguyanteaya: hello21:35
anteayajog0: hello there21:36
anteayaotherwiseguy: haven't see you in a bit, glad to have you around21:36
jog0you had a logstash question21:36
anteayayes21:37
anteayahttp://bit.ly/19di5CB21:37
anteayalet's start here21:37
anteayado you see the build hitting the top failure21:37
otherwiseguyanteaya: glad to be around. :) hopefully getting caught up on my RH havana release responsibilities this week.21:37
anteayajog0: confirm https://review.openstack.org/#/c/6253021:37
anteayaotherwiseguy: great, it will be great to have you back on upstream21:38
anteayawe need you21:38
otherwiseguyupstream work is certainly a lot more fun. ;)21:38
jog0anteaya: yeah I see that21:38
anteayado you see in the patch21:38
anteayaelastic-recheck suggests  recheck bug 125489021:39
anteayafor that failure21:39
anteayaand the logs have timeout waiting for thing: http://logs.openstack.org/30/62530/2/gate/gate-tempest-dsvm-neutron-pg/8a0bbff/console.html#_2013-12-18_17_36_51_09421:40
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 issues hopefully. Corrected Cookie issue Patch 7 Fixed hopfully the last pep8 issue. Pep8 validation passing in local environment but not Remote  https://review.openstack.org/6246421:40
anteayawhich is 125489021:40
jog0anteaya: athat is a different test21:40
jog0err build UUID21:40
jog0so what you are seeing is build uuid afed48ac95da4bfb80524e52cedd0319 ran but for some reason didn't become the one used by zuul21:41
jog0because it was a gate failure21:41
anteayaoh21:41
jog0if something in front of that patch fails in the gate, then all subsequent results are thrown out, but logstash recordds them anyway21:41
jog0anteaya: that confused me for a while too21:42
anteayaso logstash records them but I can't access the logs to follow it up21:42
anteayahrumph21:42
jog0you can, just see log_url21:42
jog0http://logs.openstack.org/30/62530/2/gate/gate-tempest-dsvm-neutron-pg-isolated/afed48a/console.html21:42
anteayaokay, do I have access to anything in addition to the console.html output?21:43
jog0yes, delete the console.html from the URL21:44
anteayathanks21:45
anteayathat was all I needed21:46
anteayaknowing what logstash is doing really helps21:46
jog0glad to help21:46
anteayajog0: this bug is rising: https://bugs.launchpad.net/tempest/+bug/125868221:47
anteayanot a neutron bug but noone is assigned21:47
anteayathought you might want to know21:47
anteayaand can we finish off our discussion from last night?21:48
openstackgerritSalvatore Orlando proposed a change to openstack/neutron: Commit for testing router processing times on gate  https://review.openstack.org/6299421:49
jog0anteaya: sure21:50
anteayajog0: we had been discussing https://bugs.launchpad.net/neutron/+bug/124425521:50
jog0FYI for 1258682 the issue right now is we don't collect logs21:50
anteayacan you look at my notes at the bottom and perhaps we can go from there21:50
*** roeyc has joined #openstack-neutron21:50
jog0so working on getting that done first21:51
jog0then we can identify what is causing tempest to timeout21:51
anteayajog0: ah okay, add me to the patch once it is up, who is working on it?21:51
jog0anteaya: Changing priority to low. The particular symptoms are cured for now, but the issue remains.21:51
openstackgerritCyril Roelandt proposed a change to openstack/python-neutronclient: Use six.moves.cStringIO rather than cStringIO  https://review.openstack.org/6299521:51
jog0ignore the last comment21:52
* anteaya ignores21:52
jog0for 125868221:53
jog0https://review.openstack.org/#/c/62784/21:53
jog0and https://review.openstack.org/#/c/62786/21:53
openstackgerritA change was merged to openstack/neutron: Add support for NSX/NVP Metadata services  https://review.openstack.org/4941521:53
jog0ok on to 124425521:54
anteayaneither mention bug 125868221:54
jog0anteaya: yeah :(21:54
jog0they are related to that bug but not exclusively21:55
jog0will update my patch to link it21:55
*** suresh12 has quit IRC21:56
jog0ok 124425521:57
*** hichihara has joined #openstack-neutron21:58
jog0I agree with your comment, this isn't a gate issue and priority can chance accordingly21:58
jog0although IIRC the patch that caused all those issues was a tempest patch21:58
anteayahmmm21:59
anteayado you remember which tempest patch?21:59
mlavalleanteaya: hi, we are supposed to talk at 22:00 UTC22:00
jog0oh  was wrong https://review.openstack.org/#/c/59787/22:00
beagleso/22:00
anteayawe are22:00
anteayaso here we are22:01
jog0its the api workers22:01
*** tongli has quit IRC22:01
anteayajog0: yes22:01
jog0so that feature not working is bad22:01
anteayayes22:01
*** suresh12 has joined #openstack-neutron22:01
anteayaand it hits that failure a lot22:01
jog0as it means right now setting api_workersfrom 0 to 4 goes boom22:01
anteayait does22:01
*** dave_tucker_zzz is now known as dave_tucker22:01
anteayamlavalle beagles so what is new?22:01
anteayawho wants to go first?22:02
beaglesI think rossella_s is still ill, but I started going through each test in the "full" suite yesterday22:02
anteayaawesome, thank you22:02
anteayawhat did you find?22:02
beaglesthe faulty cleanup breaks many things which means pinpointing "blame neutron" tests laborsome22:03
anteayawhere is the cleanup faulty22:03
anteayain the neutron tempest tests?22:03
beaglesin some cases, no22:03
beaglesI will have a complete report sometime tomorrow22:03
anteayafrom your gut for now22:04
anteayawhat do you think?22:04
anteayaif it changes tomorrow that is fine22:04
beaglesk 1 s22:04
beaglesso far I've run 1402 tests in isolation22:05
mlavalleanteaya: followed up with enikanorov about 2 developers, met them, got reviews from them. Reviewed several patches for yfried. We are working together in debugging one of them. unstuck a review for joris Roovers. Later tonight I will continue ading to the api gap analysis. That's all22:05
anteayamlavalle: okay thanks, good work22:06
anteayakeep doing that22:06
anteayabeagles: awesome22:06
beaglesand 106 have failed22:06
anteayaany pattern to the 106 that failed?22:06
mlavalleok, got run…. se you around22:06
anteayaand yay for the 1296 that passed22:07
beaglesin some cases, they are not neutron at all but errors with "image" related tests22:07
anteayamlavalle: k22:07
beaglesit breaks several22:07
anteaya"image" related tests22:07
anteayaglance?22:07
beagles1s.. I'll get you an example22:07
beaglestempest.api.compute.images.test_image_metadata.ImagesMetadataTestJSON.test_update_image_metadata.result.txt22:07
beaglesat the moment I'm weeding them out and continuing22:08
beaglesbut keeping track, all of the same22:08
beaglesI'll need to share with the parties who might be interested22:08
*** jroovers has joined #openstack-neutron22:09
beaglesmany of the neutron only tests appear to pass just fine, but I don't have a concrete number22:09
anteayaokay thanks for your early findings22:09
anteayaI'll see if I can get a glance person in channel to listen in22:09
*** aymenfrikha has quit IRC22:09
beaglesI am working on a run-in-isolation-of-each-process that will detect broken cleanups of different types and continue with the next test22:10
beagleswith the hope of getting a better picture of what is really not running22:10
*** peristeri has quit IRC22:10
beaglesand what tests are broken with cleanups22:10
*** markwash has joined #openstack-neutron22:11
anteayathanks markwash22:11
anteayabeagles was just updating me on this progress going over the tempest tests for neutron individually22:12
anteayahe hasn't finished his assessment yet22:12
markwashyeah, I'm interested to see what could be going on, if there's any way we can help22:12
anteayathank you22:12
anteayabeagles: did you want to repeat some of your thoughts for markwash's benefit?22:12
beaglessure and greetings to markwash22:13
markwashgreetings!22:13
beaglesso, basically in an effort to isolate individual failures of tests for neutron, I've taken a listing of tests from the "full" run and have begun working with breaking them into groups and isolating failures22:14
beaglesin some cases failures of the tests themselves or of setup or teardown leaves detritus around that interferes with further testing22:14
beaglesin the case of some of the tests I was running, cleanups were failing to delete VMs left behind resulting in quotas being exceeded and interfering with subsequent tests22:15
jroovershi enikanorov22:15
enikanorovhi22:15
beaglesI'm not sure if these belong to glance or not, but I guess since the term "image" shows up in some ..22:15
jrooversenikanorov, question related to https://review.openstack.org/#/c/62867/22:16
markwashbeagles: are some images getting left behind with that detritus?22:16
enikanorovjroovers: go ahead22:16
beaglesactually.. you know these tests are pretty clearly compute not glance22:16
jrooversenikanorov: I'm quite new to openstack/neutron/tempest dev22:16
beaglestempest.api.compute.images.test_image_metadata.ImagesMetadataTestXML.test_get_image_metadata_item.result.txt22:16
beaglesmaybe?22:16
jrooversenikanorov: so looking for a bit of guidance, what would your recommendation be. Wait or rebase?22:17
markwashbeagles: It probably is still talking to glance in some way22:17
markwashbeagles: so suspicion isn't completely lifted22:17
enikanorovjroovers: doesn't matter actually. It's up to you22:17
beaglesmarkwash: okay an example would be a NotFound: Object not found22:18
beaglesDetails: {"itemNotFound": {"message": "Image not found.", "code": 404}}22:18
beaglesexception in tempest.api.compute.images.test_image_metadata.ImagesMetadataTestJSON22:18
jrooversenikanorov: so, if I'm understanding your comments correctly, they only relate to the network_client part right?22:18
jrooversenikanorov: the tests itself are good?22:18
enikanorovjroovers: i was mainly concerned about adding stuff that i tried to remove from the clients22:18
markwashbeagles: in one case before we saw some issues where an image was being deleted before it's PUT had finished22:18
markwashand tempest was angry somehow, or something was complaining about errors being in the logs22:19
enikanorovjroovers: the tests look good, however I don't know if this set is enough or not22:19
jrooversenikanorov: its based on the doc22:19
beaglesmarkwash: ah cool22:19
jrooversenikanorov: https://etherpad.openstack.org/p/icehouse-summit-qa-neutron22:19
enikanorovjroovers: also I don't know if they should be placed in a separate file (is it a common practice?)22:19
enikanorovjroovers: got it22:20
jrooversenikanorov: yes, separate file is a tempest guideline22:20
enikanorovseparate file for negative, right?22:20
jrooversenikanorov: yes22:20
enikanorovok then22:20
enikanorovtests look good22:20
jrooversenikanorov: so would it be good to just remove the client part then?22:20
jrooversthat would essentially mean that the tests would only work for xml now22:21
jrooversenikanorov: sorry, err, only for json22:21
enikanorovif you could rebase on some of my patches, you should be able to run the tests for both xml and json22:21
jrooversok, I'll try that22:21
markwashbeagles: if there are some failures you want me to take a look at I'd probably have some time over the next day or so to dig into logs22:21
beaglesmarkwash: as there are lot of failures and eventually each subsequent test simply fails because quotas eventually get blown, maybe it would be best for me to simply publish the entire results tomorrow when I get the neutron stuff straightened22:21
jrooversenikanorov: don't have any experience with that, but I'll figure it out22:22
beaglesmarkwash: +122:22
enikanorovyeah, i think it's quite simple. initialy clients had lots of similar code that i just tried to automate. that however slightly changes client's usage.22:22
anteayabeagles markwash it looks like we are in a good place to go forward22:22
enikanorovok, it's 2:20 am here so i'm going to sleep a bit22:23
jrooversenikanorov: thanks for the help, I'll get back to you if I have additional questions22:23
jrooversenikanorov: good night!22:23
enikanorovjroovers: sure.22:23
anteayamarkwash: thanks for jumping in, you are welcome to idle, would be great to have you available for pinging if things come up22:23
beagles anteaya agreed22:23
*** hichihara has quit IRC22:23
markwashokay I'll lurk for a bit22:23
anteayaawesome, great work beagles22:23
anteayamarkwash: thank you22:23
anteayaand if there is anything we/I can do to help glance be sure to ask22:24
beaglesin addition, the use case stuff proceeds, but I want to give this breakdown a nudge priority wise ..22:24
beaglesso we can parcel out work22:24
anteayait would be good to know what does work22:24
beagles:) indeed it would22:24
anteayaand if there is a pattern to the failures22:24
anteayaso great direction22:24
jrooversanteaya or mlavalle , can I ask you a question about https://review.openstack.org/#/c/62867/22:24
anteayajroovers: ask away22:25
beaglesbtw mlavalle ( I guess arosen isnt' around)22:25
anteayaI haven't seen arosen lately22:25
beaglesI think he's travelling22:25
jrooversanteaya: ok, thanks :-) So I was wondering why there is a test failing22:25
beaglesbut anteaya this is for you to :)22:25
anteayathough he does tend to be kind of quiet22:25
beaglesor too22:25
jrooversanteaya: first it was check-tempest-dsvm-full22:26
beaglesI was doings some testing of searching by ip from nova22:26
beaglesso you do something like nova list --ip 10.0.0\..* or whatever22:26
jrooversanteaya: sorry, first it was check-grenade-dsvm and now it is  check-tempest-dsvm-full22:26
jrooversanteaya: I have the feeling like this is something outside of my control22:26
anteayajroovers: hve you looked at the logs for the failures?22:26
beaglesit doesn't seem to work22:27
anteayastart with the console.html log first22:27
mlavallejroovers: the first time you submitted your patch set, the check-grenade-dsvm failed to build devstack…. it had nothing to do with your test…. that's why I reched it22:27
beaglesso I've got to do a bit more analysis including checking if it is already fixed since havana dropped22:27
anteayabeagles: can you paste what output you do get from that command?22:27
beaglesbut in the meantime heads up22:27
beaglesanteaya: that's kind of the thing.. there is no output22:28
jrooversmlavalle: how did you initiate that recheck?22:28
beaglesI need to check with trunk...22:28
* anteaya looks quizzical22:28
anteayahmmm22:28
mlavallejroovers: if it failed again after that recheck, we have to look at the logs of the job where it failed.22:28
anteayaalright thanks for the heads up22:28
beaglesnova list --ip 10.0.0\.* .. you get no results22:28
anteayahmmmm22:28
anteayaI have no input22:28
anteayaother than to say I would expect something22:29
beagles:)22:29
anteayamlavalle: let's take a moment and ensure that jroovers develops good habits for addressing this test feedback from jenkins22:29
anteayajroovers: so did you look at the logs of both failed tests?22:29
beaglesyeah.. at any rate it is a parity bug if it still exists, I just need to do some sleuthing to verify22:29
jrooversanteaya: I did look at the first one, and am doing that again right now22:30
anteayabeagles: happy sleuthing22:30
anteayajroovers: link to the error please once you find it22:30
beaglesanteaya mlavalle: and that is all I have at the moment22:30
mlavallejroovers: I am busy right now, but I will take a look again later tonight. In general, you don't recheck a patchset unless you went thorugh the logs of the failing job (which I did with your patchset) and you know that the patchset is not the cause22:30
anteayabeagles: great report, thanks22:30
mlavallejroovers: but your initial assumption should be that the gate is pointing to a bug in your patchset22:32
mlavallethat is why we have a gate22:32
jrooversmlavalle: ok, thanks. Just as a clarification, what button do you click to recheck, or do you just add a comment and does jenkins automatically rechecks22:32
mlavalleyes, you just do a review with a recheck comment22:32
jrooversmlavalle, definitely agreed on checking your own code first.22:32
jrooversmlavalle: ok, good to know, thanks22:33
openstackgerritCyril Roelandt proposed a change to openstack/python-neutronclient: Remove an unused imported module  https://review.openstack.org/6300322:34
jrooversanteaya, so related to the first issue (http://logs.openstack.org/67/62867/1/check/check-grenade-dsvm/b0941ce/console.html)22:34
jrooversanteaya: the problem is that keystone did not upgrade correctly22:35
salv-orlandobeagles: not sure I understood everything by scrolling back but neutron does not support wildcard matching on ip addresses.22:35
jrooversanteaya: "./grenade.sh:253 Failure in upgrade-keystone"22:35
anteayajroovers: great work22:35
anteayaand you can click on the timestamp beside that error for it to be added to the url22:35
beaglessalv-orlando: on port-list?22:35
anteayathus22:36
anteayahttp://logs.openstack.org/67/62867/1/check/check-grenade-dsvm/b0941ce/console.html#_2013-12-18_13_16_25_61422:36
salv-orlandoI think grenade is non-voting for neutron at the moment, people are still working on getting the job right22:36
salv-orlandoyeas neutron commands.22:36
beaglessalv-orlando: or rather through the ports.json?22:36
jrooversanteaya: yes22:36
beaglessalv-orlando: through the cli it definitely doesn't22:36
jrooversanteaya: sorry, btw, didn't know you could link to lines22:36
salv-orlandobeagles: neutron api (either neutron port-list or GET /v2.0/ports.jsom22:36
beaglessalv-orlando: interesting22:36
jrooversanteaya: so is the thought process that because I did not make any changes to keystone, it must be a issue with devstack or grenade?22:36
salv-orlandothere was a patch a while ago but I do not remember why we did not approve it22:36
salv-orlandoit did regex matching22:37
beaglessalv-orlando: that would at least explain why it wouldn't work22:37
anteayajroovers: many people don't know that, which is why I wanted to take you through it and show you a few things22:37
anteayajroovers: that is certainly a possbility22:38
anteayait was an upgrade command was it not?22:38
jrooversanteaya: yes22:38
anteayaso the error could be in one of our repos or mirrors failing to have the package available when devstack was looking for it22:38
anteayathat is possible as well22:39
beaglessalv-orlando: so.. mmm that's a parity issue then22:39
*** yamahata has quit IRC22:39
anteayajroovers: so the first step is find the error22:40
jrooversanteaya: well it says that keystone did not start http://logs.openstack.org/67/62867/1/check/check-grenade-dsvm/b0941ce/console.html#_2013-12-18_13_16_25_58022:40
anteayaI'm trying to get in the habit of finding the error and using the timestamp in the url to get a useful link to use in my comment on the patch22:40
beaglessalv-orlando: the alternative would be to list all ports available to the integration library and filter them there22:40
anteayaso I can annotate my detective work on my own test failures22:41
beaglessalv-orlando: which wouldn't be the end of the world22:41
jrooversanteaya: that is good advice, I'll starting doing that as well :-)22:41
anteayait helps another to point out what is obvious might you might have overlooked22:41
anteayathen I write my assessment22:42
anteayasomething like this is a failure to upgrade and start keystone, this patch contains code to <purpose of patch> which does not affect starting keystone22:43
anteayathen I would see if I can find a bug in devstack or grenade or keystone that matches22:43
mlavallejroovers: the big picture is the following: each one of those gate jobs creates a devstack instance and the runsn against that devstack instance a battery of tempest tests, including  your patchset. So he console log, from a big picture perpective, has two sections. The first one is the creation of the devstack isntance. The second one is the execution of the tempest tests. In the case we are talking about, it didn't finish th22:43
mlavalledevstack instance creation. Never got to run the tempest tests with your patchset22:43
jrooversmlavalle: makes sense now, thanks22:44
mlavallejroovers: you will find useful going to the console log of one of the jobs that returned green in that patch submission. You will see the two sections22:45
anteayaif you find a bug, add to the bug report if you can and use recheck bug <bug number>22:45
anteayaif you can't find it, file a bug and then use your new bug number in the recheck22:45
anteayarecheck for the check queue22:45
anteayareverify for the gate queue (for patches that have been approved for merging)22:45
mlavallejroovers: here's the interesting case: a gate job that succesfully built the devstack instance, executed the tempst tests against it and one or several of the tests failed. In that case, the job will be also red in gerrit. And you should see what tempest tests failed and how they are related to your patch22:47
mlavallemakes sense?22:48
jrooversmlavalle, yes. And I think I'm experiencing that now http://logs.openstack.org/67/62867/1/check/check-tempest-dsvm-full/853cd04/console.html#_2013-12-18_22_13_13_97722:48
jrooversmlavalle, several compute tests failing22:49
mlavallejroovers: ok try to debug it. As I said, I am doing something else right now. But I'll get again to it later tonight.22:50
*** markwash has quit IRC22:51
mlavallei'll leave comments in gerrit for you so you can see them tomorrow morning, your time22:51
jrooversmlavalle, yes, but I'm going to rebase based on enikanorov's comments first. Thanks for the help. I'll probably won't be around later as it is getting late here22:51
jrooversmlavalle: much appreciated :-)22:51
mlavalleI know, you are 7 / 8 hours ahead of me22:51
mlavalle:-)22:52
jrooversmlavalle: approaching midnight here :-)22:52
mlavalleso go have a beer22:52
jrooversmlavalle: will be doing that right now :-)22:52
jrooversthanks again22:52
jrooversanteaya, thanks to you too22:53
*** ameade has joined #openstack-neutron22:53
jrooversanteaya, mlavalle, you're my heroes!22:53
* jroovers starts saving to buy beers for anteaya and mlavalle :-)22:53
mlavalleanteaya: I will add a "wrestling with the gate" section to that wiki page I put together for new developers22:54
mlavalleover the wekend22:54
anteayamlavalle: sounds like a great addition22:54
anteayathanks mlavalle22:55
anteayajroovers: looks like you are in a good spot22:55
anteayajroovers: keep us updated on your progress22:55
anteayaand be sure to ask questions22:55
marunsalv-orlando: so, I have a dumb discovery22:55
jrooversanteaya: will do, thanks!22:55
*** roeyc has quit IRC22:56
*** dims_ has quit IRC22:57
*** markwash has joined #openstack-neutron22:59
*** gdubreui has joined #openstack-neutron23:00
beaglesmlavalle anteaya: do either of you have anything to share with relevance to parity?23:05
mlavallebeagles: not right now23:05
beaglesmlavalle: if I gave you a list of the neutron methods called by way of the nova/neutron integration library, could you cross reference it with your API coverage gap analysis?23:06
mlavallebeagles: don't know but it doesn't hurt to try…. send it over. Most likley< I will try to do that over the weekend23:07
anteayabeagles: if you do it on an etherpad we can all look23:08
mlavallebeagles: I kind of suspect where you are trying to go23:08
beaglesmlavalle: ack.. I think I can pull that out pretty quickly tomorrow a.m. iirc you are west coast.. I think I'm probably something like 5 hours behind23:08
beaglesor ahead sorry23:08
anteayaand I have no valuable info to share with relevance to parity, no23:08
mlavalleI'm us central23:09
beaglesokay.. not so much.. but a few hours :)23:09
mlavalleTexas, to be precise23:09
beaglesnice!23:09
*** SushilKM has quit IRC23:09
beaglesand anteaya, yeah.. it'll go into an etherpad to start at least23:10
beaglesgets it out there23:10
anteayaawesome thank you23:12
openstackgerritCarl Baldwin proposed a change to openstack/neutron: Use information from the dnsmasq hosts file to call dhcp_release  https://review.openstack.org/5626323:12
anteaya<-- dinner23:12
beaglesI think we mentioned that tomorrow wasn't going to work for syncing up at 22:00 UTC23:12
beaglesI'll be in contact though during the day so we'll at least have some idea of what would be said at that time anyways23:12
*** dims_ has joined #openstack-neutron23:13
beaglesif 22:00 on Friday doesn't work for anybody, we should try to grab each other sometime earlier if possible23:14
*** markwash has quit IRC23:14
beaglesif I can come up with some concrete work items, I might be able to scrounge some bodies to work on them23:14
*** gdubreui has quit IRC23:16
beaglesanyways... I'm off to do domestic things for the rest of the evening and maybe wrap some gifts... till tomorrow23:16
*** banix has quit IRC23:17
*** carl_baldwin has quit IRC23:19
*** hichihara has joined #openstack-neutron23:21
*** hichihara has quit IRC23:22
anteayabeagles: sounds good to me23:24
*** jorisroovers has joined #openstack-neutron23:26
*** jroovers has quit IRC23:26
openstackgerritMicheal Thompson proposed a change to openstack/neutron: Fixed PEP8 import alphabetical order  https://review.openstack.org/6246423:28
dkehnwhaaaaaa23:31
*** layer427expert has joined #openstack-neutron23:31
*** layer427expert has quit IRC23:38
*** networkstatic is now known as networkstatic_zZ23:44
*** jorisroovers has quit IRC23:58

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