Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-06-08
21:21:01 jroll https://bugs.launchpad.net/nova/+bug/1775934
21:21:02 openstack Launchpad bug 1775934 in OpenStack Compute (nova) "Cannot run "openstack server list" with instance stuck in scheduling state" [Undecided,New]
21:21:05 jroll yeah, this isn't with deleted
21:21:31 jroll writing that I now understand why bauzus was trying to figure out how it got in that state
21:21:31 melwitt k, thanks
21:21:42 jroll I guess we probably don't expect it to work with an invalid cell mapping
21:22:07 melwitt well, if there's an invalid cell_mapping, it's supposed to use the data from nova_api.build_requests
21:23:04 melwitt rather, if InstanceMapping.cell_id=NULL it should be using nova_api.build_requests and using that to list and not failing
21:23:17 jroll well, that's an empty table :/
21:23:39 melwitt build_requests is empty?
21:23:57 jroll yep
21:24:17 melwitt huh. that is weird
21:24:23 jroll indeed
21:24:38 mriedem pretty sure it doesn't work that way
21:24:46 mriedem this is the same thing surya was talking about on wednesday
21:24:56 mriedem we look for a build request and if not there, we look for an instance mapping with a cell
21:25:17 mriedem if the build request is gone, the instance mapping should have a cell mapping because we delete the build request after updating the instance mapping
21:25:36 melwitt this shows if mapped, we look in the cell db, else we look at build requests https://github.com/openstack/nova/blob/stable/ocata/nova/compute/api.py#L2322-L2347
21:25:40 mriedem https://bugs.launchpad.net/nova/+bug/1773945
21:25:41 openstack Launchpad bug 1773945 in OpenStack Compute (nova) "nova client servers.list crashes with bad marker" [Medium,Triaged] - Assigned to Surya Seetharaman (tssurya)
21:26:12 mriedem ok, but could be hitting ^
21:26:20 mriedem where the build request is gone but the instance mapping doesn't have a cell mapping in it
21:26:28 melwitt ah, okay
21:27:14 melwitt jroll: build requests don't get soft-deleted so could be empty if everything got cleaned up properly
21:27:32 jroll oh nice, thanks mriedem
21:28:01 melwitt your traceback is different than that one, but could it be the same root cause?
21:28:24 jroll probably
21:29:02 jroll I have to bounce but pointed internal folks at that bug and the one I filed
21:29:14 jroll I can update monday if they found anything new
21:29:58 jroll thanks for all the help melwitt, mriedem
21:30:23 melwitt based on your traceback, it looks like the instance get_all from compute/api succeeded but then you failed when the REST API code tried to access instance.get_flavor(), it wanted to lazy-load it. but that attribute should have been pre-loaded. so I don't get that yet
21:31:36 melwitt jroll: thanks for letting us know about the bug
21:32:08 mriedem that lazy load failure sounds familiar
21:34:03 mriedem https://github.com/openstack/nova/commit/5a363a0d72e7dd8d79d7e950effc1d8a5fdc801b#diff-1b01e8e37be9d889295e5333b7857139
21:34:30 mriedem that's likely not it
21:34:34 mriedem probably something else in the api code
21:38:35 melwitt so they get here and fail during flavor lazy-load https://github.com/openstack/nova/blob/stable/ocata/nova/api/openstack/compute/servers.py#L369 but it seems "impossible" that they could have gotten there with cell_id=NULL + build_requests table empty
21:39:46 melwitt oh actually that's get_all so different than what I was looking at get earlier
21:43:37 melwitt okay so that does make sense, the get_all in compute/api would find whatever is in the cell dbs regardless of cell_mapping=None. so that would succeed. but should also have flavor preloaded on the instance objects returned, so why is a lazy-load happening
21:44:18 melwitt nothing should have been created from build requests if the build_requests table is empty...
21:47:09 melwitt maybe he tried that test earlier when there were build requests still. that would make sense, if some items in the instance list were "shell" instances created from build_requests, then instance.get_flavor() would trigger a lazy-load
21:56:09 melwitt jroll: if you could show nova_cell0.instance_extra for that instance it might help too
21:58:27 melwitt maybe not actually. I was trying to think whether the embedded flavor was even there but it might not be relevant
23:30:43 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
23:30:44 openstackgerrit Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
23:30:45 openstackgerrit Chris Dent proposed openstack/nova master: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
23:31:03 openstackgerrit Chris Dent proposed openstack/nova master: Add PLACEMENT_DB_ENABLED=True to the nova-next job https://review.openstack.org/564067
23:56:48 openstackgerrit Chris Dent proposed openstack/nova master: Extract part of PlacementFixture to placement https://review.openstack.org/568359
#openstack-nova - 2018-06-09
00:48:45 vpc hi
00:48:49 vpc anyone online?
07:40:14 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Return all nested providers in tree https://review.openstack.org/559480
07:40:15 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add microversion for nested allocation candidate https://review.openstack.org/565487
07:40:16 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Fix nits in placement-return-all-resources series https://review.openstack.org/573604
#openstack-nova - 2018-06-10
01:42:40 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Return all nested providers in tree https://review.openstack.org/559480
01:42:41 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add microversion for nested allocation candidate https://review.openstack.org/565487
01:42:42 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Fix nits in placement-return-all-resources series https://review.openstack.org/573604
03:46:24 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Return all nested providers in tree https://review.openstack.org/559480
03:46:25 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add microversion for nested allocation candidate https://review.openstack.org/565487
03:46:26 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Fix nits in placement-return-all-resources series https://review.openstack.org/573604
11:08:09 openstackgerrit Merged openstack/nova master: Return all resources in provider_summaries https://review.openstack.org/558045
11:22:10 openstackgerrit Alvaro Lopez Garcia proposed openstack/nova master: Ensure that periodic reclaim cleans DB deleted instances https://review.openstack.org/323250
14:16:15 mnaser is it safe to remove the cell_v2 map_instances from openstack-ansible deployment process in queens/rocky assuming no user skips releases when doing upgrades?
15:48:12 openstackgerrit Merged openstack/nova master: Remove mox in test_compute_api.py (3) https://review.openstack.org/568184
16:23:25 openstackgerrit Maciej Kucia proposed openstack/nova-specs master: Fix Non-unique network names in Servers IPs API response https://review.openstack.org/558125
18:09:28 openstackgerrit Merged openstack/nova master: Remove mox in libvirt/test_driver.py (4) https://review.openstack.org/570750
18:54:29 openstackgerrit Chris Dent proposed openstack/nova master: Provide a direct interface to placement https://review.openstack.org/572576
22:18:54 openstackgerrit Chris Dent proposed openstack/nova master: Provide a direct interface to placement https://review.openstack.org/572576
23:56:56 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (1) https://review.openstack.org/572018
#openstack-nova - 2018-06-11
00:00:24 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (2) https://review.openstack.org/573481
00:26:14 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (3) https://review.openstack.org/574104
00:49:16 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (4) https://review.openstack.org/574106
01:15:48 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (5) https://review.openstack.org/574110
01:46:02 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (6) https://review.openstack.org/574113
01:55:55 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717
01:56:24 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create https://review.openstack.org/520313
02:07:06 openstackgerrit jiang wei proposed openstack/nova master: Add action initiator attribute to the instance info https://review.openstack.org/536243
02:10:05 naichuans Hi, mriedem: melwitt: cores, do you have the time to review https://review.openstack.org/#/c/486475/ ?
02:11:13 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717
02:21:50 pvc hi
02:21:52 pvc anyone can help me
02:23:22 naichuans pvc: vgpu still doesn't work?
02:24:12 pvc how can i share my GTX 1080 TI to 2 instance?
02:24:14 pvc is that possible?
02:24:48 pvc https://www.openstack.org/assets/presentation-media/Enable-GPU-virtualization-in-OpenStack.pdf
02:24:48 naichuans If you are using passthrough, I think you can't share it among VMs
02:25:01 pvc so what is alternative to passthrough?
02:25:21 pvc this ? https://docs.openstack.org/nova/queens/admin/virtual-gpu.html
02:27:30 naichuans You can use vgpu type support in XenServer, I can help you with it. But if you are using KVM, you need to talk with bauzas, who is an expert on vgpu in libvirt.
02:36:31 naichuans pvc: The basic virtual vgpu should be support for a long time, make sure you are using the latest source code and set white list in nova.conf
02:37:47 naichuans like http://paste.openstack.org/show/723145/, but at first check KVM setting, I haven't check it on KVM.
02:38:13 naichuans guild https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/add-support-for-vgpu.html
02:38:36 naichuans omit n-rp support
02:42:11 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add InstanceGroupPolicy object https://review.openstack.org/573628
02:42:12 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy to InstanceGroup object and api models. https://review.openstack.org/563375
02:42:13 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object https://review.openstack.org/563401
03:08:22 pvc thank you naichuans
03:08:24 pvc you are using ironic?
03:08:53 naichuans No, we based on XenServer.
03:09:12 pvc you know Eclipse software?
03:09:43 pvc where should i enable that devices on scheduler?

Earlier   Later