Posted	Nick	Remark
#openstack-nova - 2019-07-07
00:05:16	spatel	sean-k-mooney: can you take a look here https://bugs.launchpad.net/nova/+bug/1835637
00:57:46	openstackgerrit	Merged openstack/nova master: Set COMPUTE_STATUS_DISABLED trait from update_provider_tree flow https://review.opendev.org/668565
16:31:53	openstackgerrit	Ghanshyam Mann proposed openstack/nova master: Add test coverage of existing os-agents policies https://review.opendev.org/669578
22:05:59	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13) https://review.opendev.org/576020
22:06:11	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14) https://review.opendev.org/576027
22:06:25	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15) https://review.opendev.org/576031
22:06:43	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16) https://review.opendev.org/576299
22:06:59	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17) https://review.opendev.org/576344
22:07:17	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18) https://review.opendev.org/576673
22:07:34	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.opendev.org/576676
22:07:52	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.opendev.org/576689
22:08:10	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.opendev.org/576709
22:08:30	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.opendev.org/576712
22:08:51	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Fix cleaning up console tokens https://review.opendev.org/637716
#openstack-nova - 2019-07-08
00:39:20	openstackgerrit	Sundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access https://review.opendev.org/631242
00:39:21	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs. https://review.opendev.org/631244
00:39:21	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec. https://review.opendev.org/631243
00:39:22	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML. https://review.opendev.org/631245
02:35:09	openstackgerrit	Yongli He proposed openstack/nova master: clean up orphan instances https://review.opendev.org/627765
03:28:50	openstackgerrit	Boxiang Zhu proposed openstack/nova master: Support agile samples name https://review.opendev.org/669591
03:33:53	openstackgerrit	Sundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access https://review.opendev.org/631242
03:33:54	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs. https://review.opendev.org/631244
03:33:54	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec. https://review.opendev.org/631243
03:33:55	openstackgerrit	Sundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML. https://review.opendev.org/631245
03:43:28	prometheanfire	I'm guessing volumes showing up as attached in nova but not cinder (and not actually being attached) is a nova problem?
03:43:34	prometheanfire	can't 'remove volume' it No volume with a name or ID of '3e92f9b6-1a3b-4a7e-8487-6ff253e888db' exists.
03:50:11	prometheanfire	problem starts when attaching it, times out with a 504 :|
04:22:03	openstackgerrit	Takashi NATSUME proposed openstack/python-novaclient master: Deprecate cells v1 and extension commands and APIs https://review.opendev.org/669597
06:16:30	openstackgerrit	Arthur Dayne proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.opendev.org/623120
06:45:02	openstackgerrit	Merged openstack/nova master: Clean up test_virtapi https://review.opendev.org/667419
07:20:44	openstackgerrit	wangwei1 proposed openstack/nova master: fix spelling error in nova/api/validation/__init__.py https://review.opendev.org/669244
07:22:06	openstackgerrit	Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520
08:41:22	openstackgerrit	Merged openstack/nova master: Add VirtAPI.update_compute_provider_status https://review.opendev.org/668706
09:51:20	openstackgerrit	Brin Zhang proposed openstack/nova master: Specify availability_zone to unshelve https://review.opendev.org/663851
09:57:49	openstackgerrit	Miguel Ángel Herranz Trillo proposed openstack/nova stable/queens: Fix type error on call to mount device https://review.opendev.org/669629
10:16:06	moshele	@sean-k-mooney: hi
10:37:25	gokhani	hi team, because of power outage, Most of our compute nodes unexpectedly shut down and now I can not start our instances. Instances Power status is No State. Error log is http://paste.openstack.org/show/754107/. My environment is OpenStack Pike and Instances are on a nfs shared storage. Nova version is 16.1.6.dev2. There are more important instances on my environment. How can I rescue my istances? What would you suggest ?
11:19:25	openstackgerrit	Ivaylo Mitev proposed openstack/nova master: VMware VMDK detach: get adapter type from instance VM https://review.opendev.org/653738
11:56:19	openstackgerrit	Merged openstack/nova master: Correct the comment of RequestSpec's network_metadata https://review.opendev.org/667061
12:33:08	openstackgerrit	Brin Zhang proposed openstack/nova master: Specify availability_zone to unshelve https://review.opendev.org/663851
12:35:24	openstackgerrit	Shilpa Devharakar proposed openstack/nova master: Support filtering of hosts by forbidden aggregates https://review.opendev.org/667952
12:57:44	openstackgerrit	Merged openstack/os-resource-classes master: Add Python 3 Train unit tests https://review.opendev.org/669479
13:00:04	openstackgerrit	Merged openstack/os-traits master: Add Python 3 Train unit tests https://review.opendev.org/669480
13:25:41	openstackgerrit	Matt Riedemann proposed openstack/nova stable/rocky: Fix type error on call to mount device https://review.opendev.org/669664
13:41:51	bauzas	mriedem: around ?
13:42:01	bauzas	mriedem: I replied to the thread but I wonder about something
13:42:06	mriedem	yes
13:42:27	bauzas	in both http://paste.openstack.org/show/734146/ and https://github.com/larsks/os-placement-tools/blob/master/check_placement.py they first ask about all the instances
13:42:55	bauzas	and then they loop around allocations by checking some persisted object
13:43:05	bauzas	but then, we could have some races
13:43:20	bauzas	plus, it could be super huge to get all the instances for CERN eg.
13:43:36	bauzas	so, I wonder whether I should call the API for every instance
13:43:49	bauzas	erh
13:43:53	bauzas	I mean, checking the DB
13:46:03	mriedem	i'd think you'd avoid races by checking if an instance has a task_state != None, and if looking at migrations, is the migration in progress
13:48:09	mriedem	mnaser's script doesn't loop over instances,
13:48:27	mriedem	it gets hypervisors and the servers on those hypervisors and compares to the resource provider inventory/allocation per hypervisor/server
13:50:13	mriedem	i'd think it would be easiest to first determine what kinds of problems the audit command is going to try and find
13:50:29	mriedem	and then figure out the best way to implement that
13:51:08	mriedem	i think we know the two main issues are missing allocations (which heal_allocations should fix) and leaked / orphaned allocations, so i'd start by focusing on the latter issue
13:55:17	mriedem	i think we could pretty easily identify leaked allocations by starting from the provider allocations and working backward - looking for servers or migration records with the allocation consumer id (since we don't have the type recorded yet)
13:59:30	mriedem	so i'd probably start by getting all hypervisors (nodes/resource providers) and for each hypervisor, get the allocations - similar to what mnaser's script does
14:00:00	mriedem	getting the hypervisors + servers in the same call like his script would also tell you if allocations on that provider was a server or not - and if not, it's either leaked or it's a migration allocation
14:00:09	mriedem	so no i don't think you need to loop over all instances
14:00:18	mriedem	maybe i should just write this thing :)
14:06:37	bauzas	mriedem: I'm pretty sure I can do it
14:16:29	openstackgerrit	François Palin proposed openstack/nova master: WIP - call volume detach even if terminate_connection fails https://review.opendev.org/669674
14:19:01	kashyap	mriedem: You're right ... indeed I didn't hear any responses on the list so far (http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007521.html)
14:19:33	kashyap	alex_xu: Hiya, when you're about, do you have a comment on the above thread? (And the change wich Matt Cced you on, which removes Intel CMT events)
14:20:10	efried	kashyap: As predicted, my wife immediately stole the sleep book
14:20:20	efried	and it is life-changing
14:20:41	kashyap	efried: Hehe. Sharing is caring. I'm sure she will not hide her fascination with the book
14:20:56	efried	I don't know why, but stuff I've been telling her for years for some reason is having more of an impact coming from a complete stranger
14:20:57	kashyap	efried: Ah, she already finished it?
14:21:20	efried	no, hasn't finished yet, but every chapter brings new insight.
14:21:26	efried	she has bought a copy for her parents
14:21:31	efried	and recommended it to a number of people.
14:21:36	kashyap	:-)
14:21:49	efried	I got a couple chapters in before she stole it, and I'm definitely sold
14:21:57	kashyap	efried: I know, you must've become like a "broken record", and people zone out the moment broken reel start spinning :D
14:22:06	kashyap	Sorry, just teasing.
14:22:35	efried	though for me it's more fascination with the science than altering lifestyle, which was already pretty close to right sleep-wise.
14:23:07	kashyap	Yeah, agreed.
14:23:46	kashyap	efried: Also, I'd highly recommend to watch him give a tech talk. He's one of the most effective speakers I've ever seen.
14:24:01	efried	noted
14:24:08	kashyap	The way he pauses for the words to sink in, diction, is all worth observing. At least to me.
14:24:11	kashyap	https://www.youtube.com/watch?v=aXflBZXAucQ
14:24:42	kashyap	efried: If you click, look how quickly (within 5 seconds) he escalates the talk. :D
14:29:27	prometheanfire	was pointed here for nova adding a cinder volume to a server without (the record/db at least) but not actually adding it to the running VM (client reports a 504 when trying to add the volume)
14:30:28	prometheanfire	it shows up in the volumes_attached field, but can't remove any of them as they either do not exist or.....
14:30:32	prometheanfire	Invalid volume: Invalid input received: Invalid volume: Unable to detach volume. Volume status must be 'in-use' and attach_status must be 'attached' to detach. (HTTP 400) (Request-ID: req-01d8a3c5-66f4-43a4-bac5-9f1104a292fe) (HTTP 400) (Request-ID: req-358132e4-38a1-493a-b87b-d135791bae2d)
15:02:46	efried	It seems straightforward enough, but I'm not sure if there could e.g. be security problems, or if there's another accepted way to do this, etc.
15:02:46	efried	https://review.opendev.org/#/c/667975/
15:02:46	efried	kashyap: Would you mind taking a look at this please?
15:03:09	kashyap	efried: In a meeting; will look
15:03:15	efried	no hurry
15:03:22	efried	thanks
15:09:28	stephenfin	lyarwood: Could you send this on its merry way? https://review.opendev.org/#/c/667355/
15:11:04	lyarwood	stephenfin: looking
15:11:48	lyarwood	stephenfin: sorry I did mean to sort that out last week once the stein change landed

Earlier   Later