*** serverascode has quit IRC | 01:32 | |
*** davidlenwell has quit IRC | 01:33 | |
*** eglute has quit IRC | 01:33 | |
*** davidlenwell has joined #refstack | 01:34 | |
*** ChanServ sets mode: +o davidlenwell | 01:34 | |
*** serverascode has joined #refstack | 01:37 | |
*** eglute has joined #refstack | 01:38 | |
*** davidlenwell_ has joined #refstack | 07:10 | |
*** davidlenwell has quit IRC | 07:15 | |
*** openstackgerrit has quit IRC | 10:16 | |
*** openstackgerrit has joined #refstack | 10:17 | |
*** esker has joined #refstack | 10:18 | |
*** esker has quit IRC | 10:28 | |
*** openstack has joined #refstack | 12:50 | |
*** edmondsw has joined #refstack | 13:28 | |
*** esker has joined #refstack | 14:33 | |
*** esker has quit IRC | 14:38 | |
*** resker has joined #refstack | 14:42 | |
*** resker has quit IRC | 14:43 | |
*** esker has joined #refstack | 14:43 | |
*** esker has quit IRC | 14:54 | |
*** sslypushenko has quit IRC | 16:52 | |
*** sslypushenko has joined #refstack | 16:52 | |
*** davidlenwell_ is now known as davidlenwell | 17:15 | |
*** ChanServ sets mode: +o davidlenwell | 17:15 | |
*** dwalleck has joined #refstack | 17:51 | |
*** catherineD has joined #refstack | 18:10 | |
*** pvaneck has joined #refstack | 18:45 | |
hogepodge | catherineD: I wasn't able to get tempest locking accounts to work with the installed version of tempest. When I use master the failures I was hitting went away. | 20:01 |
---|---|---|
catherineD | hogepodge: what is the error? | 20:01 |
hogepodge | catherineD: no configured accounts | 20:01 |
hogepodge | when I'm using accounts.yaml | 20:01 |
hogepodge | catherineD: it could be user error, though. | 20:01 |
hogepodge | catherineD: another problem I hit is resource starvation after a number of runs. | 20:02 |
mtreinish | hogepodge: the configuration shouldn't have changed | 20:02 |
mtreinish | hogepodge: are we leaking accounts? | 20:02 |
hogepodge | tempest doesn't clean up after itself, and I think we should provide or run cleanup scripts after refstack-client runs to delete ports, security groups, vms, volumes, and so on. | 20:02 |
catherineD | have notice something last night when I working with this bug https://bugs.launchpad.net/refstack/+bug/1516458 | 20:03 |
openstack | Launchpad bug 1516458 in refstack "refstack-client test failure with test-list option" [Undecided,New] - Assigned to Catherine Diep (cdiep) | 20:03 |
hogepodge | mtreinish: refstack-client installs an older version of tempest. I know that I get the most success in running from master | 20:03 |
mtreinish | hogepodge: tempest should cleanup anything it makes... :( | 20:03 |
mtreinish | oh, ok | 20:03 |
hogepodge | mtreinish: I agree, I was running into the most trouble with security groups and ports | 20:03 |
mtreinish | bah, network tests | 20:04 |
catherineD | we have run many tests with the current installed tempest version with locking accounts ... | 20:04 |
hogepodge | catherineD: I may have configured it wrong | 20:04 |
hogepodge | mtreinish: I'm also wondering if we might be able to expand the configuration guide to include more networking information. I was doing a lot of "search" configuration figuring out how to get a floating ip installation tested. I worked it out, but I am sure that some config options are just silly for what I actually wanted (there was a mix of cloud misconfiguration and just figuring stuff on the tempest side and fi | 20:06 |
hogepodge | nding and cleaning up resource leaks) | 20:06 |
catherineD | one thing I notice is that "testr list-tests" in the past all we need is to have a tempest.conf file in the ./etc directory the tempest.conf could be a copy of the tempest..conf.sample.... but with the recent run I need to use a valid tempest.conf not just a copy of the sample | 20:06 |
catherineD | that is with the same tempest version | 20:06 |
mtreinish | hogepodge: fwiw, there was a patch at one point to fix the cleanup script packaged in tempest to handle test accounts properly | 20:06 |
mtreinish | although I think it's out of date and never landed | 20:07 |
mtreinish | catherineD: you shouldnt need a tempest.conf at all | 20:07 |
catherineD | mtreinish: yup .. | 20:07 |
catherineD | but not sure why I needed it now ... | 20:07 |
hogepodge | mtreinish: you can see what I'm configuring here https://github.com/hogepodge/defcore-tools/blob/hogepodge/puppetlabs-openstack/ansible/playbooks/cloudconfig.yml and here https://github.com/hogepodge/defcore-tools/blob/hogepodge/puppetlabs-openstack/ansible/playbooks/templates/tempest.conf.j2 (I set run_validation to true, but haven't pushed that change yet) | 20:07 |
mtreinish | there is 1 test module that requires a tempest.conf at import, which is a longstanding bug (but without a proposed workaround) that can cause errors during import if the conf file is invalid | 20:08 |
hogepodge | mtreinish: I'm using accounts.yaml, so the tenants/users aren't destroyed after failed runs. | 20:08 |
mtreinish | but that's been there since like grizzly | 20:08 |
hogepodge | mtreinish: I'm trying to replicate testing against public clouds | 20:08 |
hogepodge | mtreinish: I was definitely leaking security groups and network ports | 20:08 |
mtreinish | hogepodge: you're using ansible! | 20:08 |
catherineD | here is a bug that I open for refstack to deal with the situation where testr list-tests need a tempest.conf https://bugs.launchpad.net/refstack/+bug/1516458 | 20:08 |
openstack | Launchpad bug 1516458 in refstack "refstack-client test failure with test-list option" [Undecided,New] - Assigned to Catherine Diep (cdiep) | 20:08 |
mtreinish | catherineD: why is that a refstack bug? | 20:09 |
hogepodge | mtreinish: and puppet. https://github.com/hogepodge/puppetlabs-openstack | 20:09 |
hogepodge | mtreinish: whatever gets the job done | 20:09 |
mtreinish | hogepodge: heh, I'm just giving you a hard time about not being a puppet purist :) | 20:09 |
catherineD | because if refstack-client initialize the env variable "TEMPEST_CONFIG_DIR" and "TEMPEST_CONFIG" then tempest would be able to identty the correct tempest,conf for testr list-tests | 20:10 |
mtreinish | catherineD: you shouldn't need to have a tempest.conf at all set to run a list-tests | 20:11 |
catherineD | mtreinish: still I am not quite sure why testr list-tests need a tempest,conf ... this is testing with the same tempest version but installed yesterday .. the differences are the library | 20:11 |
catherineD | mtreinish: exactly ... that is how we have been running until maybe a week ago ... | 20:11 |
mtreinish | catherineD: which sounds like a tempest bug... | 20:11 |
catherineD | I feel like someting in oslo lib but not sure ... will dig in more | 20:12 |
mtreinish | like I said there is 1 module which tries to use the conf file at import time (which is all test discovery does, import the tests) but we fast path around that case if the file isn't defined | 20:13 |
mtreinish | well 1 that uses it for real (there are others that aren't critical) | 20:13 |
mtreinish | hogepodge: that looks reasonable (well assuming you're running serially) | 20:15 |
mtreinish | hogepodge: you're running against a keystone v3 cloud? | 20:15 |
mtreinish | catherineD: the other thing I just remembered is we do have a unit test to ensure that tempest can always run a list test without config: https://github.com/openstack/tempest/blob/master/tempest/tests/test_list_tests.py | 20:22 |
catherineD | mtreinish: great this will be helpful ... thx for the link | 20:28 |
*** dwalleck has quit IRC | 20:33 | |
*** sarob_ has joined #refstack | 20:59 | |
hogepodge | mtreinish: v2/v3 | 21:11 |
hogepodge | mtreinish: I've deployed both | 21:11 |
mtreinish | hogepodge: ok cool, I guess v3 is more common place now than like a year ago | 21:21 |
*** sarob_ has quit IRC | 22:05 | |
*** sslypushenko has quit IRC | 22:54 | |
*** sslypushenko has joined #refstack | 22:54 | |
*** edmondsw has quit IRC | 23:06 | |
*** lifeless has quit IRC | 23:06 | |
*** lifeless has joined #refstack | 23:09 | |
*** edmondsw has joined #refstack | 23:13 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!