Earlier  
Posted Nick Remark
#openstack-nova - 2017-02-14
14:54:46 mriedem ok
14:55:17 scottda Sorry, I still need to audit all the swap tests, to verify we're getting what we want by calling nova swap_volume.
14:55:31 scottda I've brought it up with Erlon, but I need to check the nova logs.
14:56:25 mriedem in case you guys haven't seen this yet https://review.openstack.org/#/c/433272/
14:56:29 mriedem is why we're talking about it
14:57:06 smcginnis Heard mention but hadn't seen yet. Makes sense to me to simplify that.
14:57:54 sdague mriedem well, I've also got a cinder patch up to default to working in the publicURL case - https://review.openstack.org/#/c/433289/
14:58:34 smcginnis sdague: Might be good to put a "Depends-on" on there if you update it.
14:59:40 jaypipes anybody else seeing a "No module named gdbm" failure trying to run unit or functional tests today?
15:00:17 smcginnis jaypipes: I've seen that in the past. Can't remember how I resolved it other than maybe just "rm -fr .tox"
15:00:19 sdague jaypipes: you have to run python3 tests first
15:00:26 smcginnis Oh, right!
15:00:34 sdague smcginnis: it's testrepository
15:00:57 sdague jaypipes: rm .testrepository/times.dbm
15:01:00 smcginnis sdague: So jaypipes will need to delete .testrepository first, right? Then run py35 first.
15:01:04 jaypipes sdague: you mean I need to rm -rf .tox; tox -epy35; tox -efunctional?
15:01:18 jaypipes sdague: ah, .testrepository.
15:01:20 smcginnis sdague: Oh, good point. Just times.dbm
15:01:26 sdague jaypipes: no, I mean you have to delete your testrepository dbm file, and always run python35 tests before others
15:01:42 sdague testrepository uses default dbm format from python
15:01:45 jaypipes sdague: good to know. ty vm sir!
15:01:53 sdague there are about 5? formats
15:02:13 sdague the default format in python2 was actually deleted entirely from the stdlib in python3
15:02:28 sdague because, clearly, that could never go wrong :)
15:02:32 jaypipes heh
15:02:48 sdague and there was resistance to work around it in testrepository
15:02:58 sdague maybe mtreinish can fix that in his fork
15:05:28 mtreinish sdague: I already have an experimental feature in it that uses subunit2sql instead of dbm
15:05:50 sdague mtreinish: ok, but you could also just resolve the dbm issue right?
15:05:56 mtreinish sdague: the sql repository type: http://stestr.readthedocs.io/en/latest/MANUAL.html#repositories
15:06:04 bauzas mriedem: I have a question on https://review.openstack.org/#/c/432482/1
15:06:08 mtreinish sdague: that's harder because it's dbm issue in python
15:06:20 sdague mtreinish: right, but you can just pick a format that python3 understands
15:06:30 mriedem bauzas: don't you guys package docs in your rpms?
15:06:33 sdague which is why it works from python3 -> python2
15:06:44 mtreinish oh, good point. That shouldn't be hard
15:06:44 bauzas mriedem: dunno, but I can ask
15:06:55 bauzas mriedem: IIRC, we have a different resource
15:06:56 mtreinish I just need to remember what the right one to use is
15:07:26 bauzas mriedem: like https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform
15:12:35 mriedem melwitt: dansmith: ever seen this in a cells v1 job? http://logs.openstack.org/57/433257/2/check/gate-tempest-dsvm-cells-ubuntu-xenial/1732de2/logs/screen-n-cell-child.txt.gz#_2017-02-13_22_55_18_192
15:13:27 dansmith mriedem: hmm, no
15:14:03 mriedem could be latent
15:14:38 mtreinish jaypipes, sdague: https://github.com/mtreinish/stestr/commit/9869bfe48ed87d9abf3f3397c46a9d7f8dc60031 give that a shot
15:15:23 mriedem dansmith: actually looks like a regression
15:15:25 sdague mtreinish: that's going to mean that everyone's dbm dies the first time they try to run it again on python2 right?
15:15:32 mriedem http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Couldn't%20communicate%20with%20cell%20'child'%5C%22&from=7d
15:15:46 mriedem mtreinish: did something chagne in test_stamp_pattern? ^
15:15:48 sdague mtreinish: probably also just need an exception around the open and just rebuild the db
15:15:53 mriedem i don't think tempest runs against cells v1
15:16:12 mtreinish sdague: well for most people it won't matter because stestr uses a seperate repository dir
15:16:15 mriedem https://github.com/openstack/tempest/commit/96c36cffbe115226402600c321c2de701b281f7b
15:16:16 mriedem ha
15:16:21 mtreinish but yeah I can add an exception
15:16:43 mriedem mtreinish: i guess i can abandon this 2 year quest now https://review.openstack.org/#/c/218355/
15:16:55 mtreinish mriedem: wow, how did that slip by without either of noticing
15:16:55 mriedem dansmith: yeah so nova gate is blocked, i'll put up a skip patch
15:17:18 mtreinish sdague: unless you'd like to push a pull request for that :)
15:17:34 dansmith mriedem: it's 100% fail on that cells thing?
15:17:41 mriedem yes
15:17:43 mriedem it uses security groups
15:18:24 mtreinish mriedem: does the test actually work now?
15:18:26 dansmith sorry, I'm too distracted.. are you saying tempest is now running a secgroup test against a cells deploy that can't handle it?
15:18:52 mriedem dansmith: cells v1 yes
15:18:56 dansmith yeah, okay
15:19:02 mriedem anyway, i've got the fix
15:19:08 mriedem mtreinish: i guess?
15:19:18 mriedem mtreinish: https://review.openstack.org/#/c/431800/
15:20:01 mriedem maybe killing liberty is what did the trick
15:20:44 mriedem maybe i should start a massive ML thread about how tempest just goes and breaks nova's gate because it doesn't test against cells v1 :)
15:20:53 mriedem same with devstack
15:20:56 mriedem crazy QA guys
15:21:00 sdague mriedem: and nova-net
15:21:16 mriedem i can't remember the last nova-net regression
15:21:36 sdague so, I thought there was a feature flag around security groups
15:21:43 mriedem sdague: that never got it
15:21:45 mriedem *in
15:21:48 sdague oh
15:22:28 mriedem https://review.openstack.org/#/c/225199/
15:22:42 mriedem nearly a year old, might as well abandon
15:22:49 mriedem ccarmack isn't going to be working on that
15:26:00 bauzas mriedem: planning to cut RC2 by Thurs ?
15:26:12 mriedem bauzas: yes
15:26:27 bauzas okay
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

Earlier   Later