Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-10-25
15:52:58 dansmith mriedem: there'll be an issue with pagination with it (limits alone work fine), and that test I removed wouldn't have caught it
15:53:25 efried cdent Sigh, except for the whole line width thing.
15:53:27 dansmith mriedem: I've paged out a lot of context on this, and it's going to require re-tooling, which isn't going to happen until after summit
15:53:33 dansmith just fyi
15:53:35 cdent miagra
15:54:25 mriedem liuyulong: i have to get back to reviewing it, but busy with something else right now
15:55:04 mriedem dansmith: ack, shitty but understandable
15:55:41 mriedem dansmith: is the paging issue because we handle build requests separately from the scatter / gather sorted instances in cells thing?
15:55:47 dansmith mriedem: yeah, I wish I had written a test for this when I wrote the rest, I dunno why I didn't
15:56:44 dansmith mriedem: it's because the marker could be in build requests which we look up differently from other things, and because we need to be able to do that special value-based marker resume thing in there too
15:56:52 stephenfin Am I able to get access to these fixture properties in a test? https://github.com/openstack/nova/blob/master/nova/tests/fixtures.py#L191-L197
15:56:58 stephenfin (stdout and stderr)
15:57:13 stephenfin sdague, perhaps? ^
15:57:54 mriedem stephenfin: you'd have to store the fixture object in the base nova TestCase class
15:58:00 mriedem stephenfin: like we do here: self.stdlog = nova_fixtures.StandardLogging()
15:58:12 mriedem then you can access the attributes in the fixture from a test
15:58:13 liuyulong mriedem, great, thank you.
15:59:32 sdague stephenfin: yeh, what mriedem said
16:01:18 stephenfin mriedem, sdague: Spot on. I'll do that so
16:08:23 mriedem sdague: something i didn't think about in the flavor description spec, but i didn't say i'd return the description in GET /flavors - which is the limited response - only id, name and links
16:08:33 mriedem not sure if i should include the description or not
16:09:12 mriedem i never use GET /flavors because i want to see how much ram/cpu/disk i'm getting
16:10:25 openstackgerrit sahid proposed openstack/nova master: libvirt: disconnect volume from host during detach https://review.openstack.org/515008
16:17:09 cdent anyone have today’s count on number of different in progress changes racing for placement microversion 1.11?
16:30:33 stephenfin melwitt: Quick one - how come we don't need 'dump_inactive' for the additional call here? https://review.openstack.org/#/c/498983/4/nova/virt/libvirt/driver.py
16:32:20 melwitt stephenfin: that controls whether we pull the active (live) or inactive (persistent) config from the domain. we want to pull the live config after the volume was updated to write it back to the persistent config. does that make sense?
16:32:41 openstackgerrit Chris Dent proposed openstack/nova master: [placement] manage cache headers for inventories https://review.openstack.org/510954
16:32:41 openstackgerrit Chris Dent proposed openstack/nova master: [placement] manage cache headers for /resource_providers https://review.openstack.org/495380
16:32:42 openstackgerrit Chris Dent proposed openstack/nova master: [placement] manage cache headers for usages https://review.openstack.org/513174
16:32:42 openstackgerrit Chris Dent proposed openstack/nova master: [placement] manage cache headers for resource classes https://review.openstack.org/513161
16:32:43 openstackgerrit Chris Dent proposed openstack/nova master: [placement] manage cache headers for aggregates https://review.openstack.org/515128
16:33:02 stephenfin melwitt: Ah, that wasn't immediately obvious to me. Yup, makes sense. +2d
16:33:44 melwitt stephenfin: it could stand to have a code comment, tbh. at the time, I thought I was explaining it with the comment I added but it doesn't call out dump_inactive specifically
16:34:12 stephenfin Yeah, I added a comment to leave that in there. However, it's nit so only address if you can
16:35:17 cfriesen is there a novaclient/openstackclient command that does a GET on /os-hypervisors/detail ?
16:35:33 mriedem nova hypervisor-list?
16:35:41 cfriesen that doesn't have the detail
16:35:45 melwitt stephenfin: k, lemme do an edit on it
16:37:35 mriedem cfriesen: doesn't look like it on the CLI, the python API binding has a detailed kwarg though
16:37:41 mriedem so it could be easily added to the CLI
16:38:13 cfriesen mriedem: good, I'm not going blind.
16:38:41 mriedem although, the amount of stuff you'd get out of /detalis
16:38:42 mriedem *details
16:38:42 openstackgerrit melanie witt proposed openstack/nova master: Save updated libvirt domain XML after swapping volume https://review.openstack.org/498983
16:38:46 mriedem is a lot
16:39:28 mriedem which is why cli users would probably do hypervisor-list and then hypervisor-show on specific ones
16:39:42 cfriesen mriedem: I'm envisioning something like "nova list" where you could specify which fields you wanted.
16:41:44 openstackgerrit melanie witt proposed openstack/nova master: Save updated libvirt domain XML after swapping volume https://review.openstack.org/498983
16:47:07 arxcruz dansmith: hi, I'm having a problem with a temprest test test_volume_boot_pattern, failing with Block Device Mapping is Invalid: failed to get volume 800c3fc8-aa91-45ac-a27c-a15158582a3e
16:47:14 arxcruz the problem seems to be in nova
16:47:42 dansmith arxcruz: can you link to a CI run or something?
16:48:05 arxcruz dansmith: 2017-10-25 12:14:49.944 99098 INFO nova.api.openstack.wsgi [req-3b691589-73af-4fda-aee3-c5f962e4c8b7 - - - - -] HTTP exception thrown: Block Device Mapping is Invalid: failed to get volume 800c3fc8-aa91-45ac-a27c-a15158582a3e.
16:48:07 arxcruz this is from nova
16:48:11 arxcruz dansmith: let me check
16:49:04 dansmith arxcruz: that message likely means nova couldn't contact cinder or cinder complained
16:49:16 arxcruz dansmith: https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/undercloud/home/jenkins/tempest_output.log.txt.gz
16:49:22 arxcruz dansmith: there's nothing in cinder log
16:49:33 arxcruz dansmith: btw, this is tripleo
16:49:44 arxcruz dansmith: also, I have a env up on rdo-cloud if you want to take a look
16:51:43 dansmith arxcruz: okay, tripleo's log layout is hard for me to navigate, but I'm looking
16:51:56 arxcruz yeah... :/
16:52:09 dansmith arxcruz: "nothing in cinder log" meaning no big stack traces or something, right? have you tracked the request nova is making to cinder to see that it's not showing up at all?
16:52:28 arxcruz dansmith: yes, I track down, there's no request in cinder
16:52:45 dansmith arxcruz: the timestamps of the failures in tempest are *after* the latest log message in nova-api
16:52:54 arxcruz it's pretty instantly the failure when I was debuging tempest, when it calls the create_server function, it returns pretty faster
16:52:56 dansmith arxcruz: which seems unpossible
16:53:19 dansmith arxcruz: also, the log you link to is for the undercloud.. is there cinder in the undercloud?
16:53:22 arxcruz dansmith: you're talking about the line I pasted ?
16:53:34 arxcruz dansmith: no, the cinder is in overcloud
16:53:36 arxcruz just a sec
16:54:00 arxcruz dansmith: https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/subnode-2/var/log/
16:54:04 arxcruz logs for cinder and nova
16:54:57 dansmith arxcruz: is this 100% fail?
16:55:01 arxcruz dansmith: yes
16:55:11 mriedem arxcruz: i think i have a tempest patch for this already...
16:55:12 mriedem sec
16:55:54 arxcruz mriedem: cool :D
16:55:58 mriedem arxcruz: https://review.openstack.org/#/c/510951/ ?
16:56:02 mriedem that merged already though
16:56:22 mriedem you need to provide more details on where this actually fails, like trace the request as dan said
16:56:31 mriedem is it on attach, detach, other?
16:57:39 mriedem although that tempest patch wouldn't fix test_volume_boot_pattern which is a scenario test
16:59:28 mriedem looks like req-733a784c-6fed-48c5-a62b-3876edb56d57 is the request id
16:59:51 sdague mriedem: if it's being used to choose and understand, I sort of assumed it would be in GET /flavors
16:59:56 sdague but honestly, I can go either way
17:00:07 sdague maybe just ask the folks that wanted it
17:01:19 arxcruz mriedem: it's on test_volume_boot_pattern test, from my debug, it create the volume successfully, then when it tries to create the instance from the volume, it fails
17:01:46 arxcruz mriedem: here's the track from tempest https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/undercloud/home/jenkins/tempest_output.log.txt.gz#_2017-10-23_17_30_43
17:03:15 mriedem arxcruz: why don't i see the POST /servers request id in the nova-api undercloud logs? https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/undercloud/var/log/nova/nova-api.log.txt.gz
17:03:20 mriedem or would it be in the overcloud?
17:03:54 arxcruz in overcloud
17:04:19 arxcruz mriedem: https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/subnode-2/var/log/nova/nova-api.log.txt.gz
17:04:23 arxcruz this is the overcloud nova log
17:05:00 arxcruz https://logs.rdoproject.org/openstack-periodic-4hr/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset006-master/0bb0995/subnode-2/var/log/nova/nova-api.log.txt.gz#_2017-10-23_17_30_30_020
17:05:04 arxcruz the failure
17:05:40 mriedem huh, not helpful at all
17:06:56 arxcruz yeah, that's all that I can see...
17:07:04 arxcruz there's no call to cinder, just trow this error
17:07:33 mriedem in the dsvm ci logs we trace the requests to cinder via python-cinderclient
17:07:44 mriedem that would be helpful here in debugging failures in triple0 logs

Earlier   Later