Earlier  
Posted Nick Remark
#openstack-nova - 2018-06-18
18:21:34 mriedem sorry i didn't have the full evac migration task state in my head when writing that comment...
18:21:45 dansmith well, I never knew it would do that
18:21:55 dansmith although I wonder if it would when I wrote that, because we did rebuild_claim recently, IIRC
18:22:30 mriedem as in 2015? https://review.openstack.org/#/c/200485/
18:22:39 dansmith oh
18:22:58 dansmith I thought we added that while cleaning things up for placement, but maybe not
18:23:15 mriedem no, it was part of this https://review.openstack.org/#/q/topic:bug/1417667+(status:open+OR+status:merged)
18:23:42 dansmith yep, okay
18:24:00 mriedem i semi remember looking at that recently because of https://review.openstack.org/#/c/560467/
18:24:23 mriedem and because we log a warning during every live migratoin
18:25:08 mriedem artom_: artom__: you might care about ^
18:28:28 artom Sorry, moving around between rooms in the office :(
18:28:43 artom mriedem, thanks for the tip, I *would* care about that, but what's the context?
18:29:23 mriedem artom: RT claims code with live migration
18:29:27 mriedem which is now your thing
18:30:36 artom Sorta (see http://lists.openstack.org/pipermail/openstack-dev/2018-June/131605.html)
18:32:58 crazik :D
18:39:08 openstackgerrit Zack Cornelius proposed openstack/nova master: Implement file backed memory for instances in libvirt https://review.openstack.org/567876
19:04:33 openstackgerrit Giridhar Jayavelu proposed openstack/nova master: Avoid redundant compute node update https://review.openstack.org/576235
19:11:22 openstackgerrit Eric Fried proposed openstack/nova-specs master: Spec: Handling Reshaped Provider Trees https://review.openstack.org/572583
19:15:06 openstackgerrit Eric Fried proposed openstack/nova master: WIP: Compute: Handle reshaped provider trees https://review.openstack.org/576236
19:52:46 openstackgerrit Eric Fried proposed openstack/nova master: Nix unused raise_if_custom_resource_class_pre_v1_1 https://review.openstack.org/575847
20:18:29 openstackgerrit Merged openstack/nova master: Skip ServerShowV263Test.test_show_update_rebuild_list_server for cellsv1 https://review.openstack.org/576194
20:24:15 anupn Hi Folks, I am trying to schedule an instance over my baremetal node which is in "Available" state, but "host not mapped to any cell" error is coming upon scheduling an instance. Could you please point me how to map the host to the nova_cell1?
20:25:03 anupn I tried running "nova-manage db sync", and "nova-manage cell_v2 simple_cell_setup" but no luch
20:25:06 anupn *luck
20:25:31 mriedem anupn: see the discover_hosts command https://docs.openstack.org/nova/latest/cli/nova-manage.html#nova-cells-v2
20:27:31 anupn mriedem: Yes I did, and I don't see any hosts there
20:27:55 mriedem did you run it with the --by-service option?
20:28:20 openstackgerrit Dan Smith proposed openstack/nova master: Fix MigrateData object tests for compat routines https://review.openstack.org/576256
20:28:21 dansmith zcorneli: ^
20:29:01 zcorneli dansmith: Was just looking at jaypipes suggestion for that.
20:29:43 dansmith zcorneli: basically just what I did
20:29:44 anupn mriedem: Nope, i ran without it and I got a user warning "UserWarning: The psycopg2 wheel package will be renamed from release 2.8......"
20:29:45 dansmith except better
20:30:00 mriedem anupn: well, try running with it, since it's for ironic nodes
20:30:08 zcorneli Yep. I like the lambda, makes it more clear, I think.
20:30:19 anupn mriedem: still the same
20:30:29 dansmith zcorneli: I spent my time writing code, else I'd have committed my comment before jaypipes :P
20:30:53 mriedem anupn: did you run it with --verbose to see if it actually mapped anything?
20:30:53 anupn mriedem: Should i run "nova-manage cell_v2 map_cell1"?
20:30:59 mriedem no
20:31:12 zcorneli dansmith: Do we want to follow his other suggestion as well, and do the associated AssertIn's?
20:31:14 mriedem unless the host is actually in some other db
20:31:22 dansmith zcorneli: I did
20:31:47 dansmith zcorneli: well, what I meant was, I added a positive assertion in each case
20:31:55 anupn mriedem: Okay so with --verbose, I see it finds two cells - cell0 and cell1
20:32:00 dansmith zcorneli: no need to assert the presence of all the things for the latest version, IMHO
20:32:07 anupn it is skips cell0 as no hosts in that
20:32:07 dansmith zcorneli: just one to make sure you're not looking at the wrong level of the structure
20:32:42 anupn and from cell1 I see - "Getting computes from cell 'cell1': 182677b0-4e7d-416b-a47b-57c2f33e090e
20:32:42 anupn Found 0 unmapped computes in cell: 182677b0-4e7d-416b-a47b-57c2f33e090e
20:32:42 anupn "
20:33:01 zcorneli Seems like the positive assertion for every field is "clear" - It should be covered elsewhere in the tests as well, but ensures "It was there before making compatible, and not there after"
20:33:10 mriedem anupn: what does this give you? nova-manage cell_v2 list_hosts 182677b0-4e7d-416b-a47b-57c2f33e090e
20:33:19 mriedem does the compute host that's hosting that baremetal node show up in the list?
20:33:41 zcorneli dansmith: The single definitely helps fix the previous issue we had through with the false positives
20:33:50 dansmith right
20:34:14 dansmith zcorneli: you're welcome to positive-assert your property if you want, but I don't think it's that necessary
20:35:17 anupn mriedem: yes
20:35:26 mriedem anupn: ok so then the host is mapped to cell1
20:35:32 anupn I see the hostname of my node
20:35:39 mriedem anupn: try scheduling now
20:35:54 zcorneli dansmith: I'm OK with the statement that the positive side is covered elsewhere.
20:36:38 openstackgerrit Artom Lifshitz proposed openstack/nova master: DNM: Use claim context during live migration https://review.openstack.org/576222
20:36:38 anupn mriedem: Okay, wait but "openstack hypervisor list" shouldn't it show my ironic type hypervisor?
20:36:57 mriedem anupn: yes
20:36:59 anupn mriedem: oh yeah, it shows now
20:37:06 mriedem whew
20:37:16 anupn mriedem: so I think scheduling should work now
20:37:20 mriedem i hope so
20:37:28 anupn mriedem: what commands, made this magic?
20:37:34 mriedem discover_hosts --by-service
20:37:35 mriedem presumably
20:37:52 anupn mriedem: Ah, that's interesting, worth making a note
20:43:25 anupn mriedem: Instance got scheduled like charm :)
20:43:40 anupn thanks
20:44:26 mriedem anupn: cool, yw
20:51:09 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix regression when listing build_requests with marker and ip filter https://review.openstack.org/576161
20:56:49 openstackgerrit Eric Fried proposed openstack/nova master: Tighten up ReportClient use of generation https://review.openstack.org/556669
20:57:54 openstackgerrit Matt Riedemann proposed openstack/nova master: Clarify placement DB schema migration https://review.openstack.org/576265
20:59:53 SpamapS So.. question about placement service logs..
21:00:00 SpamapS They're basically destroying our ELK stack
21:00:05 SpamapS is there any value in logging all of that at INFO?
21:10:59 openstackgerrit Eric Fried proposed openstack/nova-specs master: Spec: Handling Reshaped Provider Trees https://review.openstack.org/572583
21:13:16 openstackgerrit Eric Fried proposed openstack/nova-specs master: Spec: Handling Reshaped Provider Trees https://review.openstack.org/572583
21:13:53 efried SpamapS: You can bust the log level down if you like.
21:14:19 efried SpamapS: What kind of logging are you seeing? I haven't looked at one lately.
21:16:20 openstackgerrit Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
21:16:34 openstackgerrit Chris Dent proposed openstack/nova master: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
21:19:26 openstackgerrit Dan Smith proposed openstack/nova stable/queens: Add amd-ssbd and amd-no-ssb CPU flags https://review.openstack.org/576270
21:25:11 jroll efried: random tempest-full run on INFO: http://logs.openstack.org/66/362766/109/gate/tempest-full/52a4e60/controller/logs/screen-placement-api.txt.gz?level=INFO
21:25:17 jroll that is certainly a lot of logs
21:25:32 jroll looks like it's logging each request at INFO
21:25:44 efried jroll: Is that not what it should be doing?
21:25:56 efried It's not logging payloads.
21:26:02 efried That would be DEBUG-worthy.
21:26:04 jroll I don't know, I don't make those decisions :P
21:26:18 zcorneli dansmith: For that test fixup, looks like there's a number of similar issues in the objects/ dir, worth fixing them all?
21:26:33 jroll efried: in my experience, apache/nginx/whatever does the request logging, and the service only logs whatever else is needed

Earlier   Later