Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-07-31
21:42:20 dansmith running them each once leaves it at update, delete
21:42:27 dansmith so no allocation at all, target or source
21:42:36 mriedem ok new things looks fine
21:42:41 dansmith ack
21:44:39 dansmith boom ^
21:44:41 openstackgerrit Dan Smith proposed openstack/nova master: Test resize with placement api https://review.openstack.org/487958
21:44:41 dansmith dang
21:44:44 dansmith boom ^
21:45:36 mriedem oh you sucker
21:45:59 mriedem DOUBLE BOOM!
21:46:03 mriedem SONIC BOOM?!
21:48:17 tonyb mriedem: https://www.youtube.com/watch?v=Fnmh7dF4c2U
21:48:20 dansmith ah, I didn't realize what you were pointing to in that
21:48:57 mriedem tonyb: exactly
21:49:21 openstackgerrit Dan Smith proposed openstack/nova master: Test resize with placement api https://review.openstack.org/487958
21:49:41 dansmith turBOOM
21:51:32 mriedem dansmith: the commit message is a bit old now
21:51:41 dansmith gdi riedeman
21:52:11 mriedem well you could just leave it
21:52:24 mriedem 2 n's btw
21:52:29 mriedem double-n as my dad would say
21:52:42 mriedem karl with a k, double-n
21:53:14 dansmith gdi riedermann
21:53:21 mriedem double r is more like it
21:53:25 dansmith heh
21:53:32 mriedem riderman as my first manager at ibm would say
21:53:35 mriedem and write
21:54:00 openstackgerrit Dan Smith proposed openstack/nova master: Test resize with placement api https://review.openstack.org/487958
21:54:05 dansmith hah, riderman
21:55:31 mriedem so i pulled it down and ran just the test class and both tests failed
21:55:46 dansmith they pass for me...
21:56:03 dansmith fail how?
21:56:43 mriedem i could be picking up a stale branch with the git review -d
21:56:56 mriedem no that's not it
21:57:37 dansmith okay I see fails if I run them in tox in parallel
21:58:03 dansmith they pass in isolation
21:59:03 mriedem i'm just doing:
21:59:03 mriedem tox -e functional -- nova.tests.functional.test_servers.ServerMovingTests
21:59:08 mriedem this time they both passed
21:59:27 dansmith ugh
22:00:22 dansmith I just ran singles a bunch of times and saw it fail
22:01:20 dansmith and it fails to assert the usage of the target, which should be stable since I run the periodics in the same order each time
22:01:45 dansmith brb
22:01:57 mriedem same here
22:07:22 mriedem wonder if it has something to do with the _FAKE_NODES in the fake virt driver
22:10:27 dansmith I think we're racing with other threads
22:10:40 dansmith I see when it fails that we delete the allocation, but PUT it right after, then the test fails
22:10:53 dansmith because it expects it to be gone, since the periodic on the second node should delete it
22:16:09 dansmith seems to fail more often than not when I run it from tox
22:16:38 dansmith but passes every time when I run it with subunit.run
22:16:46 jaypipes dansmith: have you pushed up another gibi patch? do I need to rebase?
22:16:58 dansmith jaypipes: yes, but it's not stable and I'm not sure why
22:20:00 jaypipes dansmith: that whole time.sleep(1) and manipulating the fake.set_nodes() globals is probably the culprit...
22:20:43 melwitt dansmith: I think subunit.run doesn't run tests in parallel but tox does (via testr underneath)
22:20:55 jaypipes dansmith: you could try adding a time.sleep(1) after the second self.start_service() call...
22:24:08 mriedem i'm not sure why the first time.sleep(1) is needed after the first service starts
22:24:52 dansmith melwitt: I'm running one test with tox, so should be the same
22:25:03 melwitt oh, one test
22:26:30 dansmith jaypipes: doesn't help
22:29:07 dansmith oh,
22:29:19 dansmith I was thinking he was forcing to host1 on initial boot each time
22:29:21 dansmith but he's not
22:29:37 dansmith so maybe it's just based on which it initially lands on and then moves to
22:30:02 dfisher nova-compute doesn't use etcd3, does it? (pike b3)
22:30:06 dansmith because I'm running periodics in a set order, but the actual stuff will be reversed
22:39:28 dansmith yeah I think that makes it repeatable
22:43:02 mriedem dansmith: yeah it's random
22:43:16 mriedem so toggle the update_rt call based on which host i guess?
22:43:20 mriedem dfisher: nope
22:43:29 dansmith mriedem: no, we need to run it both ways and make sure it behaves the same
22:43:38 mriedem oh
22:43:39 dansmith I shall have patchification soonly
22:43:46 mriedem cool
22:43:57 dfisher mriedem: i'm seeing nova service-list show my compute node but openstack hypervisor list not show it.
22:44:13 mriedem dfisher: is it mapped to a cell?
22:44:22 mriedem nova-manage cell_v2 discover_hosts
22:44:30 mriedem --verbose
22:44:30 dfisher no, it's not mapped.
22:44:38 dfisher how would I map it
22:44:42 dfisher ?
22:46:01 mriedem dfisher: ^
22:46:04 mriedem discover_hosts
22:46:29 dfisher yeah, that's not finding it :(
22:46:48 dfisher http://paste.openstack.org/show/617066/
22:48:25 dansmith dfisher: then your compute isn't checking into the cell1 db
22:48:52 dansmith dfisher: make sure your conductor's config is pointed at the cell1 db, matching the cell1 cell_mapping record
22:49:08 dfisher ok. will poke. thanks dansmith!
22:52:26 openstackgerrit Dan Smith proposed openstack/nova master: Test resize with placement api https://review.openstack.org/487958
22:52:32 dansmith mriedem: ^ see if you hate that
22:52:40 dansmith should be repeatable, and keep jaypipes honest :)
22:57:17 mriedem dansmith: questions inline about the az stuff
22:59:25 dansmith mriedem: comments inline
23:00:51 mriedem oh right forced_host
23:00:58 mriedem which there used to be a docs page for that,
23:01:02 mriedem but with the migration it looks like it's gone
23:01:16 mriedem and our api-ref doesn't mention this wrinkle of course
23:03:19 dansmith I admit, I had to copy some deets out of an ask.o.o article :P
23:03:42 mriedem there used to be a nice docs page called "Select hosts where instances are launched"
23:03:46 mriedem and it had this information in it
23:03:51 mriedem but apparently it's been deleted

Earlier   Later