Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-07-28
17:11:02 cdent cool, thanks leakypipes, I figured as much but wanted to be sure
17:11:54 sdague also... evacuate bugs... zomg
17:11:59 melwitt sdague: you are a champion
17:12:31 cdent gerrit hates me
17:13:15 cdent voila
17:13:18 superdan cdent: hates everyone apparently
17:13:23 superdan *it hates
17:13:29 cdent s/://
17:13:37 superdan well, I suspected, but
17:13:49 melwitt yeah, gerrit hates us all. it's not you
17:15:21 cfriesen_ review.openstack.org is down?
17:15:52 cfriesen_ never mind, just saw the note
17:19:46 openstack bug 1669054 in OpenStack Compute (nova) "RequestSpec.ignore_hosts from resize is reused in subsequent evacuate" [Undecided,Opinion] https://launchpad.net/bugs/1669054
17:19:46 cfriesen_ sdague: arguably bug 1669054 is not opinion...if CONF.allow_resize_to_same_host is False and we do a resize then a subsequent rebuild/evacuate, it will continue to ignore the original host.
17:20:09 cfriesen_ sdague: the only "might" is around exactly where to do the fix
17:23:55 openstackgerrit Peter Hamilton proposed openstack/nova-specs master: Add support for certificate validation https://review.openstack.org/488541
17:26:34 openstackgerrit melanie witt proposed openstack/nova master: Detach device from live domain even if not found on persistent https://review.openstack.org/488545
17:34:27 openstackgerrit Peter Hamilton proposed openstack/nova-specs master: Add support for certificate validation https://review.openstack.org/488541
17:40:16 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
17:54:28 openstackgerrit Dan Smith proposed openstack/nova master: Add some more cellsv2 doc goodness https://review.openstack.org/487183
17:59:50 sdague cfriesen_: Opinion often means bring it back in via the specs process. Did I not do that with this one?
18:00:11 sdague cfriesen_: if you want it confirmed / medium, that's fine as well, but that ends up being kind of a different black hole.
18:00:49 sdague cfriesen_: trying to make every open bug actionable
18:01:00 sdague might and may are not really actionable
18:01:11 openstackgerrit Jay Pipes proposed openstack/nova master: remove source provider allocs in confirm_resize() https://review.openstack.org/488510
18:01:30 leakypipes superdan, figleaf: updated &
18:01:33 leakypipes ^^
18:02:24 openstackgerrit Dan Smith proposed openstack/nova master: Add some more cellsv2 doc goodness https://review.openstack.org/487183
18:02:25 superdan leakypipes: fixed ^
18:04:01 leakypipes superdan: +2
18:04:06 superdan tys
18:10:58 cdent ah buckets, dan gets in the revision while I’m reviewing the cellsv2 doc goodness
18:11:04 melwitt superdan: thanks for writing that up, complete with diagrams! since I've been thinking about consoles, I'm thinking maybe I can add onto that with mention of nova-consoleauth and the websocketproxies similar to "Neutron Metadata API proxy"?
18:54:17 cfriesen_ jaypipes: would https://review.openstack.org/#/c/339715 still be an issue with the new placement/allocations stuff? (i.e should I bother refreshing it or will it be handled already?)
18:55:32 cfriesen_ sdague: in this case the "might" was for a possibly way to fix it. The bug exists, that is not in question.
19:00:12 leakypipes cfriesen_: no, I don't think so. different issue.
19:00:33 leakypipes cfriesen_: I think you can revamp that patch, address the comments from Matt.
19:12:30 openstackgerrit Ed Leafe proposed openstack/nova master: Handle hash ring rebalancing in ironic flavor migration https://review.openstack.org/487954
19:14:07 openstackgerrit Eric Fried proposed openstack/nova master: nova.utils.get_endpoint_data() https://review.openstack.org/488137
19:34:40 fried_rice mriedem https://review.openstack.org/#/c/488034/ (g-r bump) is verified now.
19:41:14 openstack Launchpad bug 1707284 in OpenStack Compute (nova) "Extend attached volume fails with "VolumePathsNotFound: Could not find any paths for the volume." in os-brick iscsi connector" [Medium,Confirmed]
19:41:14 mriedem mgagne: https://bugs.launchpad.net/nova/+bug/1707284
19:41:28 mgagne mriedem: hi
19:47:18 mgagne mriedem: could it be a redheering ? I'm not familiar with os-bricks and friends but right above, you can read "iscsiadm: No active sessions" and u'target_discovered': False in the bdm dump. that's what I found at first glance
19:53:17 hongbin hi folks, i want to confirm that if i create an instance with an existing port and a security group, the security group should be added to the existing port or not?
19:55:18 hongbin or the security group should override the port's security group?
20:03:37 mgagne mriedem: I'm having a hard time debugging the logic, there are missing debug logs from os-brick, especially around calls to _iterate_all_targets from _get_potential_volume_paths in os_brick/initiator/connectors/iscsi.py
20:05:36 openstackgerrit Jay Pipes proposed openstack/nova master: placement: don't allocate on compute nodes https://review.openstack.org/488595
20:06:01 leakypipes mriedem, superdan, figleaf, bauwser: mind blown.... ^
20:06:51 openstack Launchpad bug 1707256 in OpenStack Compute (nova) "Scheduler report client does not account for shared resource providers" [High,Confirmed] - Assigned to Jay Pipes (jaypipes)
20:06:51 leakypipes mriedem: and that takes care of https://bugs.launchpad.net/nova/+bug/1707256 actually. :)
20:07:13 superdan leakypipes: um, what?
20:07:24 superdan leakypipes: who un-doubles the move allocation?
20:07:29 leakypipes mriedem: by removing the compute node/resource tracker from all allocation operations, we kind of just remove the whole "is this shared or not" problem on the compute node.
20:07:43 leakypipes superdan: that's done in the dependent patch.
20:07:58 leakypipes superdan: https://review.openstack.org/#/c/488510/3
20:08:25 leakypipes superdan: so that's the only place on the compute node that will update allocations.
20:08:33 superdan ...okay
20:09:04 superdan leakypipes: so while we're upgrading,
20:09:35 superdan ocata computes will alter/delete the scheduler allocation, and we'll never heal it on pike computes, right? so how do we ensure it heals if it gets damaged?
20:09:46 leakypipes superdan: "mind blown" was referring to my own mind being blown. :) Basically, the patch makes the resource tracker look like what I wanted it to look like once placement-claims was complete. i.e. don't have it mucking with claims/allocations at all.
20:10:07 superdan yeah, I got it
20:10:14 superdan still not sure we can go that far yet
20:11:08 superdan maybe we should hangout to discuss?
20:11:16 leakypipes superdan: still haven't gotten that far in mind yet :) I could go for a hangout walkthrough of ideas. that last patch was more a "let's see what happens" patch than anything else :)
20:11:25 openstackgerrit Hongbin Lu proposed openstack/nova master: Handle exception on adding secgroup https://review.openstack.org/465173
20:11:44 superdan oh okay, I thought you were suggesting that we do that for pike to eliminate these problems
20:11:53 leakypipes superdan: nah
20:11:57 superdan okay
20:11:57 superdan "let's see what happens in the gate" isn't going to convince me
20:12:25 leakypipes superdan: in any case, I would be good for a hangout.
20:12:31 leakypipes would be useful to talk through some of this.
20:15:03 mgagne mriedem: ok, I think there is a bug in os-brick. When retrieve the iscsi sessions here: https://github.com/openstack/os-brick/blob/1.15.1/os_brick/initiator/connectors/iscsi.py#L247
20:15:04 mgagne That's my hypothesis on what's happening.
20:15:04 mgagne So I'm not sure how this value is useful for the logic below which compares the bdm target_portal against the above value. In the end, you will always end up with an empty host_devices list.
20:15:04 mgagne Below, it tries to do something I don't fully understand. But iscsi_portals_with_sessions will end up with the value ['.']
20:15:04 mgagne The returned value should look like so: ['10.0.1.24:3260']
20:18:55 mgagne I think it got broken by this refactor despite the comment in the commit "It's worth mentioning that this patch does not touch the extend operation.": https://github.com/openstack/os-brick/commit/56c8665d3d342ce90f5d9433966c0f244063b4c1
20:32:08 hongbin hi, if i create a vm with an existing neutron port and a security group, the security group is ignored, i wonder why not populating the port with the specified sg?
20:43:47 openstackgerrit Merged openstack/nova master: Provide original fault message when BFV fails https://review.openstack.org/467715
21:04:19 openstackgerrit OpenStack Release Bot proposed openstack/os-vif master: Update reno for stable/pike https://review.openstack.org/488671
21:05:14 openstackgerrit Merged openstack/nova master: Updated from global requirements https://review.openstack.org/488034
21:07:48 openstackgerrit OpenStack Release Bot proposed openstack/python-novaclient master: Update reno for stable/pike https://review.openstack.org/488799
21:43:15 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/488865
21:51:00 openstackgerrit Ed Leafe proposed openstack/nova master: Clarifying node_uuid usage in ironic driver. https://review.openstack.org/485803
21:56:36 openstackgerrit Merged openstack/nova master: [placement] quash unicode warning with shared provider https://review.openstack.org/488363
22:25:12 openstackgerrit Eric Fried proposed openstack/nova master: nova.utils.get_endpoint_data() https://review.openstack.org/488137
#openstack-nova - 2017-07-29
02:37:29 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/488865
09:12:04 openstack bug 1454515 in OpenStack Compute (nova) "Property "instance.disable_terminate" is always "False" and never actually used." [Low,Confirmed] https://launchpad.net/bugs/1454515 - Assigned to Khushbuparakh (khushbuparakh)
09:12:04 openstackgerrit khushbu parakh proposed openstack/nova master: Closes-Bug: #1454515 https://review.openstack.org/488941
09:15:05 khushbu_ hi
09:17:01 openstack Launchpad bug 1454515 in OpenStack Compute (nova) "Property "instance.disable_terminate" is always "False" and never actually used." [Low,In progress] - Assigned to Khushbuparakh (khushbuparakh)
09:17:01 khushbu_ https://review.openstack.org/#/c/488941/ I submitted a review request for https://bugs.launchpad.net/nova/+bug/1454515 This patch uses the second method. If some one can review it
11:56:38 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.openstack.org/477091
12:34:30 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
14:55:31 openstackgerrit Hongbin Lu proposed openstack/nova master: [WIP] Apply security groups to existing port https://review.openstack.org/488956
15:14:14 openstack Launchpad bug 1629046 in OpenStack Compute (nova) "Errors about multiple networks pollutes functional test output" [Low,Confirmed] - Assigned to Khushbuparakh (khushbuparakh)
15:14:14 khushbu_ hi #channel I am trying to find out the actual error for my tests to fail but instead of that. I can see lot of unwanted Captured stderr failure traceback. thr is also a bug report https://bugs.launchpad.net/nova/+bug/1629046
15:14:46 khushbu_ what would be a good approach to solve this
#openstack-nova - 2017-07-30
10:58:17 openstackgerrit Spencer Yu proposed openstack/python-novaclient master: Nova client should retry with Retry-After value https://review.openstack.org/447766

Earlier   Later