Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-02-14
15:26:33 mriedem sdague: dansmith: https://review.openstack.org/433707
15:26:40 bauzas mriedem: I have https://review.openstack.org/#/c/427200/ still WIP
15:26:54 bauzas mriedem: do you think it's still fine for trying to merge it ?
15:26:59 bauzas and then cherry-picking it ?
15:27:01 mriedem bauzas: it's getting a bit late
15:27:06 bauzas yup
15:27:11 bauzas hence my point
15:27:12 mriedem i'd rather just backport to stable/ocata
15:27:18 mriedem after we release ocata
15:27:26 bauzas for a point release ? fine by me
15:27:47 sdague mriedem: +2
15:27:48 bauzas okay, I'll look after other bugs then
15:28:22 mriedem fudge, this means we'll have to backport this skip patch to ocata too
15:28:26 mriedem and newton
15:28:27 mriedem and mitaka
15:28:52 mriedem and i've got scrum to run to, so bbiab
16:02:10 jaypipes mtreinish: did something happen to -- --failing for ostestr? I'm now getting an error if I run tox -epy35 -- --failing...
16:02:41 jaypipes mtreinish: soemthing about --failing not being a regex.
16:05:17 mtreinish jaypipes: hmm, ostestr should passthrough --failing straight to testr in the subprocess since it's not a known arg
16:05:34 mtreinish we haven't changed anything related to that lately
16:05:40 jaypipes ya... that's what it used to do I think :)
16:06:21 mriedem i gave up on it
16:06:21 mriedem i haven't gotten --failing to work for a long time
16:06:51 mtreinish there might be an ostestr bug related to it
16:07:03 mtreinish I haven't tried it recently
16:07:08 mtreinish jaypipes: can you pastebin the stacktrace?
16:10:52 jaypipes mtreinish: yeah, gimme a bit. running entire functional test suite :)
16:15:23 dansmith mriedem: I use --failing every day
16:18:39 mtreinish dansmith: with ostestr or just testr straight?
16:19:00 dansmith mtreinish: whatever I get if I do "tox -ething -- --failing"
16:19:44 mtreinish dansmith: if it's py27 or anything that doesn't have an whitelist or blacklist file its probably just testr
16:19:51 dansmith okay
16:19:58 dansmith I do it on functional too
16:21:30 mtreinish dansmith: yeah it looks like ostestr is only used on the py35 jobs
16:21:34 dansmith ack
16:22:42 mriedem lyarwood: i'm enjoying working on backports of https://review.openstack.org/#/q/topic:bug/1643017+branch:stable/newton to stable/mitaka for a customer
16:22:51 mriedem lyarwood: i assume you are doing or have done the same
16:24:04 macsz gcb: ping
16:26:42 vgadiraj question - is there an enable_service command? Receiving an error when running a reproduce.sh file that reads "No hosts found to map to cell, exiting". This is for a multi-node gate job. Trying to see if adding "enable_service n-cell" has any positive effect
16:29:59 jaypipes mtreinish: paste showing tox -efunctional -- --failing working and tox -epy35 -- --failing not working: http://paste.openstack.org/show/598861/
16:30:36 jaypipes mtreinish: must be some difference between pretty_tox.sh and pretty_tox3.sh
16:31:38 jaypipes mtreinish: indeed there is quite a big difference! :)]
16:32:07 mtreinish jaypipes: yeah pretty_tox3.sh is forcing a -r there: https://github.com/openstack/nova/blob/master/tools/pretty_tox3.sh
16:32:35 mtreinish it assumes any args when it's called are going to be a regex
16:32:42 mtreinish which doesn't work if you pass --failing or another flag
16:46:56 mtreinish mriedem: do you know if novnc works on py35?
16:47:03 mriedem no idea
16:47:12 mtreinish we're trying to fix the novnc test on tempest when running under p35 and we're hitting: http://logs.openstack.org/49/429949/8/check/gate-tempest-dsvm-py35-ubuntu-xenial-nv/30158f2/logs/screen-n-novnc.txt.gz#_2017-02-14_14_44_15_302
16:47:22 mtreinish https://review.openstack.org/#/c/429949/ is the tempest change
16:55:41 sdague mriedem: which job was supposed to fail?
16:55:46 sdague because the nfs one seems to have worked
16:55:50 mriedem sdague: nfs and lvm multibackend
16:56:25 mriedem sdague: the console logs are confusing on the lvm multibackend fail because of a tempest bug https://review.openstack.org/#/c/433763/
16:56:34 mriedem but the swap volume (retype) timed out, so something failed there
16:57:32 sdague http://logs.openstack.org/85/433685/1/experimental/gate-tempest-dsvm-lvm-multibackend-ubuntu-xenial-nv/beed8bb/logs/screen-c-vol.txt.gz?level=TRACE#_2017-02-14_15_45_35_632 ok lvm multibackend actually failed in the expected way
16:58:57 mriedem yup
16:59:29 sdague I also think that this exposes further confusion on the meaning of those tokens
16:59:30 mriedem sdague: the nfs job didn't fail b/c apparently it's not testing volume snapshot yet http://logs.openstack.org/85/433685/1/experimental/gate-tempest-dsvm-full-devstack-plugin-nfs-nv/1ce9f04/console.html#_2017-02-14_15_33_51_633162
16:59:38 mriedem smcginnis: eharney: ^
17:00:01 mriedem ah https://review.openstack.org/#/c/422740/
17:01:30 faizy hey guys can anybody help guide me how to remove linux bridge that is used for security groups and use onle openvswitch
17:08:03 mriedem lyarwood: mdbooth: behold the stable/mitaka backportery https://review.openstack.org/#/c/433793/1
17:10:41 openstackgerrit Bence Romsics proposed openstack/nova-specs master: Expose trunk details over metadata API https://review.openstack.org/399076
17:23:22 openstackgerrit Vivek Agrawal proposed openstack/nova-specs master: Spec for libvirt driver extension for Veritas HyperScale https://review.openstack.org/430488
17:28:19 openstackgerrit Vivek Agrawal proposed openstack/nova-specs master: Spec for libvirt driver extension for Veritas HyperScale https://review.openstack.org/430488
17:43:25 BobBall mriedem: Any chance you could take a look at https://review.openstack.org/#/c/424428/ instead? :) I'm aware that RC2 is fast approaching and we'd still need a cherry-pick once we have a merge to master.
17:43:46 BobBall mriedem: (OK, so ignore the 'instead' - turns out my mistaken request was on #openstack-infra too! two mistakes for the price of one)
17:44:03 mriedem didn't dansmith go through that once?
17:44:48 dansmith mriedem: I did, but I don't know that I did completely.. and kinda in the middle of something else atm
17:44:49 dansmith pretty sure I vetted the object and version stuff tho
17:44:55 mriedem ok
17:45:23 mriedem BobBall: when can we expect multinode xenserver ci for live migration testing?
17:45:32 mriedem virtuozzo already beat you guys to that
17:48:24 BobBall Oh shocking! multinode is proving to be tricky because of the dodgyness of the nodes we are using (Ugly details are XenServer in VM, with devstack running in a nested VM and fudging the MAC/IP so nodepool talks directly to devstack...). Current focus is on upgrading to Xenial, but then we will switch back to trying to get multinode working.
17:49:23 BobBall Can't promise timings, but I would definitely expect multinode working during Pike, probably by P-1 but I'd be happier to be held to P-2 ;)
17:49:50 mriedem i won't hold you to it, but it makes getting stuff like this through faster
17:49:54 mriedem when it's actually tested
17:50:41 mriedem sdague: can you hit these backports for the cells v1 failure? https://review.openstack.org/#/q/Id7e8351026ca86694fc9814002b96260f6ba10f9,n,z
17:50:55 BobBall Indeed... I want to make sure that we don't regress again because it's plain embarassing.
17:51:43 sdague mriedem: yeh, I'm just going to fast approve them as we know it's a gate break
17:51:55 mriedem yeah
17:52:19 lbragstad mriedem are you planning on having a specific etherpad for your rbac/policy discussions?
17:52:33 mtreinish sdague: here's your backwards incompat fix: https://github.com/mtreinish/stestr/commit/97a52706c92cedd033484009e7ce409a0679ba41
17:52:49 mriedem lbragstad: i'm not privy to any of that
17:53:01 mriedem johnthetubaguy: are we having a big rbac/policy pow-wow at the PTG?
17:53:07 sdague mtreinish: ++
17:53:27 johnthetubaguy mriedem: I think lbragstad was looking at scheduling something
17:53:59 lbragstad johnthetubaguy mriedem i have policy/rbac penciled in for wednesday afternoon (but that's open to change if needed)
17:54:30 mriedem lbragstad: we were going to do resource providers/placement on wed afternoon, and the ironic team was going to be in on that too
17:54:47 lbragstad mriedem makes sense - i can work things around
17:54:53 mriedem thursday afternoon or friday morning probably works better for us
17:55:11 mriedem can you throw something on https://etherpad.openstack.org/p/nova-ptg-pike ?
17:55:16 lbragstad mriedem ok - i'll rework some things
18:09:51 cfriesen what is the distinction between doc/api_samples/servers/v2.X and nova/tests/functional/api_sample_tests/api_samples/servers/v2.X ? are there instructions somewhere about adding functional tests?
18:10:59 sdague cfriesen: the api samples tests include templates
18:11:02 mriedem cfriesen: the api-samples functional tests use the doc api samples as sample input data
18:11:34 sdague and when run there is a 3 way comparison between - returned results from the server, templates filled in, and static documentation that's included in our api-ref
18:11:51 mriedem i believe you're supposed to write the functional test first with the template, and then run tox -r -e api-samples to generate the doc api samples
18:11:54 sdague which ensures the documentation is up to date with the code
18:12:59 cfriesen sdague: mriedem: thanks. will give that a try.

Earlier   Later