Earlier  
Posted Nick Remark
#openstack-nova - 2017-12-19
02:39:13 mriedem oh so you have a global switch
02:39:22 lbragstad where an operator can go through and flip that switch once they have the right role infrastructure in place
02:39:31 lbragstad and they have audited their users to have the right roles
02:39:40 rybridges so the whole reason why i was asking about suspend originally is because snapshots were failing
02:39:55 rybridges and the snapshot flow (to my knowledge) is suspend > snapshot > resume
02:39:57 lbragstad (e.g. bob had the admin role but based on good faith, he didn't hose my deployment)
02:40:02 rybridges and it was always failing on suspend
02:40:22 rybridges and they still fail most of the time on suspend
02:40:25 rybridges with the same error above
02:40:42 mriedem rybridges: what libvirt calls suspend is likely != the compute api suspend
02:40:44 rybridges even though i cannot reproduce the error with suspending on the cli with the loop
02:41:31 mriedem https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L1786
02:41:48 mriedem https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L2686
02:41:57 mriedem former is what libvirt calls on the guest during a snapshot
02:42:11 mriedem latter is what you get with 'openstack server suspend'
02:42:35 rybridges oh
02:42:38 rybridges ok that is interesting
02:43:00 mriedem oh jeez, nvm
02:43:01 mriedem self.suspend(context, instance)
02:43:03 mriedem derp
02:43:05 mriedem you're right
02:43:18 mriedem i was thinking of this https://github.com/openstack/nova/blob/master/nova/virt/libvirt/guest.py#L600
02:43:54 mriedem rybridges: did you see where/why the snapshot was actually failing? have you tried doing live snapshots?
02:44:19 rybridges the snapshots are failing with the exact same error as i posted in the pastebin above
02:44:28 mriedem you might want to try live snapshot if libvirt / qemu on the host is new enough
02:44:36 rybridges it looks like it is just failing on the suspend
02:44:45 mriedem we don't call suspend if you do a live snapshot
02:44:57 rybridges we are running the latest libvirt / qemu that is available for rhel7
02:45:06 mriedem which is what?
02:45:16 mriedem https://github.com/openstack/nova/blob/stable/ocata/nova/conf/workarounds.py#L68
02:45:44 rybridges can you do live snapshot from horizon?
02:45:57 mriedem live vs cold is a config option in nova-compute in this case
02:46:01 rybridges i dont see where to do that
02:46:03 mriedem by default it's cold
02:46:40 mriedem we removed that in queens https://github.com/openstack/nova/commit/980d0fcd75c2b15ccb0af857a9848031919c6c7d
02:46:42 mriedem so now it's always live
02:46:47 mriedem well, live by default
02:47:32 rybridges ok this is very interesting
02:47:33 mriedem using libvirt 3.6.0 and qemu 2.10 we haven't seen issues with live snapshot in CI
02:47:35 rybridges i will try this now
02:47:42 rybridges ok
02:47:54 mriedem used to see about a 25% failure rate with live snapshot using libvirt 1.2.2 back in the day
02:48:08 rybridges ok
02:48:23 rybridges you said that conf option should be on the hypervisor right?
02:48:25 rybridges for nova compute
02:48:26 mriedem yeah
02:48:28 rybridges not in nova api
02:48:30 mriedem it's read from the nova-compute service
02:48:30 rybridges ok
02:49:07 mriedem if that works, penick owes me a ginger ale in dublin
02:49:36 mriedem either way i'm hanging it up for the night
02:50:41 rybridges haha
02:50:46 rybridges i will be in ireland for ptg in feb
02:50:54 rybridges so ill get ou a ginger ale too
04:52:29 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Verify parameters in servers.inc https://review.openstack.org/528201
04:52:34 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Verify parameters in servers.inc https://review.openstack.org/528201
05:21:21 openstackgerrit Nakanishi Tomotaka proposed openstack/nova master: Use Placement API to check resource usage https://review.openstack.org/528953
06:05:58 openstackgerrit Rajesh Tailor proposed openstack/nova master: Host addition host-aggregate should be case-sensitive https://review.openstack.org/498334
06:06:33 openstackgerrit Rajesh Tailor proposed openstack/nova master: Fix case-sensitivity for metadata keys https://review.openstack.org/504885
07:00:31 openstackgerrit jichenjc proposed openstack/nova master: Remove 'nova-manage shell' command https://review.openstack.org/521835
07:00:32 openstackgerrit jichenjc proposed openstack/nova master: Remove 'nova-manage logs' command https://review.openstack.org/522133
07:00:32 openstackgerrit jichenjc proposed openstack/nova master: Remove 'nova-manage account' and 'nova-manage project' https://review.openstack.org/521833
07:12:56 Guest72028 Hello All
07:19:17 Guest72028 I have a questions for nova specialists about nova ressources: is it possible to have compute nodes spares ? is it possible to reserve compute ressources , prioritize rebuild order of VM while evacuation process ?
08:25:12 openstackgerrit 龚肖 proposed openstack/nova stable/pike: compute: Catch binding failed exception while init host https://review.openstack.org/528985
08:35:02 openstackgerrit TommyLike proposed openstack/nova master: Remove redundant try/except block when authorize https://review.openstack.org/528991
08:35:38 openstackgerrit Mr Rambo proposed openstack/nova master: Fix the problems that volume-backed server rebuild https://review.openstack.org/528994
09:05:26 lyarwood mdbooth: thanks for the reviews yesterday btw, is your uuid series ready for review?
09:07:00 mdbooth lyarwood: Mostly, yes.
09:07:17 mdbooth lyarwood: Well, most of it
09:08:22 mdbooth lyarwood: I'd very much like your input on this one: https://review.openstack.org/#/c/528363/
09:08:41 mdbooth But I'm about to rebase that into the main series, because I need it for the next patch
09:09:33 mdbooth The series is here: https://review.openstack.org/#/q/topic:bp/local-disk-serial-numbers+(status:open+OR+status:merged)
09:10:36 lyarwood mdbooth: ack, looking
09:13:27 mdbooth lyarwood: Thanks
09:37:46 openstackgerrit Mr Rambo proposed openstack/nova master: Fix the problems that volume-backed server rebuild https://review.openstack.org/528740
09:41:28 maciejjozefczyk gibi jaypipes: Hello, thanks for your comments :) Please check my response https://review.openstack.org/#/c/520024/ Thank you!
10:02:49 lyarwood mdbooth: so the DriverVolumeBlockDevice change LGTM, could we set self.connection_info earlier and just pass that around within the method?
10:05:03 mdbooth lyarwood: Which function are you referring to specifically?
10:05:51 lyarwood mdbooth: _legacy_volume_attach or _volume_attach in block_device.py
10:06:28 mdbooth Sec, just reading and digesting your review comment
10:07:07 mdbooth lyarwood: Ah, you're talking about *not* changing the interface?
10:07:17 mdbooth And continuing to pass connection info explicitly?
10:07:46 lyarwood mdbooth: no, just setting self.connection_info when we actually fetch it from cinder
10:07:56 mdbooth Ah...
10:08:45 mdbooth Yep, that would be cleaner.
10:08:54 mdbooth It would make the patch a bit noisier, though...
10:08:59 mdbooth And it's already pretty noisy.
10:09:01 mdbooth Hmm...
10:09:06 lyarwood yeah I assumed that's why you didn't do it tbh
10:16:06 norman hi all, anyone know why domainxml of the live-migrated instance has <features> under <cpu> section, but new booted instances not
10:17:04 norman I'd trying go through the code ,failed to find clues. I am still using the Mitaka, not sure the new version is Ok or not
10:17:56 Tahvok Hey guys, I'm unable to find a good example of ComputeCapabilitiesFilter. Do you apply it on the flavor's metadata or on the compute host somehow? If it should me on the compute host, so where exactly do I specify my 'capabilities' filter?
10:28:25 openstackgerrit Merged openstack/nova stable/ocata: Make request_spec.spec MediumText https://review.openstack.org/528332
10:28:31 openstackgerrit Merged openstack/nova master: Fix the formatting for 2.56 in the compute REST API history doc https://review.openstack.org/528114
10:41:02 lyarwood kashyap: http://logs.openstack.org/38/528338/4/check/legacy-tempest-dsvm-multinode-live-migration/d867726/logs/subnode-2/screen-n-cpu.txt.gz#_2017-12-18_20_20_13_894 - seeing this on stable/newton, LM failure for a single paused instance, looks like the remote libvirtd didn't respond in time, have you seen this before?
10:41:09 lyarwood kashyap: http://logs.openstack.org/38/528338/4/check/legacy-tempest-dsvm-multinode-live-migration/d867726/job-output.txt.gz#_2017-12-18_20_20_56_230121 is the tempest failure
10:42:04 kashyap lyarwood: Is this only stable/newton?
10:42:29 lyarwood kashyap: that's the only place I've seen it thus far
10:50:20 kashyap lyarwood: So I looked at all the logs, one thing that potentially jumps out at me is in the source QEMU log:

Earlier   Later