Monday, 2013-10-07

*** salv-orlando has quit IRC00:48
*** matsuhashi has joined #openstack-qa00:54
*** nosnos has joined #openstack-qa01:00
openstackgerritminsel proposed a change to openstack/tempest: Fixes test_network_basic_ops  https://review.openstack.org/4997701:41
*** jasondotstar|afk has quit IRC01:42
openstackgerritKen'ichi Ohmichi proposed a change to openstack/tempest: Add shelve/unshelve test of nova APIs  https://review.openstack.org/4989202:05
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/41615 failed tempest because of: https://bugs.launchpad.net/bugs/123543502:06
openstackrecheckopenstack/nova change: https://review.openstack.org/48196 failed tempest with an unrecognized error02:27
openstackrecheckopenstack/keystone change: https://review.openstack.org/49460 failed tempest with an unrecognized error02:36
openstackgerritKen'ichi Ohmichi proposed a change to openstack/tempest: Move negative action tests to right place  https://review.openstack.org/4998202:37
*** dims has quit IRC02:44
openstackrecheckopenstack/neutron change: https://review.openstack.org/48999 failed tempest because of: https://bugs.launchpad.net/bugs/123543502:46
*** kong has joined #openstack-qa02:51
openstackrecheckopenstack/neutron change: https://review.openstack.org/49936 failed tempest because of: https://bugs.launchpad.net/bugs/122400103:04
*** prekarat has joined #openstack-qa03:12
*** prekarat has quit IRC03:14
*** prekarat1 has joined #openstack-qa03:14
*** kong has quit IRC03:15
openstackrecheckopenstack/neutron change: https://review.openstack.org/49985 failed tempest because of: https://bugs.launchpad.net/bugs/122400103:20
openstackgerritKen'ichi Ohmichi proposed a change to openstack/tempest: Move negative action tests to right place  https://review.openstack.org/4998203:20
*** Mann has joined #openstack-qa03:24
*** ko_ has joined #openstack-qa03:25
*** Ghanshyam has joined #openstack-qa03:30
openstackrecheckopenstack/horizon change: https://review.openstack.org/49645 failed tempest with an unrecognized error04:10
raiesafazekas_zz: hi04:16
openstackgerritMh Raies proposed a change to openstack/tempest: VPNaas vpnservice test cases  https://review.openstack.org/4733904:18
openstackgerritMh Raies proposed a change to openstack/tempest: VPNaas IKE policies tests  https://review.openstack.org/4734804:19
openstackgerritMh Raies proposed a change to openstack/tempest: VPNaas IPSec policies tests  https://review.openstack.org/4781604:20
openstackgerritMh Raies proposed a change to openstack/tempest: VPNaas IPSec Site Connection API tests  https://review.openstack.org/4822004:20
*** afazekas has joined #openstack-qa04:44
*** afazekas_zz has quit IRC04:44
openstackrecheckopenstack/tempest change: https://review.openstack.org/48220 failed tempest with an unrecognized error04:46
openstackrecheckopenstack/tempest change: https://review.openstack.org/47339 failed tempest with an unrecognized error04:51
openstackrecheckopenstack/tempest change: https://review.openstack.org/47348 failed tempest with an unrecognized error04:55
openstackrecheckopenstack/tempest change: https://review.openstack.org/47816 failed tempest with an unrecognized error05:03
*** SergeyLukjanov has joined #openstack-qa05:11
*** Madan has joined #openstack-qa05:20
openstackrecheckopenstack/neutron change: https://review.openstack.org/48999 failed tempest because of: https://bugs.launchpad.net/bugs/122400105:21
*** SergeyLukjanov has quit IRC05:25
*** DennyZhang has joined #openstack-qa05:28
*** sourabh has joined #openstack-qa05:28
openstackgerritafazekas proposed a change to openstack-dev/devstack: install_pip script fails if pip was not installed  https://review.openstack.org/4999005:32
openstackgerritafazekas proposed a change to openstack-dev/devstack: install_pip script fails if pip was not installed  https://review.openstack.org/4999005:33
*** nosnos has quit IRC05:36
*** nosnos_ has joined #openstack-qa05:36
*** DennyZhang has quit IRC05:37
*** SergeyLukjanov has joined #openstack-qa05:45
*** shilpa_ has joined #openstack-qa05:54
*** matsuhashi has quit IRC05:56
*** SergeyLukjanov has quit IRC06:00
*** Mann has quit IRC06:03
*** Ghanshyam has quit IRC06:04
kashyapafazekas, Heya, morning, so on the side, I just started to try latest Havana, bits and I see these mongodb failures - http://paste.openstack.org/show/48014/06:26
*** matsuhashi has joined #openstack-qa06:30
kashyapI thought I'll check with you, as you're swimming in OpenStack day in and day out06:37
*** dkorn has joined #openstack-qa06:39
openstackrecheckopenstack/cinder change: https://review.openstack.org/49681 failed tempest with an unrecognized error06:43
*** matsuhashi has quit IRC06:51
*** matsuhashi has joined #openstack-qa06:54
*** notmyname has quit IRC06:58
*** notmyname has joined #openstack-qa06:59
*** matsuhas_ has joined #openstack-qa07:01
*** matsuhashi has quit IRC07:01
afazekaskashyap: can you start the mongodb by hand ?07:02
*** nosnos has joined #openstack-qa07:02
*** nosnos_ has quit IRC07:02
kashyapTrying07:03
kashyapafazekas, Um, starting the service is just stuck - systemctl start mongod.service07:04
kashyapOk, it fails, looking for logs07:05
*** jlibosva has joined #openstack-qa07:07
kashyapafazekas, Side question - what's mongodb used for here?07:07
afazekaskashyap: ceilometer using it as database, AFAIK the sql backend is not fully completed, and mongodb expected to be faster anyway07:08
kashyapafazekas, I'm trying to stand-up a minimal OpenStack07:09
kashyapafazekas, I don't really much care about Ceilometer. So, if I have to go minimal, I think the only way is to selectively install packages and configure things, right?07:10
*** prekarat1 has quit IRC07:11
afazekasyou can install openstack without ceilometer07:11
afazekasBTW: mongodb is able to start with it's default config without any change on f1907:12
afazekasprobbaly your installer did something unwise..07:12
kashyapYeah, it's packastack. I'm using latest f1907:15
kashyapWhat's your working mongodb version?07:15
afazekaspython-pymongo-2.5.2-1.fc19.x86_6407:19
afazekasmongodb-server-2.4.6-1.fc19.x86_6407:19
*** nosnos has quit IRC07:19
afazekasmake sure you have enough free space, it uses a huge amount of storage07:19
kashyapI don't even have python-pymongo07:20
kashyapafazekas, Duh, I'm doing this all on a VM. (OpenStack in a vm).  Will check the storage too07:20
*** nosnos has joined #openstack-qa07:20
kashyapI have 38G of available free space, that should be sufficient I guess07:21
*** yeylon_ has joined #openstack-qa07:25
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/39280 failed tempest because of: https://bugs.launchpad.net/bugs/122400107:44
openstackrecheckopenstack/nova change: https://review.openstack.org/48886 failed tempest with an unrecognized error07:50
*** dkorn has quit IRC07:55
*** fbo_away is now known as fbo07:59
openstackrecheckopenstack/neutron change: https://review.openstack.org/49596 failed tempest because of: https://bugs.launchpad.net/bugs/122400108:01
*** jlibosva has quit IRC08:01
*** jlibosva has joined #openstack-qa08:01
raiesafzekas: https://review.openstack.org/#/c/48632/08:02
*** giulivo has joined #openstack-qa08:02
raiesgiulivo: https://review.openstack.org/#/c/48632/08:03
*** dkorn has joined #openstack-qa08:08
*** yassine has joined #openstack-qa08:12
*** prekarat has joined #openstack-qa08:18
*** jhenner has joined #openstack-qa08:22
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/39280 failed tempest with an unrecognized error08:24
*** salv-orlando has joined #openstack-qa08:24
openstackgerritMasayuki Igawa proposed a change to openstack/tempest: Fix skip_because decorator  https://review.openstack.org/5000808:25
*** jlibosva has quit IRC08:29
*** jlibosva has joined #openstack-qa08:32
*** SergeyLukjanov has joined #openstack-qa08:33
openstackgerritMasayuki Igawa proposed a change to openstack/tempest: Fix skip_because decorator  https://review.openstack.org/5000808:55
*** dkorn has quit IRC08:58
*** yeylon_ has quit IRC08:59
*** jlibosva1 has joined #openstack-qa09:04
*** dkorn has joined #openstack-qa09:04
*** yeylon_ has joined #openstack-qa09:05
*** jlibosva has quit IRC09:06
Madanafazekas: ping09:17
afazekasMadan: pong09:28
MadanAfazekas: do you have any documents that would guide us to configure tempest09:29
Madanafazekas: Not for devstack09:30
afazekaspsedlak: ^^09:30
Madanafazekas: There is team working on Power VC which is built on openstack,, They wanted to configure tempest09:31
openstackgerritMasayuki Igawa proposed a change to openstack/tempest: Fix skip_because decorator  https://review.openstack.org/5000809:33
afazekasMadan: novanetwork or neutron ?09:34
MadanAfazekas: it is different i guess,, Like Power virtulization Center,, I'm very new to tempest so :(09:36
afazekashttp://logs.openstack.org/20/42920/11/check/check-tempest-devstack-vm-full/268cdff/console.html.gz  after '2013-10-01 09:54:44.068 | 2013-10-01 09:54:44' it prints the config used on the gate system09:38
afazekasthe admin user creadentials needs to be configured, and two addtional user needs to be created and configured09:39
afazekasYou need to have a small bootable image uploaded to the glance, it's id needs to be configured09:39
afazekasfor the ec2 you need to do an euca bundle  (using the test system x509 certs)09:40
afazekasUsually the default values are good,  if you have question related to particular failure let me know09:42
MadanAfazekas: Ok,, i'll Try and let you update on this :)09:46
openstackrecheckopenstack/neutron change: https://review.openstack.org/43724 failed tempest because of: https://bugs.launchpad.net/bugs/122400109:51
*** ko_ has quit IRC10:08
*** gszasz has joined #openstack-qa10:17
*** gszasz has quit IRC10:18
*** gszasz has joined #openstack-qa10:19
*** gszasz has quit IRC10:20
giulivoraies, if there aren't tests tied to those actions, I really think you should strip those out of the submission and repost them together with some tests in a different one10:32
giulivothe basic idea is to only merge changes which are actually teste10:33
giulivod*tested10:33
mkoderergiulivo: https://review.openstack.org/#/c/50008/310:53
mkoderergiulivo: I am sure you are interested in that one10:53
giulivoindeed, but I tested it, I'm not sure why the guy is reporting that10:54
giulivoyou know, jenkins actually also tested it10:54
*** gszasz has joined #openstack-qa10:56
mkoderergiulivo: the thing is that decorators that causing errors are simply ignored by subunit discover10:57
mkoderergiulivo: are you sure that you tested this case? A skipped test with condition = False?10:58
mkoderergiulivo: mh but if you have a look in https://bugs.launchpad.net/tempest/+bug/123622011:00
mkodererthe bug that he's refering to is not closed...11:00
giulivoso the first thing is, with nose I don't get the error at all11:02
giulivoalso I've just tested that case you mention too, it just doesn't skip, as expected11:07
mkoderergiulivo: so the bug report is invalid for sure11:08
giulivono I'm not sure, I'm trying to figure what happens with testr11:08
mkodererthe StringException is a bit wired11:10
*** HenryG has quit IRC11:20
giulivomkoderer, I'm unable to reproduce that :(11:31
giulivooh wait, I found a case11:31
giulivomkoderer, anyway thanks for pointing that out ... looks like that only happens when running a class rather than a test; I'm not sure why really, looking into it11:45
*** dims has joined #openstack-qa11:46
*** rfolco has joined #openstack-qa11:49
giulivomkoderer, and the same problem is affecting for instance the attr decorator11:49
openstackrecheckopenstack/heat change: https://review.openstack.org/49673 failed tempest with an unrecognized error11:53
afazekashttps://review.openstack.org/#/c/50008/3/tempest/test.py with @functools.wraps(f) I guess the def 'decorator(f):'  is not required11:59
openstackgerritA change was merged to openstack/tempest: tempest/config.py parse some sections incorrectly  https://review.openstack.org/4850211:59
*** prekarat has quit IRC12:03
*** matsuhas_ has quit IRC12:04
*** matsuhashi has joined #openstack-qa12:06
*** jlibosva1 has quit IRC12:08
*** Madan has quit IRC12:08
*** jlibosva has joined #openstack-qa12:09
*** prekarat has joined #openstack-qa12:09
*** matsuhashi has quit IRC12:10
*** matsuhashi has joined #openstack-qa12:11
*** prekarat1 has joined #openstack-qa12:11
*** prekarat has quit IRC12:13
*** prekarat1 has quit IRC12:14
*** weshay has joined #openstack-qa12:14
giulivoafazekas, so that only happens when launching a "class" not when actually launching the test case, I think I figured why so would like to suggest a different approach12:15
*** weshay has quit IRC12:15
openstackgerritIvan-Zhu proposed a change to openstack/tempest: port test_images and test_server_actions into v3 part2  https://review.openstack.org/3960912:16
*** adalbas has joined #openstack-qa12:19
giulivoafazekas, the thing is that we raise instead of decorate12:20
afazekasis the ' @functools.wraps(f)' really required ?12:20
giulivoyeah indeed I was suggesting to remove that12:21
giulivostill I'm not sure why what won't cause errors when running a single test case12:21
giulivoalso, for whatever reason, it wasn't affecting nose :(12:24
*** shilpa_ has quit IRC12:30
openstackgerritGiulio Fidente proposed a change to openstack/tempest: uses skip_because where appropriate instead of regular skip  https://review.openstack.org/5005212:30
*** SergeyLukjanov has quit IRC12:30
*** SergeyLukjanov has joined #openstack-qa12:32
giulivoafazekas, https://review.openstack.org/#/c/50008/ see my inline12:32
*** jlibosva has quit IRC12:35
afazekas'Without the use of this decorator factory, the name of the example function would have been 'wrapper', and the docstring of the original example() would have been lost.'12:38
afazekasSo it is just for preserving the name and the docstring12:39
afazekasgiulivo: I Would like to +2 it as it is12:43
*** jlibosva has joined #openstack-qa12:44
giulivoI see but we don't use it for the other decorators doing the same thing (like attr or services), that's why I wanted to avoid using functools12:45
*** nosnos has quit IRC12:47
giulivomaybe we can suggest to actually use that in all of them?12:47
dkranzgiulivo, afazekas : Can you please look at https://review.openstack.org/#/c/49808/  which is needed for me to push the devstack change.12:49
*** kong has joined #openstack-qa12:52
afazekasgiulivo: the others just changing attrs and does not replacing the function in the 'usual' way, one indirection is optimized out :)12:53
*** rustlebee is now known as russellb12:54
afazekasdkranz: TRACE messages ?12:54
dkranzafazekas: All our code that looks for log errors checks for ERROR/TRACE, no?12:55
afazekaswhy not for ERROR and CRITICAL ?12:55
*** matsuhashi has quit IRC12:55
*** weshay has joined #openstack-qa12:56
*** matsuhashi has joined #openstack-qa12:56
giulivoafazekas, and to be honest, I'm not sure why raising from within the decorator is not causing troubles when using functools12:57
afazekasgiulivo: bacause it runs at declare time12:58
giulivoand without'12:58
giulivo?12:58
afazekasNot the functools fixing it,  the additional 'inline' function12:58
afazekasthe new decorator even without the '@functools.wraps(f)'  would be a fix12:59
afazekasbut all other line is required12:59
*** matsuhashi has quit IRC13:00
afazekasdkranz: AFAIK the TRACE log level us under the DEBUG log level13:01
*** matsuhashi has joined #openstack-qa13:01
afazekasdkranz: I see it is an openstack special log.exception level :)13:03
konghi all, there are some different ideas between Ken'ichi and I, https://review.openstack.org/#/c/49488/, I want to hear others' opinion, especially the Cores.13:03
afazekasdkranz: please look for the CRITICAL messages as well13:03
*** matsuhashi has quit IRC13:13
*** matsuhashi has joined #openstack-qa13:14
*** mriedem has joined #openstack-qa13:16
*** matsuhashi has quit IRC13:18
openstackrecheckopenstack/neutron change: https://review.openstack.org/49424 failed tempest because of: https://bugs.launchpad.net/bugs/122400113:20
*** mkollaro has joined #openstack-qa13:21
afazekaskong: when the force delete expected to be succeed or fail ?13:22
*** HenryG has joined #openstack-qa13:25
dkranzafazekas: OK, I will include CRITICAL.  I will make that change in the real version I have. I wanted to just push this so I can hook up devstack-gate to call it.13:31
dkranzafazekas: Then I will update the script to do the real thing in main.13:32
afazekasdkranz: ok13:32
dkranzafazekas: So it would help if you could approve this dummy version.13:32
dkranzafazekas: Thanks13:32
dkranzafazekas: I am also going to add a "-u" option that can point to a url13:33
afazekasdkranz: will the yaml file contain filenames ?13:34
giulivodkranz, I missed you were in while I was writing the comments... I found the directory/files combination confusing a bit too, I wanted to suggest directory as a required arg and then allow for arbitrary regexp so people could write their own filter13:36
giulivodkranz, -u would actual download all log files from some http and check those?13:37
giulivo(the regexp would be applied on filenames=13:37
openstackgerritGiulio Fidente proposed a change to openstack/tempest: uses skip_because where appropriate instead of regular skip  https://review.openstack.org/5005213:40
dkranzafazekas: Yes, the yaml will contain file names mapped to a list of whitelist regexps13:42
dkranzgiulivo: Yes -u will download the files and search them13:42
dkranzgiulivo, afazekas : Please wait until I have pushed the real code for more comments/questions13:42
dkranzgiulivo, afazekas : I just need -d now which is what devstack-gate will call13:43
giulivodkranz, I like the directory argument over multiple files too13:44
dkranzgiulivo: Remember the real goal of this is to have no whitelist. That is just to get us going13:44
kongafazekas, only if the 'reclaim_instance_interval' is set, you can force delete a server.13:47
afazekasdkranz: What kind of dark spell are you planning to cast for suppressing the ERROR output from the boto negative tests ?13:48
dkranzafazekas: I thought you knew how to do that?13:49
afazekaskong: if the reclaim interval is set can you force-delete an active server ?13:49
afazekasdkranz: I can figure out a way, but I can not guarantee it will not be dirty :)13:49
dkranzafazekas: You mean in the tempest log?13:50
afazekasyes13:50
kongafazekas, yes13:50
kongafazekas, you must soft-delete a server first13:51
dkranzafazekas: I'll take a look when I get to putting in the actual whitelist13:51
dkranzafazekas: BTW, is it possible to put a string in a yaml file that will be read in to Python as if it were in the code as r"..."13:52
afazekaskong: so the  test_force_delete_server_invalid_state will be 409 even if the reclaim_instance_interval is set, bacuse first I need to do 'regular' soft delete before the force one , right ?13:53
kongafazekas, actually, yes13:54
afazekasdkranz: ' If deemed appropriate, the record may be modified in-place by this method.' http://docs.python.org/2/library/logging.html#filter-objects  seems to be one option13:55
dkranzafazekas: I'll take a look13:55
afazekasdkranz: the other option is aggressive monkey patching .., so the above  seams to be the nicer dirty way13:56
dkranzafazekas: Just say no to monkey patching :)13:57
*** gszasz has quit IRC13:58
*** dkorn has quit IRC13:58
dkranzafazekas, giulivo :  I could resubmit the patch with just a main that returns 0 if you prefer. But it would be easier if you could just +2 it for bootstrapping purposes.13:59
*** yeylon_ has quit IRC14:01
*** gszasz has joined #openstack-qa14:01
*** HenryG has quit IRC14:01
*** dkorn has joined #openstack-qa14:05
afazekasdkranz: The patch in this form almost does nothing, just reserves file names.14:14
afazekaswhitelist.yaml should be in the etc IMHO14:14
*** dkranz has quit IRC14:16
giulivoafazekas, "It restores 100+ test case run" ?14:21
afazekasgiulivo: check the running test cases number after and before the patch14:21
giulivowhy would that be?14:22
afazekasraising the skip exception on class deceleration time or at method call time is big difference14:26
afazekashttp://www.fpaste.org/44786/11559791/ # it prints without a function call14:26
*** marun has joined #openstack-qa14:41
*** kong has quit IRC14:44
openstackrecheckopenstack/tempest change: https://review.openstack.org/49934 failed tempest with an unrecognized error14:48
afazekasgiulivo: you should consider  approving the skip decorator fix  before someone introduces a bug14:52
*** torandu has joined #openstack-qa15:02
afazekassdague: Which type of change would you prefer ? Fully killing the setUpClasses and tearDownClasses, or have them to be able to capture log and call force call super and each other when the clean up is required ?15:03
*** prekarat has joined #openstack-qa15:04
*** dkranz has joined #openstack-qa15:04
afazekassetupclass killing would lead to repeating the setupclass/teardownclass class actions with every test method, it may lead to performance degradation, until a testresources (or similar) solution (with per process isolation) not added for server sharing15:07
afazekasThe forced tearDownclass super call can be implemented as decorator, which can replace the classmethod decorator. The setUpClass can attempt to call the tearDownclass on error (or just delete the isolated credentials on skip)15:10
*** mlavalle has joined #openstack-qa15:13
openstackrecheckopenstack/neutron change: https://review.openstack.org/49994 failed tempest with an unrecognized error15:13
openstackgerritDavid Kranz proposed a change to openstack/tempest: Placeholder log check script to be called by devstack-gate  https://review.openstack.org/4980815:16
mkoderersdague: I would like to get rid of the failing stress tests - could you have a look to https://review.openstack.org/#/c/49870/115:23
mkodererdkranz: ^^15:23
dkranzmkoderer: Just a sec. ANd can you look at the one I pushed a few minutes ago?15:24
mkodererdkranz: https://review.openstack.org/#/c/49808/? ok sure15:24
dkranzmkoderer: Doesn't an exception from the framework mean there is a bug in the framework?15:26
mkodererdkranz: yes there is one somewhere..15:27
dkranzmkoderer: Then don't we want it to fail?15:28
mkodererdkranz: aha you mean the result code?15:28
mkodererdkranz: yes :)15:29
dkranzmkoderer: Yes15:29
mkodererdkranz: ok you will get in in the next secs15:29
dkranzmkoderer: 'except' should return non-zero I think15:29
mkodererdkranz: mhh not sure with it15:30
*** torandu has quit IRC15:30
*** torandu has joined #openstack-qa15:31
mkodererdkranz: regarding https://review.openstack.org/#/c/49808/2/ .. so it's the first step, you just want to have a placeholder to see if it's called?15:32
dkranzmkoderer: It will get called from devstack-gate15:32
mkodererdkranz: and you will enhance it later on?15:33
*** dkorn has quit IRC15:33
dkranzmkoderer: I want to be able to test the real code in an actual job before pushing it15:33
dkranzmkoderer: Yes15:33
dkranzmkoderer: Soon15:33
mkodererdkranz: ok just because it does "nothing" ;)15:34
dkranzmkoderer: Right, I want to establish the correct flow and behavior, then change it to actually do something useful15:34
openstackrecheckopenstack/swift change: https://review.openstack.org/49583 failed tempest with an unrecognized error15:35
mkodererdkranz: ok need to wait for jenkins :)15:36
mkodererbut LGTM15:36
dkranzmkoderer: thanks15:36
mkodererdkranz: I will have a look to the result code and add a exit call if it's mandatory15:37
openstackrecheckopenstack/swift change: https://review.openstack.org/49169 failed tempest with an unrecognized error15:43
*** yassine has quit IRC15:57
*** SergeyLukjanov has quit IRC16:01
openstackgerritafazekas proposed a change to openstack/tempest: glance v2 image share WIP  https://review.openstack.org/5012216:07
openstackgerritA change was merged to openstack-dev/devstack: Fix "instal_prereqs.sh" typo  https://review.openstack.org/4984816:09
openstackgerritA change was merged to openstack/tempest: Fix skip_because decorator  https://review.openstack.org/5000816:09
*** afazekas has quit IRC16:11
*** jlibosva has quit IRC16:13
openstackrecheckopenstack/neutron change: https://review.openstack.org/49644 failed tempest with an unrecognized error16:22
*** flashgordon is now known as jog016:27
Anjudkranz:  ping16:28
openstackgerritMarc Koderer proposed a change to openstack/tempest: Add addtional logging and catch exceptions  https://review.openstack.org/4987016:31
*** SergeyLukjanov has joined #openstack-qa16:35
Anjusdague : https://blueprints.launchpad.net/tempest/+spec/multinode-testing16:39
openstackgerritA change was merged to openstack/tempest: Placeholder log check script to be called by devstack-gate  https://review.openstack.org/4980816:39
*** HenryG has joined #openstack-qa16:57
*** fbo is now known as fbo_away17:01
*** prekarat has quit IRC17:03
dkranzAnju: Yes?17:05
*** DennyZhang has joined #openstack-qa17:06
Anjudkranz:   https://blueprints.launchpad.net/tempest/+spec/multinode-testing17:11
dkranzAnju: What did you want to say about that blueprint?17:11
Anjuis this completed17:12
Anju?17:12
*** dims has quit IRC17:12
dkranzAnju: No17:12
dkranzAnju: It requires infra to allow a job to use multiple vms17:13
Anjudkranz:  then is there any tempest config for mutinode setup17:13
dkranzAnju: Tempest is not concerned with setup17:13
dkranzAnju: You configure your system and edit tempest.conf to use the appropriate credentials, urls, etc.17:13
Anjuok ok thanks dkranz17:14
dkranzAnju: Your welcome.17:14
dkranzAnju: Multinode tests upstream will be discussed again at the upcoming Hong Kong summit17:14
Anjuokkk okk then I will be there17:15
Anjubtw thanks marc17:16
Anju:)17:16
Anjubtw thanks dkranz17:17
*** dims has joined #openstack-qa17:24
*** mlavalle has quit IRC17:26
*** harlowja has joined #openstack-qa17:29
*** raies_ has joined #openstack-qa17:40
dkranzmtreinish: ping17:41
mtreinishdkranz: pong17:41
dkranzmtreinish: I'm a bash novice. Does this make sense?  http://paste.openstack.org/show/48032/17:41
raies_jaypipes: hi17:43
marunhi all17:43
mkodererdkranz: https://review.openstack.org/#/c/49870/217:43
marunI have a possible lead on the neutron gate failures....17:43
mtreinishdkranz: it seems reasonable17:44
dkranzmtreinish: THanks. I'll submit that, and then the real log_error script.17:44
mtreinishmarun: cool17:44
dkranzmkoderer: How is this different than the previous behavior?17:45
mkodererdkranz: I added a sys exit if a exception was raised17:45
dkranzmkoderer: If there was an exception woudn't the stacktrace be printed and then exit nonzero?17:45
marunmtreinish: mlavalle claims to be able to fix the problem by logging in via password instead of ssh key17:45
mkodererdkranz: no the exit code was 0 before17:45
dkranzmkoderer: I mean this change you are making?17:45
marunmtreinish i just realized that this indicates that the failure could be due to ip reuse17:46
dkranzmkoderer: Sorry, I don't mean the previous version of this patch17:46
marunmtreinish: password on cirros is always the same, but if the ip is reused and tempest is trying to hit the wrong vm, key based auth would fail17:46
mkodererdkranz: so what happens now: if a exception is raised the result code will be 117:46
dkranzmkoderer: What is the current failure behavior you didn't like that prompted this change?17:46
mkodererdkranz: currently we get a "CRITICAL tempest [-] local variable 'attrs' referenced before assignment"17:47
mkodererdkranz: with no stack trace17:47
mtreinishmarun: hmm, that's a good catch. That should be true.17:48
dkranzmkoderer: Yes, I see that missing attr has to be fixed. But not sure why the extra exit logic is needed. I misunderstood with my comment earlier this morning.17:48
*** mlavalle has joined #openstack-qa17:48
mtreinishI haven't checked the key pair code in tempest, I don't remember how they're being used there17:48
mkodererdkranz:  you mean the catch of the exception?17:49
dkranzmkoderer: Yes, I'm not sure it does anything different.17:49
dkranzmkoderer: But it is not wrong17:49
mkodererdkranz: it will print the stack trace..17:49
mkodererdkranz: before it simple print out the error without a trace17:49
mkodererdkranz: I thought that python will do it automatically but it doesn't17:50
dkranzmkoderer: ok17:51
mtreinishmarun: refresh my memory are the isolated jobs only failing on /3)───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────17:51
mtreinishwow that paste buffer got all screwed up :)17:51
dkranzmkoderer: I gave it a +217:51
mtreinishit should have been test_network_basic_ops17:51
marunmtreinish: mlavalle has committed to submitting a patch that would do a password-based check before the key-baesd check, so that the problem will be more apparent.17:51
mkodererdkranz: thanks17:51
mtreinishmarun: or does it fail in other places too17:51
marunjust the isolated jobs afaik17:52
mtreinishmarun: I meant is it just the one test or on other tests too?17:54
marunmtreinish: just the one test that I can see17:54
marunmtreinish: the neutron connectivity check17:54
mtreinishmarun: yeah I think doing the test with a password and keypair is probably a good change to make in general17:54
mtreinishmarun: yeah for those tests it generates a fresh keypair and uses that for server creation. So I'm not sure it's actually ip reuse being the problem17:55
*** gszasz has quit IRC17:55
openstackgerritDennyZhang proposed a change to openstack/tempest: remove code duplication in tempest/config.py  https://review.openstack.org/5014217:55
mlavallemtreinish: yes, i'll create a patch set  that does both checks17:56
marunmtreinish: The point is that the server in question that the test is attempting to verify connectivity for is not the server that is reachable via the ip that nova knows about.17:56
marunmtreinish: it's not a solution, but at least we can narrow our focus.17:57
mtreinishmarun: oh I see what you're saying17:57
openstackgerritDennyZhang proposed a change to openstack/tempest: remove code duplication in tempest/config.py  https://review.openstack.org/5014217:58
openstackgerritDavid Kranz proposed a change to openstack-infra/devstack-gate: Call a script to check for ERRORs in logs on tempest success  https://review.openstack.org/5014318:00
mtreinishmlavalle: my only concern with doing both is that we'll have a hardcoded assumption that it's a cirros image we are bring up. So we should probably make the password a config option and default it to cirros creds. (ideally we'd inject the password, but then we'd have the same problem as with keypairs)18:01
mlavallemtreinish: you are right. in fact, the option already exists in tempest.conf. it's only that it is not being configured in the gate jobs, so last night i just wanted to do a 'quick and dirty' show of concept. But you are right, it should be an option configured in tempest.conf18:03
mtreinishmlavalle: you're right (there are too many config options) it should be fine to use those, just make sure they're they default to the cirros creds18:04
mtreinishmlavalle: whatever is in sample.conf is used unless devstack overwrites it18:05
mkoderermtreinish: if you have some time https://review.openstack.org/#/c/49870/218:05
openstackrecheckopenstack/nova change: https://review.openstack.org/45421 failed tempest with an unrecognized error18:05
mlavallemtreinish: agree18:05
openstackrecheckopenstack/neutron change: https://review.openstack.org/45927 failed tempest because of: https://bugs.launchpad.net/bugs/122400118:07
*** raies_ has quit IRC18:08
openstackrecheckopenstack/requirements change: https://review.openstack.org/50140 failed tempest with an unrecognized error18:10
*** dkranz has quit IRC18:21
Anjumtreinish:  is there any setting to run nova v3 api18:22
*** dkranz has joined #openstack-qa18:23
mtreinishAnju: there aren't any v3 api tests in tempest yet. There will be an option when they start to merge into tempest.18:24
Anjuyes mtreinish  I know about that18:24
AnjuIvan started that18:24
mtreinishAnju: or were you talking about in nova?18:25
Anjubut i am not able to run v3 api18:25
Anjuyes mtreinish18:25
Anjumtreinish:  can you please help18:26
mtreinishAnju: there are a couple things that you have to set. I think the easiest way would be to look at the devstack code around the v3 api18:28
mtreinishhttps://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/nova18:28
mtreinishthat should give good instructions on how to set it up18:28
Anjuohh mtreinish  thanks for help18:28
mtreinishAnju: there is a config option and you also have to register another endpoint in keystone18:29
Anjuokk mtreinish  I will do that also18:30
Anjucheccking18:30
*** fbo_away is now known as fbo18:30
openstackrecheckopenstack/neutron change: https://review.openstack.org/49644 failed tempest because of: https://bugs.launchpad.net/bugs/122400118:33
mriedemhi, shameless request for another +2 on this set of patches: https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bug/1235411,n,z18:35
mriedemfrom a non-ibm core :)18:35
openstackgerritDennyZhang proposed a change to openstack/tempest: remove code duplication in tempest/config.py  https://review.openstack.org/5014218:47
*** zzs has joined #openstack-qa18:52
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: Add query for bug 1235486  https://review.openstack.org/4984618:59
mtreinishmriedem: stop bugging me I already +2'd them :)19:04
openstackrecheckopenstack/swift change: https://review.openstack.org/49169 failed tempest with an unrecognized error19:05
openstackgerritArmando Migliaccio proposed a change to openstack-dev/devstack: Specify agent mode and service cluster uuid for nicira plugin  https://review.openstack.org/4836819:06
mriedemmtreinish: you're a dirty ibmer though19:06
*** yeylon_ has joined #openstack-qa19:07
*** hemnafk is now known as hemna19:09
dkranzmriedem: OK, I approved them.19:12
mriedemdkranz: thanks19:12
dkranzmtreinish: Do you know what is going on with the coverage builds?19:12
dkranzmtreinish: I can't find one that has any coverage data and there are failures invoking the script in the log.19:12
openstackrecheckopenstack/neutron change: https://review.openstack.org/49994 failed tempest with an unrecognized error19:13
*** fbo is now known as fbo_away19:21
*** pleia2 has quit IRC19:22
mtreinishdkranz: no I don't know what's wrong with them19:27
mtreinishI can't reproduce the failure locally19:27
*** pleia2 has joined #openstack-qa19:27
mtreinishI've been meaning to push a debug message patch to the coverage scripts19:27
mtreinishlet me do that now19:27
mtreinishdkranz: it's kind of weird it just exits with a failure status and no errors19:28
dkranzmtreinish: Yeah19:28
dkranzmtreinish: How do I find the most recent successful coverage build?19:28
mtreinishdkranz: they're somewhere in here: http://logs.openstack.org/periodic/periodic-tempest-devstack-vm-coverage/19:29
mtreinishthe naming dir naming isn't very good anymore19:30
mtreinishdkranz: here is the most recent pass I could find: http://logs.openstack.org/periodic/periodic-tempest-devstack-vm-coverage/devstack-precise-hpcloud-az2-428529/29/logs/coverage-report/19:32
dkranzmtreinish: So I looked in the logs of a recent build but there is no coverage_report dir like I expect from lookint at devstasck-gate-wrap.sh19:33
mtreinishfrom oct 1st19:33
dkranzmtreinish: I was looking at Oct 4 which must have failed19:33
mtreinishdkranz: yeah that's the part that is failing the script that makes the api calls to create the reports19:33
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: Change test_queries from logical AND to OR  https://review.openstack.org/5016019:33
mtreinishit just exits with a return code >0 and no error message19:33
dkranzmtreinish: The biggest trouble is that I don't know how to get from the jenkins display for a job to its logs19:33
mtreinishand nothing gets created19:33
dkranzmtreinish: I see19:34
mtreinishdkranz: on a successful run there is normally a link on a line like: "Detailed logs: http://logs.openstack.org/" towards the bottom of the run19:35
mtreinishor you can replace the /srv/static/logs on the scp lines with logs.openstack.org19:35
openstackrecheckopenstack/tempest change: https://review.openstack.org/49819 failed tempest with an unrecognized error19:42
*** DennyZhang has quit IRC19:45
openstackrecheckopenstack/neutron change: https://review.openstack.org/49644 failed tempest because of: https://bugs.launchpad.net/bugs/122400119:47
*** fbo_away is now known as fbo20:00
mtreinishdkranz: actually I just found the issue with the coverage runs: http://logs.openstack.org/periodic/periodic-tempest-devstack-vm-coverage/devstack-precise-hpcloud-az1-557068/32/logs/tempest.txt.gz#_2013-10-07_06_27_39_10820:02
mtreinishit looks the coverage extension is failing to start20:02
mtreinishI'm not sure why the error isn't being raised through the script though20:02
dkranzmtreinish: Huh. So that's a nova bug, right?20:02
mtreinishdkranz: it probably is, but I need to dig further. (in the nova logs) on the tempest side it gets a 200 for starting coverage: http://logs.openstack.org/periodic/periodic-tempest-devstack-vm-coverage/devstack-precise-hpcloud-az1-557068/32/logs/tempest.txt.gz#_2013-10-07_06_07_25_60120:04
*** mp_ has joined #openstack-qa20:05
dkranzmtreinish: I see. "report" is failing.20:05
mp_I am trying to bring up devstack.  anyone had issues with keystone? keystone service-create and endpoint creation failed with HTTP 503.20:06
mtreinishdkranz: yeah, and that's the action that stops coverage collection and generates a report file20:06
mp_anyone had this similar problem?20:06
mtreinishthen the script takes that report and copies to a known location20:06
dkranzmtreinish: Yeah, I saw that in the code.20:07
openstackrecheckopenstack/cinder change: https://review.openstack.org/45130 failed tempest with an unrecognized error20:09
*** jlibosva has joined #openstack-qa20:33
*** jamielennox|away is now known as jamielennox20:39
*** DennyZhang has joined #openstack-qa20:42
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Update to latest tox  https://review.openstack.org/4955920:52
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Update to latest tox  https://review.openstack.org/4955920:52
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Split out unit tests as separate tox jobs  https://review.openstack.org/4956220:53
*** weshay has quit IRC21:01
mriedemmtreinish: apparently my patch for bug 1234370 didn't completely fix the problem, i see the issue and will post another patch. just wondering, does the new patch refer to the old bug or do i need to create a new one?21:05
*** rfolco has quit IRC21:06
mtreinishmriedem: if it's the same bug I'd reopen it and it should be fine to use it again21:06
mriedemok21:06
mtreinishunless it's a new bug that you found after closing the original one21:06
mriedemmtreinish: no, same problem, just my patch didn't resolve it (false positive in my testing)21:07
mriedemi got MULTI_USER and allow_tenant_isolation mixed up21:07
mtreinishmriedem: well, then so did I :)21:08
*** mp_ has quit IRC21:13
openstackgerritMatt Riedemann proposed a change to openstack/tempest: Cleanup existing instances in setup for test_list_servers_negative.py  https://review.openstack.org/5017221:13
mriedemi mean, c'mon, who runs tempest without tenant isolation anyway?!21:14
openstackgerritA change was merged to openstack/tempest: Add addtional logging and catch exceptions  https://review.openstack.org/4987021:16
mtreinishmriedem: I agree it's pseudo stress testing look at what it shook out in neutron. Plus you can run in parallel with it.21:17
mtreinishoops I guess thats a sour subject since you run it on 2.621:17
mriedemmtreinish: i was just joking21:17
mriedemmtreinish: and yes, now my feelings are hurt21:18
*** HenryG has quit IRC21:18
mriedemi would prefer to run w/ tenant isolation with testr if i could21:18
mtreinishmriedem: why do you run in on 2.6? Just bring up an ubuntu or fedora guest on your devstack cloud and use that to run tempest.21:19
mtreinishI think that should work21:19
mriedemmtreinish: i don't know, something about people wanting the code tested on the supported OS they are shipping products on - that whole rigmarole21:21
mriedemin other words, i'm tied to it21:21
mtreinishmriedem: ok I can understand that21:21
mriedemmtreinish: the nose vs testr thing is only a small part of that though, the real blocker is neutron21:22
mriedemsince we run with openvswitch and neutron21:22
mriedembecause you're right, i could setup tempest on a non-rhel 6 OS and point the clients at my openstack on another host, which is running rhel 621:23
mtreinishmriedem: yeah the neutron bugs are making progress. So hopefully tenant isolation with neutron will work soon21:24
mriedemmtreinish: so until devstack changes allow_tenant_isolation=true when neutron is configured, i'm following suit21:24
mtreinishthen you can move to that (although I'm sure running in parallel will find more bugs)21:24
mriedemyup21:24
mtreinishmriedem: well it was configured that way for about a week :)21:25
mriedemmtreinish: how did that go?21:25
mriedemuphill battle?21:25
mtreinishmriedem: yeah something like that: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=1c1aef0eb7796f0fe8b2502eb4aaa62369b7842a something with statistics and random sampling...21:26
mtreinishactually it didn't even last a week only 5 days...21:28
mriedemyeah, i saw that commit, it's what actually made me give up on trying to get things to work with neutron and tenant isolation on my own21:28
mtreinishmriedem: it's a fun one too: https://bugs.launchpad.net/bugs/122400121:29
mriedemah yes, i've rechecked on that several times myself21:30
mtreinishmriedem: this is the fun part: https://bugs.launchpad.net/swift/+bug/1224001/comments/1621:31
*** dkranz has quit IRC21:32
openstackrecheckopenstack/keystone change: https://review.openstack.org/49460 failed tempest with an unrecognized error21:33
*** notmyname has quit IRC21:34
*** zzs has quit IRC21:34
*** openstackgerrit has quit IRC21:34
*** sileht has quit IRC21:34
*** Anju has quit IRC21:34
*** notmyname has joined #openstack-qa21:35
*** zzs has joined #openstack-qa21:35
*** mriedem has quit IRC21:36
*** sileht has joined #openstack-qa21:38
*** fbo is now known as fbo_away21:43
*** SergeyLukjanov has quit IRC22:07
*** jlibosva has quit IRC22:11
*** mkollaro has quit IRC22:13
*** jhenner has quit IRC22:17
*** jhenner has joined #openstack-qa22:24
openstackrecheckopenstack/neutron change: https://review.openstack.org/49644 failed tempest because of: https://bugs.launchpad.net/bugs/122400122:25
*** DennyZhang has quit IRC22:31
openstackrecheckopenstack/horizon change: https://review.openstack.org/49948 failed tempest with an unrecognized error22:33
openstackrecheckopenstack/swift change: https://review.openstack.org/49739 failed tempest because of: https://bugs.launchpad.net/bugs/123543722:38
*** dims has quit IRC22:46
openstackrecheckopenstack/neutron change: https://review.openstack.org/45678 failed tempest because of: https://bugs.launchpad.net/bugs/122400122:47
*** giulivo has quit IRC22:51
*** wramthun has quit IRC23:00
*** openstackgerrit has joined #openstack-qa23:01
*** dims has joined #openstack-qa23:01
*** mlavalle has quit IRC23:16
*** Anju has joined #openstack-qa23:26
openstackgerritJeremy Stanley proposed a change to openstack-infra/devstack-gate: Conditionally override PyPI for reqs integration  https://review.openstack.org/5019823:34
*** jhenner has quit IRC23:42
*** zzs has left #openstack-qa23:44
*** bill_az_ has joined #openstack-qa23:44
openstackgerritKen'ichi Ohmichi proposed a change to openstack/tempest: Move negative action tests to right place  https://review.openstack.org/4998223:45

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