Thursday, 2014-01-02

*** rfolco has quit IRC00:23
*** adam_g has quit IRC00:24
*** adam_g has joined #openstack-qa00:24
*** adam_g has joined #openstack-qa00:24
openstackrecheckopenstack/neutron change: https://review.openstack.org/61964 failed tempest with an unrecognized error00:32
*** adam_g has quit IRC00:35
*** adam_g has joined #openstack-qa00:35
*** adam_g has joined #openstack-qa00:35
*** jhenner has joined #openstack-qa01:36
*** jhenner has quit IRC01:36
*** jhenner has joined #openstack-qa01:37
openstackgerrithuangtianhua proposed a change to openstack/tempest: add tests for security_group updating  https://review.openstack.org/5304401:57
*** jhenner has quit IRC01:58
openstackrecheckopenstack/glance change: https://review.openstack.org/64087 failed tempest with an unrecognized error02:08
openstackrecheckopenstack/neutron change: https://review.openstack.org/59146 failed tempest because of: https://bugs.launchpad.net/bugs/125610602:08
openstackrecheckopenstack/cinder change: https://review.openstack.org/64512 failed tempest because of: https://bugs.launchpad.net/bugs/125389602:25
*** zhikunliu has joined #openstack-qa02:34
openstackrecheckopenstack/swift change: https://review.openstack.org/64537 failed tempest with an unrecognized error02:40
*** adam_g has quit IRC02:48
*** adam_g has joined #openstack-qa02:48
*** adam_g has joined #openstack-qa02:48
*** zhikunliu has quit IRC02:53
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip flavor_access_add/remove related tests  https://review.openstack.org/6463402:58
openstackrecheckopenstack/nova change: https://review.openstack.org/64590 failed tempest with an unrecognized error02:58
openstackrecheckopenstack/horizon change: https://review.openstack.org/61391 failed tempest because of: https://bugs.launchpad.net/bugs/125389602:58
*** zhikunliu has joined #openstack-qa03:02
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip simple_tenant_usage related tests  https://review.openstack.org/6463703:11
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip simple_tenant_usage related tests  https://review.openstack.org/6463703:13
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip simple_tenant_usage related tests  https://review.openstack.org/6463703:16
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip flavor_access_add/remove related tests  https://review.openstack.org/6463403:17
openstackrecheckopenstack/neutron change: https://review.openstack.org/64605 failed tempest with an unrecognized error03:26
openstackrecheckopenstack/nova change: https://review.openstack.org/58450 failed tempest with an unrecognized error03:29
openstackgerritA change was merged to openstack-dev/devstack: Set default_network in tempest.conf  https://review.openstack.org/6349303:39
openstackgerritA change was merged to openstack-dev/grenade: Fix spelling mistake occured=>occurred  https://review.openstack.org/6386103:39
openstackgerritA change was merged to openstack-dev/grenade: Point readme to git.o.o instead of github  https://review.openstack.org/6386003:39
openstackrecheckopenstack/nova change: https://review.openstack.org/58444 failed tempest with an unrecognized error03:45
openstackrecheckopenstack/cinder change: https://review.openstack.org/64635 failed tempest because of: https://bugs.launchpad.net/bugs/125762603:46
openstackrecheckopenstack/nova change: https://review.openstack.org/58443 failed tempest with an unrecognized error04:05
openstackrecheckopenstack/nova change: https://review.openstack.org/58218 failed tempest with an unrecognized error04:05
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip flavor_access_add/remove related tests  https://review.openstack.org/6463405:14
openstackgerritAlex Xu proposed a change to openstack/tempest: Skip simple_tenant_usage related tests  https://review.openstack.org/6463705:15
openstackrecheckopenstack/nova change: https://review.openstack.org/59931 failed tempest because of: https://bugs.launchpad.net/bugs/125389605:16
*** ivanzhu has joined #openstack-qa05:19
*** adam_g has quit IRC05:21
*** adam_g has joined #openstack-qa05:21
*** adam_g has joined #openstack-qa05:21
*** adam_g has quit IRC05:24
*** adam_g has joined #openstack-qa05:24
*** adam_g has joined #openstack-qa05:24
*** Madan has joined #openstack-qa05:43
*** yfried has quit IRC05:46
*** psharma has joined #openstack-qa05:46
*** prekarat has joined #openstack-qa06:55
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: enable volume list tests for cinder v2 - part1  https://review.openstack.org/6440206:55
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: enable volume list tests for cinder v2 - part2  https://review.openstack.org/5973306:55
openstackrecheckopenstack/nova change: https://review.openstack.org/63607 failed tempest with an unrecognized error06:55
*** zigo has joined #openstack-qa06:56
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: enable volume list tests for cinder v2 - part2  https://review.openstack.org/5973306:58
*** prekarat has quit IRC06:59
*** yfried has joined #openstack-qa06:59
yfriedsalv-orlando: here?07:04
openstackrecheckopenstack/cinder change: https://review.openstack.org/64642 failed tempest because of: https://bugs.launchpad.net/bugs/125389607:06
*** prekarat has joined #openstack-qa07:14
*** yrabl has joined #openstack-qa07:30
openstackrecheckopenstack/tempest change: https://review.openstack.org/64402 failed tempest with an unrecognized error07:42
openstackrecheckopenstack/tempest change: https://review.openstack.org/59733 failed tempest with an unrecognized error07:42
*** nmagnezi has joined #openstack-qa07:54
*** adam_g has quit IRC08:07
*** adam_g has joined #openstack-qa08:08
*** adam_g has joined #openstack-qa08:08
*** fbo_away is now known as fbo08:12
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: enable volume list tests for cinder v2 - part2  https://review.openstack.org/5973308:14
openstackrecheckopenstack/tempest change: https://review.openstack.org/55146 failed tempest because of: https://bugs.launchpad.net/bugs/125389608:14
openstackrecheckopenstack/tempest change: https://review.openstack.org/64622 failed tempest because of: https://bugs.launchpad.net/bugs/125389608:16
openstackgerritIvan-Zhu proposed a change to openstack/tempest: port nova v2 images related tests into nova v3 part2  https://review.openstack.org/6436108:17
openstackgerritIvan-Zhu proposed a change to openstack/tempest: port nova v2 images related tests into nova v3 part1  https://review.openstack.org/6436008:17
*** vponomaryov has joined #openstack-qa08:18
*** ivanzhu has quit IRC08:22
openstackrecheckopenstack/ceilometer change: https://review.openstack.org/64025 failed tempest with an unrecognized error08:23
yfriedsalv-orlando: ping08:23
*** ivanzhu has joined #openstack-qa08:23
*** tkammer has joined #openstack-qa08:25
*** jlibosva has joined #openstack-qa08:28
*** vponomaryov has quit IRC08:30
*** tkammer has quit IRC08:36
*** vponomaryov has joined #openstack-qa08:39
openstackrecheckopenstack/glance change: https://review.openstack.org/64079 failed tempest with an unrecognized error08:49
openstackrecheckopenstack/nova change: https://review.openstack.org/59860 failed tempest because of: https://bugs.launchpad.net/bugs/125389608:50
*** tkammer has joined #openstack-qa08:51
openstackrecheckopenstack/neutron change: https://review.openstack.org/49110 failed tempest because of: https://bugs.launchpad.net/bugs/125389608:52
openstackrecheckopenstack/tempest change: https://review.openstack.org/55146 failed tempest with an unrecognized error08:59
*** jpich has joined #openstack-qa09:00
*** adam_g has quit IRC09:02
*** adam_g has joined #openstack-qa09:03
*** adam_g has joined #openstack-qa09:03
openstackrecheckopenstack/tempest change: https://review.openstack.org/64622 failed tempest because of: https://bugs.launchpad.net/bugs/125487209:04
openstackrecheckopenstack/nova change: https://review.openstack.org/57614 failed tempest with an unrecognized error09:06
enikanorov__sdague: Hi. Could you explain your comment on https://review.openstack.org/#/c/64377/ ?09:16
*** tkammer has quit IRC09:25
*** giulivo has joined #openstack-qa09:25
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: enable volume list tests for cinder v2 - part2  https://review.openstack.org/5973309:28
openstackrecheckopenstack/tempest change: https://review.openstack.org/64402 failed tempest with an unrecognized error09:38
*** psharma has quit IRC09:53
openstackrecheckopenstack/heat change: https://review.openstack.org/63839 failed tempest with an unrecognized error09:55
vponomaryovDoes anyone know about weekly qa meeting for today? On the https://wiki.openstack.org/wiki/Meetings/QATeamMeeting no info since 19 december...09:56
openstackgerritFabien Boucher proposed a change to openstack/tempest: Remove Swift container-sync test skipping  https://review.openstack.org/6454810:01
openstackrecheckopenstack/nova change: https://review.openstack.org/61462 failed tempest because of: https://bugs.launchpad.net/bugs/125389610:12
*** yrabl has quit IRC10:14
openstackrecheckopenstack/nova change: https://review.openstack.org/63826 failed tempest because of: https://bugs.launchpad.net/bugs/125389610:22
*** psharma has joined #openstack-qa10:22
openstackrecheckopenstack/nova change: https://review.openstack.org/63827 failed tempest with an unrecognized error10:23
*** tkammer has joined #openstack-qa10:26
openstackgerritYair Fried proposed a change to openstack/tempest: Increase exception log details  https://review.openstack.org/6465410:33
openstackgerritYair Fried proposed a change to openstack/tempest: Increase exception log details  https://review.openstack.org/6465410:35
openstackgerritChmouel Boudjnah proposed a change to openstack-dev/devstack: Handle more nicely when role root is already here  https://review.openstack.org/6465510:35
*** ivanzhu has quit IRC10:36
yfrieddkranz: ping10:43
salv-orlandohi yfried10:43
salv-orlandosorry for being unreachable in the past few days, I was on vacation10:44
yfriedsalv-orlando: how are you? I have some question if you have the time10:44
yfriedsalv-orlando: np - hope you enjoyed it10:44
yfriedsalv-orlando: so - about your comment here - https://review.openstack.org/#/c/63886/10:46
yfriedsalv-orlando: do you think those scenarios should retrieve the network resources created by the tenant instead of creating their own?10:47
salv-orlandoyfried - we need to talk to mtreinish for these patches. The reason is that I believe he did the tests they way they are on purpose10:47
salv-orlandoI mean always creating new stuff10:47
salv-orlandorather than re-using it.10:48
salv-orlandoIf he's happy with reusing rather than creating new items, then one could have a single tenant for all scenarios. period.10:48
salv-orlandoBut I think using a different tenant with different resources for each test was one of the goals of the introduction of "tenant isolation".10:49
salv-orlandoBut since I did not participate in this activity, we need to talk to the relevant people. I surely recall mtreinish, not sure if there are other; perhaps mlavalle as well.10:49
yfriedsalv-orlando: I think we are not talking about the same thing10:49
yfriedsalv-orlando: in "tenant isolation" each scenario has it's own tenant rather than the default "demo" tenant, right?10:50
openstackrecheckopenstack/tempest change: https://review.openstack.org/64106 failed tempest with an unrecognized error10:51
openstackrecheckopenstack/neutron change: https://review.openstack.org/61964 failed tempest with an unrecognized error10:51
openstackrecheckopenstack/tempest change: https://review.openstack.org/64283 failed tempest with an unrecognized error10:52
yfriedsalv-orlando: and the "tenant isolation" module is creating network resources (net, sub, router) for each tenant10:52
salv-orlandoyes correct.10:53
yfriedsalv-orlando: here comes my issue: Since in "regular" mode these network resources don't exist - each test create them anyway, regardless of regula/isolation mode it's in10:54
yfriedsalv-orlando: so I'm thinking:10:54
yfriedsalv-orlando: Either we get tests to use these resources when they exist, or we disable their creation10:55
yfriedsalv-orlando: what do you think?10:55
salv-orlandoyfried: help me understand. So there is a fundamental problem that the scenarios create those resources but then don't use them?10:56
yfriedsalv-orlando: that's what I'm thinking. do you know differently?10:57
salv-orlandoyfried: I assumed differently. But mine is an assumption based on how I think the code should work, not based on how the code actually works.10:57
yfriedsalv-orlando: what did you assume?10:58
salv-orlandoYou can ask for confirmation to tempest-core devs, but my expectation is that when tenant isolation is enabled a new tenant with a new set of resources is created and used for each test. When tenant isolation is disabled, pre-defined credentials and resources should always be used.10:58
salv-orlandoif the code creates resource but then just don't use them, this is incorrect.10:59
yfriedsalv-orlando: I know that these resources are created10:59
salv-orlandoyfried: I know that too for a fact! They've been troubling me a bit with parallel testing11:00
*** mkollaro has joined #openstack-qa11:00
openstackgerritRohan Kanade proposed a change to openstack/tempest: Rename instance_actions v3 plugin tests to server_actions  https://review.openstack.org/5918711:03
yfriedsalv-orlando: they are created here: https://github.com/openstack/tempest/blob/bfae59d7687bb2353b939f10be85f3c1651ccf17/tempest/common/isolated_creds.py#L19711:03
*** yrabl has joined #openstack-qa11:04
salv-orlandoyfried: I'm a bit knowledgeable with that bit. I also have a patch related on review. I'm more interesting in understanding why they're not used.11:04
salv-orlandobasically, if they're not used anyway, all the hustle and bustle tempest does with parallel testing, which brings the cpu on devstack-gate machine at 100%, could just be avoided11:05
* yfried researches network usage11:05
yfriedsalv-orlando: alright11:08
yfriedsalv-orlando: this is the only place the network is used according to my ide https://github.com/openstack/tempest/blob/bfae59d7687bb2353b939f10be85f3c1651ccf17/tempest/common/isolated_creds.py#L29511:08
openstackgerritZhi Kun Liu proposed a change to openstack/tempest: cinder v2 api tests - fix volume client  https://review.openstack.org/6466011:09
yfriedsalv-orlando: and according to the same ide - this method is never called in the tempest project11:09
openstackgerritChristian Schwede proposed a change to openstack/tempest: List Nova and Cinder extensions in debug log  https://review.openstack.org/6428311:09
salv-orlandoyfried: ok. Let's wait a bit for somebody from the tempest team to come online. If they confirm your finding then there is definitely a problem to address and we might just stop creating stuff we do not use.11:11
openstackgerritFabien Boucher proposed a change to openstack/tempest: Remove Swift container-sync test skipping  https://review.openstack.org/6454811:14
openstackrecheckopenstack/nova change: https://review.openstack.org/62043 failed tempest with an unrecognized error11:16
openstackrecheckopenstack/glance change: https://review.openstack.org/63707 failed tempest because of: https://bugs.launchpad.net/bugs/125389611:16
yfriedsalv-orlando: ok - it is created and saved but not used anywhere11:28
yfriedsalv-orlando: assuming this is the case - should we start using them or should we remove them from the code?11:29
*** jroovers has joined #openstack-qa11:30
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/60324 failed tempest because of: https://bugs.launchpad.net/bugs/125610611:32
yfriedsalv-orlando: different issue - did you have time to look at the blueprint I submitted about reports?11:33
yfriedsalv-orlando: sorry - not what I wanted to ask11:34
yfriedsalv-orlando: that's what I wanted you to look at - https://review.openstack.org/#/c/64622/ Could you please take a quick look and tell me what you think in general?11:35
*** jorisroovers has joined #openstack-qa11:39
*** jroovers has quit IRC11:41
*** tkammer has quit IRC11:50
*** tkammer has joined #openstack-qa11:50
*** zhikunliu has quit IRC11:50
yfriedsalv-orlando: still here?11:51
openstackrecheckopenstack/tempest change: https://review.openstack.org/64283 failed tempest because of: https://bugs.launchpad.net/bugs/125389611:59
openstackrecheckopenstack/tempest change: https://review.openstack.org/64654 failed tempest because of: https://bugs.launchpad.net/bugs/1257641 and https://bugs.launchpad.net/bugs/125489012:03
openstackrecheckopenstack/tempest change: https://review.openstack.org/61118 failed tempest with an unrecognized error12:03
salv-orlandoyfried - I'm back. Give me 10 minutes and I will look at your patch12:07
*** Madan has quit IRC12:29
openstackrecheckopenstack/nova change: https://review.openstack.org/63617 failed tempest with an unrecognized error12:43
*** prekarat has left #openstack-qa12:49
*** jorisroovers has quit IRC12:49
openstackrecheckopenstack/nova change: https://review.openstack.org/63615 failed tempest with an unrecognized error12:57
*** weshay has joined #openstack-qa13:01
sdaguemorning folks, happy new year13:01
*** sthaha has joined #openstack-qa13:04
*** sthaha has joined #openstack-qa13:04
*** sthaha has quit IRC13:06
openstackrecheckopenstack/nova change: https://review.openstack.org/63614 failed tempest with an unrecognized error13:10
openstackrecheckopenstack/nova change: https://review.openstack.org/63616 failed tempest because of: https://bugs.launchpad.net/bugs/125762613:10
*** rfolco has joined #openstack-qa13:13
enikanorov__sdague: good morning.13:20
enikanorov__sdague: could you please explain your comment: https://review.openstack.org/#/c/64377/13:21
sdagueso the init scripts in a neutron environment now assume a long list of config files get sent to them?13:22
sdaguewhich changes mid release?13:23
openstackrecheckopenstack/nova change: https://review.openstack.org/63618 failed tempest with an unrecognized error13:24
openstackrecheckopenstack/neutron change: https://review.openstack.org/58270 failed tempest because of: https://bugs.launchpad.net/bugs/121048313:24
yfriedsdague: is there an online qa meeting today?13:24
enikanorov__sdague: right, another conf file is being added. what cons do you see with that?13:24
sdagueyfried: no, today is skipped13:25
enikanorov__sdague: services like x-aas are going to store their configurations (including vendor-specific) in this file.13:25
sdagueyfried: we'll restart next week13:25
yfriedsdague: tnx.13:25
sdagueenikanorov__: what happens to existing functional havana installs?13:25
openstackgerritFabien Boucher proposed a change to openstack/tempest: Remove Swift container-sync test skipping  https://review.openstack.org/6454813:26
enikanorov__sdague: it's not mandatory for existing insallations13:26
enikanorov__i mean services.conf is not mandatory13:26
enikanorov__but afaik there was a consensus to store vendor-specific info in a file separate from neutron.conf13:27
*** yfried has quit IRC13:30
sdagueis there a mailing list thread on this I can go take a look at. It just seems really operator hostile to need to pass, manually 3 config files to a bunch of neutron services. If the answer is > 1 this should just be a directory which is handled automatically by neutron in startup.13:30
enikanorov__the answer is already > 113:31
enikanorov__lib/neutron passes neutron.conf and core plugin-specific conf-file13:31
enikanorov__sdague: in some cases even more than that. ml2 plugin may require conf file for each of its configured mechanism drivers13:32
sdagueso how is this expected to be managed via normal init scripts?13:33
sdagueI'd like to back up this discussion, because this seems to have gone in a very different direction than the way nova handles this successfully, which is just having optional sections in the main config file for drivers. So being different requires strong justification.13:36
sdagueespecially when that puts load on init scripts to ensure they conditionally link in all the right config parts depending on what the user wants to enable13:37
enikanorov__well, the nova's direction is 3.5K lines of config file13:38
enikanorov__i guess that is what neutron tried to avoid13:39
*** anand has joined #openstack-qa13:39
giulivohappy new year there sdague :)13:39
anandany docs for rdo storage part?13:40
giulivoanand, I think you should try on #rdo rather than here13:41
anandokay. may I ask for what this channel will be useful?13:41
giulivoanand, I don't think there is a strict ruling but this channel is more about the QA processes and projects; I thought you had a specific question for rdo/storage so #rdo seemed more appropriate13:44
*** mriedem has joined #openstack-qa13:44
sdagueenikanorov__: yeh, but a bunch of config files, which have to be manually passed to a server, is something *no* other server does.13:44
sdagueI could see an apache style model with includes being managed in config13:45
enikanorov__i'm not sure; why are you saying "manually"?13:45
anandgiulivo, okay thank you so much.13:45
sdagueenikanorov__: you are passing them to the binary13:45
enikanorov__sdague: right. either by init script or devstack does it13:45
enikanorov__what does mean "manually" in this case?13:46
sdagueenikanorov__: but they are conditionally sent there13:46
sdague--config-file /$Q_PLUGIN_CONF_FILE13:46
enikanorov__in fact I'd made it a mandatory file for the future release13:46
sdaguethis is backing up the whole conversation, because we should have caught it earlier13:47
enikanorov__does the number of config files matter? neutron-server and agents care about config options13:47
enikanorov__which could be gathered from 1 file or from 10 files13:47
sdagueenikanorov__: if it doesn't matter, put them all into one config file13:48
openstackgerritThierry Carrez proposed a change to openstack-infra/devstack-gate: Add oslo.rootwrap to the devstack gate  https://review.openstack.org/6467513:48
enikanorov__sdague: well, folks found that putting them in a separate file is more convenient13:48
enikanorov__and that was the whole point13:48
openstackrecheckopenstack/neutron change: https://review.openstack.org/64613 failed tempest with an unrecognized error13:48
sdagueI think it does matter, because show examples of any server software on your linux environment that requires passing multiple config files to the server process13:49
sdagueenikanorov__: then make neutron do all that intrinsically, so it only starts with a neutron.conf (which is a default), and the rest isn't something that needs to be managed on the command line13:49
enikanorov__ok, you're implying setting conf dir in main config file13:50
sdaguesure13:50
sdaguelike an apache style13:50
sdagueand that I'd be fine with, or some include logic13:50
sdaguebut if config-file is being passed more than once to a binary, I really think we're doing this wrong.13:51
enikanorov__that may make sense, but what is the problem of passing additional conf file to neutron server in devstack?13:51
enikanorov__while conf-directory not there13:51
sdaguebecause this patch takes us in the wrong direction, so I want the underlying issue fixed first13:52
sdaguewhich also provides some urgency to it, as this feature won't land until that gets sorted13:52
enikanorov__ok. i'll bring this up on the next neutron meeting13:52
*** timello_ is now known as timello13:58
sdaguesure, or kick of an ML thread on it to deal with it sooner. Because it seems like there also might need to be some oslo config interaction here as well. I don't know that they support an include syntax at this point.14:01
openstackgerritThierry Carrez proposed a change to openstack-dev/devstack: Add oslo.rootwrap to devstack gate  https://review.openstack.org/6467914:08
*** anand has quit IRC14:10
openstackrecheckopenstack/nova change: https://review.openstack.org/57614 failed tempest with an unrecognized error14:10
*** psharma has quit IRC14:10
*** jasondotstar has joined #openstack-qa14:27
*** malini_afk is now known as malini14:34
*** mkollaro has quit IRC14:40
*** ruhe has joined #openstack-qa14:41
*** Anju has quit IRC14:42
*** mkollaro has joined #openstack-qa14:44
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Remove test_auth_token.py  https://review.openstack.org/6119214:44
*** markmcclain has quit IRC14:54
*** ruhe has quit IRC14:55
*** Anju has joined #openstack-qa15:03
*** yfried has joined #openstack-qa15:04
yfriedsalv-orlando: did you manage to take a look at my patch?15:07
salv-orlandoyfried: yes, commented it on it and will do a thorough review in the next few hours. I agree on the approach - makes sense to me.15:07
yfriedsalv-orlando: when you're done, please ping me, if I'm still awake I would like to discuss it. This is a stub in the dark for me. It seemed easy on paper but having some issues with the actual implementation15:09
openstackrecheckopenstack/nova change: https://review.openstack.org/61977 failed tempest with an unrecognized error15:13
*** croberts has joined #openstack-qa15:17
*** mkollaro has quit IRC15:19
yfrieddkranz: sdague: https://review.openstack.org/#/c/64622/ feels to me like a major change to scenario tests. I would appreciate your comments on the general idea (and later the implementation) when you can. It is rather time consuming and I would like some core members' point of view before committing more time and work in this direction15:24
openstackrecheckopenstack/horizon change: https://review.openstack.org/63403 failed tempest with an unrecognized error15:26
*** markmcclain has joined #openstack-qa15:26
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/63003 failed tempest with an unrecognized error15:26
*** nmagnezi has quit IRC15:29
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Add a discoverable_apis option for swift  https://review.openstack.org/6206315:31
openstackgerritMalini Kamalambal proposed a change to openstack/tempest: Adds basic Marconi test  https://review.openstack.org/6344915:31
*** bdperkin has quit IRC15:34
*** bdperkin has joined #openstack-qa15:34
openstackrecheckopenstack/horizon change: https://review.openstack.org/64272 failed tempest because of: https://bugs.launchpad.net/bugs/125762615:35
yfrieddkranz: are you back from vacation?15:37
dkranzyfried: Yes, such that it was15:38
yfrieddkranz: great to have you back :) can you spare some time to look at the patch. It's the work we discussed - simulating fixtures15:39
dkranzyfried: Yes, but maybe not until tomorrow. I am trying to push a negative test framework WIP today.15:40
yfrieddkranz: is that the automatically generated negative tests?15:40
dkranzyfried: Yes15:40
yfrieddkranz: sounds intersting - can I take a look?15:41
yfriedmtreinish: ping15:41
dkranzyfried: Yes, I need to actually run it before pushing it up.15:41
yfrieddkranz: :(15:41
sdagueyfried: so I'll put comments in the review as well15:41
dkranzyfried: I am writing code for about another hour I think15:42
dkranzyfried: But then need to debug15:42
mtreinishyfried: what's up?15:42
sdaguehowever, instead of doing all the logic with dirty validation and class level variables15:42
sdaguewhy not just use setUp15:42
sdagueand only build the resources there15:42
sdaguesetUpClass is just an optimization, but in this case I don't think we need or want that optimization, especially when the logic to keep it gets so complicated15:42
yfrieddkranz: too bad. I was hoping to have a look. Purely out of interest. I don't think I can contribute much to this. Please tag me on the patch when you do push it.15:44
mtreinishays vehicle information screens (performance gauges, climate controls, battery voltage, check engine codes and more) with compatible Kenwood radios.* Basic radio replacement features also available with other radios makes.15:44
dkranzyfried: ok. What is too bad?15:44
mtreinishoops finger slipped sorry about that15:44
mtreinishdon't know what that was in my middle mouse paste buffer though...15:44
yfrieddkranz: too bad that I can't look at it today15:44
yfriedsdague: do you mean that I shouldn't declare the dirty flag in setUpClass? how else can I share the state between test_case instances?15:46
sdagueso you shouldn't be sharing state between test case instances15:48
yfriedmtreinish: salv-orlando and I had a discussion earlier about network resources in isolated_creds, and we were hoping for your input. Did you happen to see it? Would you like me to sum it up here?15:48
sdaguebecause their execution order is not guarunteed15:48
mtreinishyfried: let me read the backlog one sec15:48
yfriedsdague: but I need the "expensive" resources to be shared unless test_case fails15:48
sdaguehow expensive are they really?15:49
sdagueI would rather see the non optimized version, then decide if it makes the test too long15:50
yfriedsdague: boot a VM for every testcase???15:52
sdaguethat's only 7 seconds15:52
salv-orlandoyfried: thanks. Let me scroll back on catch up on IRC15:52
yfriedsdague: you must have a state of the art setup. i can never get a pingable VM in 7 sec15:53
openstackrecheckopenstack/tempest change: https://review.openstack.org/62063 failed tempest with an unrecognized error15:54
salv-orlandoyfried: sorry - I thought you had already a chat with mtreinish. I seem to no be able to read anymore after the break.15:54
mtreinishyfried: so if a resource is needed for a test case but right now we're only creating it with isolated_creds then the test should explicitly create the resource needed15:54
sdagueanyway, we're actually trying to evolve away from setupClass, so can we see what this looks like without all the complicated class caching, and see what the run time in the gate is15:54
mtreinishtenant isolation is there to provide isolation between tests running in parallel so they don't conflict with each other15:54
yfriedsalv-orlando: I am trying to get mtreinish into our chat. you are already up to speed15:55
mtreinishbut if you need a network for the test you should create it15:55
sdagueotherwise, if these are coupled, they should remain coupled in a single test, and just check point sanity more often15:55
mtreinishyfried: especially for scenario tests, you want to be testing the whole scenario which includes resource creation. I think a better solution would be to disable the network isolation for scenarios if you're trying to avoid duplicated effort15:58
mtreinishI think salv-orlando (or someone else) had a patch doing that15:58
yfriedsdague: I will push another version without shared resources. Would you like it in a new patch, or on the same patch? Also - if a test case is skipped - can we avoide setup/teardown? Currently it seems like skip happens after setup15:58
salv-orlandomtreinish: I just has a patch for not creating routers unless needed15:59
salv-orlandoI think yfried instead has a patch for reusing, rather than creating network resources.15:59
openstackrecheckopenstack/neutron change: https://review.openstack.org/62687 failed tempest with an unrecognized error16:00
salv-orlandoI am not sure if this is inline with the aim of tenant isolation, but it seems yfried observed that the resources creates by scenario tests are not used anyway - the 'default' credentials and resources are always used16:00
salv-orlandoyfried: please correct me if I wrote anything wrong.16:00
sdagueyfried: so that's a good point on per test script. In that case moving setup into something which is called in the tests, vs using setup at the test level would actually be better16:00
sdaguethen you can also use addCleanup instead of teardown, which will always get called16:01
mtreinishsalv-orlando: yeah I was looking at it, it uses the isolated resources if they're available. But, I'm saying the test should be explicit if it's testing the neutron resources.16:01
mtreinishsalv-orlando: things created by tenant isolation really weren't meant to be used for testing directly. It's more a way to enabling tests. If a resource needs to be created for a test, the test should do that.16:02
yfriedsdague: salv-orlando: mtreinish I'm having trouble taking part in 2 chats at once. my fault for starting them both. Can I please get one of you to hold this for a few minutes?16:03
mtreinishso that the api semantics can be verified explicitly16:03
salv-orlandoyfried: sure I'll be around for a while.16:03
sdagueyfried: sure, I can hold16:03
sdagueactually, I just put my comments in the review, we can take it there whenever is convenient for you16:04
yfriedsdague: then why don't you join the isolated_cred issue for now?16:04
yfriedsdague: then I will read them and get back to you shortly. Thanks for understanding16:05
yfriedsalv-orlando: mtreinish: I will recaup:16:06
*** mkollaro has joined #openstack-qa16:09
yfriediso_creds creates (upon first credential request) net_resources (net, subnet, router) for each tenant. As far as I can see, these resources are NEVER used. salv-orlando also observed that they put stress on the gate performance. We can easily drop them and current testing won't be affected. Did I miss anything?16:09
yfriedsalv-orlando: mtreinish ^16:11
salv-orlandoone thing to mention is that the "stress" was probably intentional.16:11
yfriedsalv-orlando: why intentional?16:11
mtreinishyes the stress was somewhat intentional (after we found that it was stressing things)16:11
*** jgrimm has joined #openstack-qa16:12
mtreinishyfried: if the extra resource creation is interfering with a test I'd say instead of just using the resources created by the isolated creds code, add a flag to disable there creation16:12
mtreinishif it's not getting in the way I don't see any harm in leaving things as they are16:13
mtreinishjust for the16:13
yfriedmtreinish: salv-orlando pointed out that a standard cloud usage requires each tenant to take create its own net_resources, and thus we are simulating this16:13
mtreinish"stess effect" it's nice side effect to make sure things can handle a reasonable load16:14
yfriedmtreinish: ok. so let me propose this:16:14
salv-orlandoperhaps we can just make sure the scenario test uses the resource being created16:15
salv-orlandoI honestly thought this was how it worked16:15
mtreinishsalv-orlando: there are 2 issues with that. 1. the resources aren't always created. (A non default config flag must be set) 2. You aren't explicitly testing the create operations anymore which I thought was part of the test scenario16:17
yfriedmtreinish: we allow each test the choice of using the resources created, or creating its own (in case net-creation is part of the test). However, if the test creates its own tenant network, the previous net_resources will be disabled at test-setup and not created at all16:17
openstackrecheckopenstack/tempest change: https://review.openstack.org/61037 failed tempest with an unrecognized error16:18
mtreinishyfried: yes that's what I'm saying we should do16:18
yfriedmtreinish: salv-orlando: I would also like to point out that using existing net_resources causes substantial difference between "default" and "isolated_creds" mode, and this should be addressed by the tests.16:19
mtreinishyfried: that is 1 of the reasons the network scenario tests create resources explicitly16:20
*** markmcclain has quit IRC16:21
salv-orlandocool. So perhaps we can have a first step in which a test case can tell the credentials manager whether it should create or not network resources?16:22
yfriedmtreinish: AFAIK the 1st scenario net test was created before iso_creds was introduced. The 2nd was written by me, and I didn't know this option existed.16:22
yfriedsalv-orlando: +116:22
salv-orlandoand then how can we work out the reuse/vs create thing? I'm not sure I understand how can we reuse net resource when tenant isolation is enabled. Every test will run with a different tenant...16:23
mtreinishyfried: it was, but when I added isolated creds to the scenario tests I considered all of this.16:23
mtreinishsalv-orlando: it's more if the test doesn't specifically need to test any of the net resources created by tenant isolation then just use those resources16:24
openstackrecheckopenstack/horizon change: https://review.openstack.org/64272 failed tempest because of: https://bugs.launchpad.net/bugs/125389616:24
mtreinishbut if it needs to test something created by it, then the test has to create it16:25
yfriedsalv-orlando: I don't see your concern. The point is to use already created net_resources. Not to share them with other tests16:25
*** jlibosva has quit IRC16:25
salv-orlandomtreinish, fried: forgive my dumbness. I don't know where these network resources are created…16:26
mtreinishsalv-orlando: in the scenario tests or the isolated creds code?16:27
salv-orlandomtreinish: meh just ignore me then. I was moaning because I thought you wanted to create them once and then reuse for several scenarios16:28
*** andreaf has joined #openstack-qa16:28
salv-orlandosorry for wasting your time16:28
*** jlibosva has joined #openstack-qa16:28
*** yrabl has quit IRC16:29
*** mlavalle has joined #openstack-qa16:29
mtreinishsalv-orlando: oh, ok. yeah, that's not going to happen.16:29
yfriedsalv-orlando: they are created for each tenant. each isolated "domain" has admin, primary, and sometimes alt tenant16:29
yfriedsalv-orlando: AFAIK "domain" is a Class.16:30
salv-orlandook so there is nothing really to discuss beyond what we previously agreed16:30
*** yfried is now known as yfried_brb16:30
yfried_brbsalv-orlando: mtreinish need to step away for 2 min16:31
*** tkammer has quit IRC16:37
*** yfried_brb is now known as yfried16:42
openstackrecheckopenstack/keystone change: https://review.openstack.org/64589 failed tempest because of: https://bugs.launchpad.net/bugs/125762616:46
yfriedsalv-orlando: I'm back to wonder how we know if a test should reuse the net_resources or not. I know about my the ones I wrote. but what of the others? We need a list of all the tests that create network resources. What about API tests - they don't use network at all (except for network api that create their own resources), so the only serve to stress the gate16:46
salv-orlandoyfried: That isn't easy to know; some API tests use network resource even if they're not network test - think about the tests that create an instance16:48
salv-orlandoBut you're right that some do not need network resources at all.16:48
salv-orlandoFinding all of them in a single patch is probably too cumbersome.16:48
salv-orlandoAnd on the other hand, let's say that they add some "healthy" stress on Neutron as mtreinish pointed out.16:49
yfriedsalv-orlando: those that create the instance should definitely reuse resources16:49
salv-orlandoI've just a patch for not creating the routers - as actually in many cases you do not need them, and setting up a router on the l3 agent takes time for ip and ovs commands16:49
yfriedsalv-orlando: we should combine our patches16:50
salv-orlandoI've seen yours and mine and they can stay separated.16:50
salv-orlandono conflict. Reviewers also tend to prefer smaller patches.16:50
salv-orlandobut I don't have strong opinions (well, I never have :))16:51
yfriedsalv-orlando: just because I didn't know about yours. But the should be applied to the same place in the code, I think.16:52
yfriedsalv-orlando: can you post your patch here? I haven't seen it16:52
salv-orlandohttps://review.openstack.org/#/c/62962/16:53
openstackrecheckopenstack/keystone change: https://review.openstack.org/59526 failed tempest because of: https://bugs.launchpad.net/bugs/124906516:55
*** vponomaryov has quit IRC17:00
*** jasondotstar has quit IRC17:05
sdaguesalv-orlando: so I have another idea about an approach on that last patch, which would be a little more extensive, but I think might serve us better. What if we annotated the classes that have tests that need a router with some attribute, and have the isolated creds call look at that instead.17:07
*** zz_ajo is now known as ajo17:07
sdaguehaving it come as a parameter seems kind of odd17:07
*** jasondotstar has joined #openstack-qa17:12
*** ruhe has joined #openstack-qa17:13
openstackrecheckopenstack/python-novaclient change: https://review.openstack.org/59861 failed tempest because of: https://bugs.launchpad.net/bugs/125762617:16
*** jaypipes has joined #openstack-qa17:18
*** ChanServ sets mode: +o jaypipes17:18
*** jaypipes has quit IRC17:19
salv-orlandosdague: that is functionally equivalent to me17:20
salv-orlandoI can do that17:20
sdaguesalv-orlando: cool. I'd also like the default to be not creating the resource. Assume we only need the attribute if we are creating it17:21
sdaguebecause reverse logic is harder for people to keep straight in their head on reviewing17:21
salv-orlandosdague: I agree with you - I did my patch the other way around because I'm lazy and it led to a shorter diff17:21
sdague:)17:21
sdaguethat's fair17:21
salv-orlandobut yes, I can do as you suggest17:22
sdaguecool, thanks17:22
sdaguethere was another patch of yours that I had a question with a -1 on. https://review.openstack.org/#/c/64217/17:22
sdaguebecause I don't actually understand how we are hitting the issue that is trying to prevent.17:23
*** krtaylor has quit IRC17:24
*** markmcclain has joined #openstack-qa17:24
*** rwsu has joined #openstack-qa17:27
*** ruhe has quit IRC17:28
yfriedsalv-orlando: great. so I will hold my patch until you push yours and work according to it.17:31
*** mlavalle has quit IRC17:32
yfriedsalv-orlando: mtreinish while on the subject - can we take a look at the methods used to handle isolated_creds? we have a different method for every resource and tenant, so that's something like get_(router, creds, net, subnet,...)x(admin,primary,alt)17:32
*** jpich has quit IRC17:33
dansmithI'm sure I'm being stupid, but how do I get tempest to run with tox and only run one test? seems like specifying the whole class path or a regex (like nova) doesn't work17:34
yfriedmtreinish: seems like a better way would be to define a tenant_object and have it handle its resources17:37
yfriedsdague: what do you think ^17:37
russellbdansmith: compare tox.ini ... should have something to pass through args you provide17:38
sdaguedansmith: the class path should work17:38
dansmithrussellb: yeah, seems like it's there, that's the thing17:39
*** DennyZhang has joined #openstack-qa17:39
russellbthen i've got nothin17:39
dansmithsdague: nose-style with a colon or testr style ?17:39
sdaguetestr style17:39
dansmithsdague: because regardless, it just runs everything, instead of not matching anything17:39
sdagueok, let me go test17:39
sdaguewe did do some fancy loader logic recently, maybe we broke args somewhere17:40
dansmithsdague: I'm using smoke-serial by the way, but it looks like it's the same as full17:40
*** jaypipes has joined #openstack-qa17:40
*** ChanServ sets mode: +o jaypipes17:40
*** jlibosva has quit IRC17:41
sdaguedansmith: ok, I'm spinning up a rax devstack node, will poke there17:41
mtreinishdansmith: the issue is the regex on the tox jobs17:41
*** jlibosva has joined #openstack-qa17:41
dansmithmtreinish: use more words17:41
mtreinishdansmith: testr uses or's between multiple regexes on the cli17:42
mtreinishso when you add a more selective regex to tox and there is already a regex specified17:42
mtreinishyours doesn't do anything17:42
dansmithah17:43
dansmithis there a tox job I should use that doesn't specify a regex?17:43
dansmithfull does17:43
mtreinishuse all17:43
* dansmith tries17:43
dansmithmtreinish: nice, it works, thanks :)17:46
sdaguemtreinish: given that we are passing that through the helper script all the time, we could always drop the default regex if arg #2 doesn't start with --17:46
mtreinishsdague: probably, I just get a bit twitchy touching those helper scripts17:47
mtreinishfor something that simple I sure have caused a lot of problems with them17:47
sdagueheh17:48
sdagueyeh, let me put it on my queue.17:48
*** harlowja has joined #openstack-qa17:49
*** prekarat has joined #openstack-qa17:57
*** DennyZhang has quit IRC17:59
*** mlavalle has joined #openstack-qa17:59
sdagueyfried: sorry, back to your question, an tenant_object model would be a good move forward as well. Create an object responsible for create and cleanup.17:59
yfriedsdague: what do you mean?18:03
sdague<yfried> mtreinish: seems like a better way would be to define a tenant_object and have it handle its resources18:04
sdagueyfried: +118:04
yfriedsdague: I tried to do this locally for my cross_tenant scenario. if this  would be done globally, that would be great. we could have the object handle either the default tenant, or the isolated_creds on runtime18:06
openstackgerritA change was merged to openstack-dev/devstack: Migrating trove to entry points  https://review.openstack.org/6445718:07
openstackgerritA change was merged to openstack-dev/devstack: Change the libvirtd log level to DEBUG  https://review.openstack.org/6399218:08
openstackgerritA change was merged to openstack-dev/devstack: Correct glance db_sync command  https://review.openstack.org/6360518:08
openstackgerritA change was merged to openstack-dev/devstack: XenAPI: Fix bug with Xen ext4-using guests  https://review.openstack.org/6379518:08
sdagueyfried: agreed18:13
yfriedsdague: since I'm new - how do we translate these discussions to patches? The tenant object seems beyond my current abilities, but I would like to this added, and not just in the channel log18:16
sdagueyfried: so I think this should probably become a blueprint18:16
sdaguethat would be the right way to record it18:16
openstackgerritSteven Hardy proposed a change to openstack/tempest: Add basic read-only tests for heat cli  https://review.openstack.org/6470718:17
yfriedsdague: So I will create an initial one.18:17
sdagueyfried: great, thank you18:17
yfriedsdague: keep in mind that it will probably require massive edit from you :)18:18
sdagueyfried: no problem, but it's a start :)18:18
sdagueand also does the right thing of making sure we don't completely forget it18:19
openstackgerritA change was merged to openstack/tempest: keystone OS-TRUST extension, test list operations  https://review.openstack.org/6117618:19
*** markmcclain has quit IRC18:21
yfriedsdague: https://blueprints.launchpad.net/tempest/+spec/tenant-menager please review and add relevant people18:33
*** mlavalle has quit IRC18:35
*** markmcclain has joined #openstack-qa18:37
*** jroovers has joined #openstack-qa18:41
*** jroovers has quit IRC18:48
*** sileht has quit IRC18:59
*** sc68cal has quit IRC18:59
*** markmcclain has quit IRC19:04
openstackrecheckopenstack/keystone change: https://review.openstack.org/59526 failed tempest because of: https://bugs.launchpad.net/bugs/125489019:04
*** markmcclain has joined #openstack-qa19:05
*** sileht has joined #openstack-qa19:05
*** sc68cal has joined #openstack-qa19:05
openstackrecheckopenstack/tempest change: https://review.openstack.org/61175 failed tempest with an unrecognized error19:13
*** markmcclain has quit IRC19:15
openstackrecheckopenstack/neutron change: https://review.openstack.org/63918 failed tempest with an unrecognized error19:17
*** markmcclain has joined #openstack-qa19:17
*** mlavalle has joined #openstack-qa19:18
*** krtaylor has joined #openstack-qa19:18
mtreinishsdague: how should we handle this? https://review.openstack.org/#/c/63062/519:27
mtreinishI'm inclined to say it should just be the newer versions19:27
sdagueyeh, I agree19:36
sdaguealso, the previous behavior didn't support < 1.9 anyway19:37
mtreinishwell there is that too :)19:41
*** jlibosva has quit IRC19:45
*** markmcclain has quit IRC19:49
*** markmcclain has joined #openstack-qa19:53
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Add a discoverable_apis option for swift  https://review.openstack.org/6206319:53
*** jgrimm has quit IRC20:00
openstackrecheckopenstack/keystone change: https://review.openstack.org/59526 failed tempest with an unrecognized error20:02
openstackgerritandrea-frittoli proposed a change to openstack/tempest: Input scenario capability for tempest  https://review.openstack.org/6043420:08
*** markmcclain has quit IRC20:09
*** markmcclain has joined #openstack-qa20:11
openstackrecheckopenstack/tempest change: https://review.openstack.org/60434 failed tempest with an unrecognized error20:27
openstackrecheckopenstack-dev/devstack change: https://review.openstack.org/61854 failed tempest with an unrecognized error20:29
*** ruhe has joined #openstack-qa20:38
*** fbo is now known as fbo_away20:47
*** malini is now known as malini_afk20:50
openstackrecheckopenstack/tempest change: https://review.openstack.org/62063 failed tempest with an unrecognized error20:54
*** croberts has quit IRC20:59
openstackgerritMatthew Treinish proposed a change to openstack/tempest: Add a discoverable_apis option for swift  https://review.openstack.org/6206321:01
*** croberts has joined #openstack-qa21:11
*** yfried has quit IRC21:13
*** syerrapragada1 has quit IRC21:19
openstackrecheckopenstack/heat change: https://review.openstack.org/64720 failed tempest with an unrecognized error21:25
openstackrecheckopenstack/neutron change: https://review.openstack.org/59787 failed tempest because of: https://bugs.launchpad.net/bugs/1253896 and https://bugs.launchpad.net/bugs/124425521:26
*** croberts has quit IRC21:27
openstackgerritA change was merged to openstack/tempest: Add test for HEAD queries on Swift tempurl MW  https://review.openstack.org/6446721:39
*** ruhe has quit IRC21:40
openstackrecheckopenstack/neutron change: https://review.openstack.org/64205 failed tempest because of: https://bugs.launchpad.net/bugs/121048321:42
*** croberts has joined #openstack-qa21:45
openstackgerritDavid Kranz proposed a change to openstack/tempest: First draft of negative test generation  https://review.openstack.org/6473321:51
openstackrecheckopenstack/python-heatclient change: https://review.openstack.org/62925 failed tempest with an unrecognized error22:01
*** jasondotstar has quit IRC22:02
*** seiflotfy_ has quit IRC22:19
openstackgerritandrea-frittoli proposed a change to openstack/tempest: Input scenario capability for tempest  https://review.openstack.org/6043422:21
*** seiflotfy_ has joined #openstack-qa22:22
openstackgerritandrea-frittoli proposed a change to openstack/tempest: Input scenario capability for tempest  https://review.openstack.org/6043422:26
*** croberts has quit IRC22:27
sdagueianw, dkranz: when you guys get some time - http://lists.openstack.org/pipermail/openstack-dev/2014-January/023321.html22:27
dkranzsdague: I think ianw will look at this.22:28
sdaguesure, I just don't know how irc active he is, so I figured I'd poke you to poke him if he didn't see it22:29
*** markmcclain has quit IRC22:32
*** rwsu has quit IRC22:33
openstackrecheckopenstack/nova change: https://review.openstack.org/39998 failed tempest because of: https://bugs.launchpad.net/bugs/125489022:33
dkranzsdague, mtreinish , cyeoh : It would be nice to finally get this in (nova v3 item) https://review.openstack.org/#/c/60776/22:33
dkranzsdague: Will do22:33
*** mkoderer_ has quit IRC22:33
sdaguedkranz: +A22:34
dkranzsdague: Thanks22:34
*** mkoderer_ has joined #openstack-qa22:36
*** rwsu has joined #openstack-qa22:40
*** seiflotfy_ has quit IRC22:41
*** mkoderer_ has quit IRC22:48
*** weshay has quit IRC22:49
openstackrecheckopenstack/neutron change: https://review.openstack.org/64724 failed tempest with an unrecognized error22:51
*** mkoderer_ has joined #openstack-qa22:52
*** rwsu has quit IRC22:59
*** mkoderer_ has quit IRC23:00
anteayanormally I would ping jog0 about this but I don't see him around23:02
*** mkoderer_ has joined #openstack-qa23:03
anteayaI am aware that https://bugs.launchpad.net/tempest/+bug/1253896 is a top bug in elastci-recheck, salv-orlando has asked if the elastic-recheck stats for this are accurate in this latest comment23:03
anteayais there anyone who is able to offer an opinion, and perhaps also update the bug report?23:03
openstackgerritA change was merged to openstack/tempest: Kill finally, use addCleanUp  https://review.openstack.org/6265923:03
openstackrecheckopenstack/neutron change: https://review.openstack.org/58017 failed tempest because of: https://bugs.launchpad.net/bugs/125389623:04
clarkbanteaya: it is easy to do a check by hand, run the elasticsearch query for the bug but add 'AND NOT build_queue:"experimental"23:05
anteayaI'll try that, thanks clarkb23:05
clarkbanteaya: 83 hits the last 7 days23:05
anteayathanks23:05
anteayaairport wifi might not have given me that23:06
anteayastill waiting23:08
openstackgerritA change was merged to openstack/tempest: keystone OS-TRUST extension, test with expiry  https://review.openstack.org/6117523:08
*** nsaje has quit IRC23:09
openstackrecheckopenstack/tempest change: https://review.openstack.org/60434 failed tempest with an unrecognized error23:09
*** nsaje has joined #openstack-qa23:12
*** rwsu has joined #openstack-qa23:12
*** mkollaro has quit IRC23:20
*** mlavalle has quit IRC23:33
openstackrecheckopenstack/python-neutronclient change: https://review.openstack.org/62130 failed tempest with an unrecognized error23:33
*** sthaha has joined #openstack-qa23:35
*** sthaha has joined #openstack-qa23:35
openstackrecheckopenstack/nova change: https://review.openstack.org/60719 failed tempest because of: https://bugs.launchpad.net/bugs/1250168 and https://bugs.launchpad.net/bugs/125489023:36

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