Friday, 2017-02-03

*** Rocky_g has joined #refstack00:49
*** Rockyg has quit IRC00:50
*** rmart04 has joined #refstack11:28
*** athinkingmeat has joined #refstack11:31
athinkingmeathi, i have an issue running tempest with refclient, one test fails if i have shared external network, tempest.api.network.test_ports.PortsTestJSON.test_list_ports_fields - testtools.matchers._impl.MismatchError: ['id', 'mac_address'] != [u'id', u'mac_address', u'network:tenant_id']11:37
*** markvoelker_ has joined #refstack13:29
*** markvoelker has quit IRC13:32
*** annegentle has joined #refstack13:42
*** annegentle has quit IRC13:50
*** annegentle has joined #refstack14:00
*** annegentle has quit IRC14:17
*** designbybeck_ has joined #refstack14:17
*** rmart04 has quit IRC14:35
*** designbybeck_ has quit IRC14:56
*** annegentle has joined #refstack15:59
*** annegentle has quit IRC17:25
*** annegentle has joined #refstack17:28
*** andreaf has quit IRC17:56
*** andreaf has joined #refstack17:58
*** annegentle has quit IRC18:30
*** annegentle has joined #refstack19:06
*** pvaneck has joined #refstack19:16
catherineDathinkingmeat: I feel like having a shared external network is not the reason for the failure. Do you have more than one external networks? Pls check the setting for the fixed_network_name and validation.connect_method in your tempest.conf.19:23
annegentledoes refstack itself change much, or is it mostly tempest tests that change? I rebuilt a container that installs the refstack-client, and got different errors than before, and I'm not sure where to start troubleshooting, the client or the tests?20:08
annegentleoh, and I guess also, I'm running https://refstack.openstack.org/api/v1/guidelines/2016.01/tests?target=platform&type=required&alias=true&flag=false20:11
annegentletrying to peel apart the layers20:11
catherineDannegentle: RefStack is mostly Tempest tests.... However, the default version of Tempest installed with RefStack is quite old and we are in the process to update the default Tempest version to the latest one (after we validate the new Tempest version against the 2017.01.json)21:26
annegentlecatherineD ok, thanks, that's helpful. Yeah, I see "deprecated" errors in the logs sometimes.21:26
catherineDmeanwhile, you can run your test with the latest  tempest if so wish21:27
annegentlecatherineD how do I substitute?21:27
catherineDwith the refresh instrallation of refstack ...21:27
catherineDyou can go to refstack-client/.tempest21:27
catherineDgit log  ( to note the last patch ) it should be something in July ...21:28
catherineDgit checkout -b  july-default-tempest21:29
catherineDgit branch21:29
catherineDare you with me?21:29
annegentlehm, mine is jun 17, sound right?21:30
catherineDyup21:30
annegentleokie21:30
catherineDso git branch should show that you are at at the july-default-tempest21:30
catherineDcorrect?21:30
annegentle* (HEAD detached at 4d63b16)21:30
annegentleis what I have21:30
annegentlegit log -n 1 --pretty=oneline21:31
annegentlegives Merge "Add IPv6 rule creation to validation resources"21:31
annegentleam I even close? :)21:31
catherineDwhich date is that?21:31
annegentleHere's the log21:32
annegentlehttp://paste.openstack.org/show/597632/21:32
annegentleso I built refstack-client21:33
annegentlenot refstack, I believe.21:33
catherineDyep so that is the default tempest21:33
annegentleok21:33
catherineDsorry it is refstack-client21:33
annegentleoh, right, I'm in .tempest now21:33
catherineDnow save that version by doing21:33
annegentleso the git log is tempest's git log21:33
catherineDgit checkout -b july-default-version21:33
catherineDyes git log is the tempest git log because you are in .tempest21:34
annegentleok, got it21:34
annegentlegit branch says that's the one I got - july-default-version21:34
annegentledo I need a fetch?21:34
annegentleor is that a tagged branch?21:34
catherineDnow just do21:34
catherineDgit checkout master21:34
catherineDthe git log ( and see what is the date)21:35
catherineDrefstack-client just pull from the master the date you down load21:35
annegentlecatherineD ok, great, now I have Fri Feb 3 16:39:00 2017 +000021:35
catherineDok so ...21:35
catherineDto be safe I think do21:36
annegentlecatherineD and since I cloned refstack-client today, what should that be at?21:36
catherineDpip[ install -U .21:36
catherineDyes21:36
annegentleoh sure, yeah.21:36
catherineDpip install -U .21:36
annegentlegoing going21:36
annegentlebuilding building21:36
annegentlefun fun :)21:36
catherineDafter that you should be at the latest tempest ...21:37
annegentlerefstack-client-0.1.0.dev11721:37
catherineDlet me know when it is done21:37
annegentleall done21:37
catherineDno error?21:37
annegentlenope, built fine21:38
catherineDgreat ..21:38
annegentlepip freeze | grep refstack21:38
annegentlerefstack-client==0.1.0.dev11721:38
annegentlenow, re-run tests?21:38
catherineDso now you should be at the latest tempest but I do not think that was the problem with the test-ports testcase21:38
catherineDfirst I see that you get the must pass list from 2016.01 ...21:39
catherineDso that is 2 versions older ...21:39
annegentleyeah, we're testing a liberty-based cloud21:39
catherineDin that version I believe the test-ports tests are advisory21:39
catherineDlet me double check21:39
annegentlewhat happens is it says it can't schedule building a server/instance21:39
annegentlebut I can build instances from the CLI, etc. so I must have something wrong in the test setup21:40
catherineDso in 2016.01 not work test are not required ... they are just advisory21:41
annegentleeven for server launch?21:42
catherineDback to testing ..21:42
catherineDdo you want to show me the tempest.conf .... but first of all mask out all the password before showing21:43
annegentlecatherineD sure, thanks for taking a look21:43
catherineDyou can ping me in private ...21:43
catherineDbut still mask out the password21:43
*** annegentle has quit IRC23:35

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