Earlier  
Posted Nick Remark
#openstack-nova - 2018-06-14
13:59:06 mriedem jmlowe: link?
13:59:17 jmlowe karma 1, so it may never see the light of day
13:59:30 mriedem jmlowe: might still be good to put into our troubleshooting docs
13:59:47 mriedem since we probably don't leverage the fact we have those at all enough
13:59:51 jmlowe absolutely
14:00:16 jmlowe https://ask.openstack.org/en/question/114805/why-is-nova-ignoring-microvesions/#114806
14:00:20 mriedem artom: i plan on getting to it eventually, just busy atm
14:00:24 mriedem jmlowe: thanks
14:00:31 artom mriedem, heh, no worries :)
14:00:46 jmlowe also the follow up https://ask.openstack.org/en/question/114808/why-is-nova-cli-not-using-https/#114809
14:01:48 mriedem jmlowe: i keep getting a "Sorry, this content is not available" error on the first one,
14:01:55 mriedem maybe it has to go through screening first
14:02:00 mriedem to de-pence-ify it
14:02:03 mriedem i know you're in indiana
14:02:11 jmlowe right, awaiting moderator approval
14:02:20 jmlowe too soon
14:02:21 sahid artom: i don't want to make any troubles on your implementation, it's just if we can reuse what we already have that will limit the code introduced,
14:02:25 jmlowe :)
14:02:30 sahid also when it will be the time to drop claim, we could think of that in one step, everything will be grouped
14:02:57 sahid but if there is already a preferece for a new impl, i will remove my -1
14:03:06 artom sahid, heh, I'm just trying to find the balance between doing it right and getting it merged
14:03:16 sahid artom: yes i guess :)
14:03:35 artom Given that https://review.openstack.org/#/c/244489/ has languished in review purgatory for literally *years*, maybe claims isn't the most mergeable way of doing it ;)
14:03:41 sahid artom: have a look at what i suggested, that should be really easy to implement
14:04:10 sahid artom: it's because it's all in one patch, if you can make it comprhensible i guess that will help
14:04:20 artom sahid, in the interest of good faith, I will :)
14:04:30 sahid so you can focus on updating the guest domain XML
14:04:52 artom But the argument of "it's all already a mess with no claims and resource tracking, so just making it suck less with NUMA" is pretty strong as wlel
14:05:21 stephenfin Random question: is there a way to rerun only the tests that failed on the last run? I recall this being a ((o)s)testr feature
14:05:27 stephenfin efried, mdbooth: ^ ?
14:05:49 efried stephenfin: You mean from gerrit or locally?
14:05:56 efried stephenfin: (In either case, I have no idea :)
14:06:01 stephenfin Locally
14:06:08 jmlowe mriedem: tossed out a request for an ask openstack moderator in #openstack, maybe I'll find one
14:06:10 efried stephenfin: If it's a *testr thing, mtreinish would be the SME I would call on.
14:06:13 stephenfin darn, where's mtreinish when you need him
14:06:16 stephenfin jinx
14:11:16 mriedem dansmith: see my comment on this pike backport for the build failure weigher - we'll need to handle the ironic host manager fallout there somehow https://review.openstack.org/#/c/573248/
14:11:41 dansmith mriedem: we already merged something for that
14:12:02 mriedem i know, on queens
14:12:03 dansmith mriedem: https://review.openstack.org/#/c/574997/
14:12:06 mriedem we just have to do the dance for pike
14:12:08 dansmith yep
14:12:08 dansmith oh kay
14:15:16 mriedem tssurya: we can also be fixing the instance list 500 error as a bug fix today
14:15:23 mriedem regardless of the handling a down cell spec
14:15:42 mriedem tssurya: if you haven't started a fix for that, maybe dansmith wants to take a crack at it?
14:16:13 tssurya mriedem: you mean this one ? -> https://bugs.launchpad.net/nova/+bug/1773945
14:16:14 openstack Launchpad bug 1773945 in OpenStack Compute (nova) "nova client servers.list crashes with bad marker" [Medium,Triaged] - Assigned to Surya Seetharaman (tssurya)
14:16:48 tssurya or the general one as a part of handling down cell
14:16:49 mriedem tssurya: no
14:16:52 mriedem the general one
14:17:02 dansmith I'm confused, isn't tssurya working on the general one?
14:17:03 mriedem tssurya: if you don't have a patch for that ^ bug about the marker, i can push something for that
14:17:22 mriedem she's working on the handling a down cell alternative i thought
14:17:24 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add notification support for trusted_certs https://review.openstack.org/563269
14:17:25 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add certificate validation docs https://review.openstack.org/560158
14:17:26 openstackgerrit Balazs Gibizer proposed openstack/nova master: WIP: Add trusted certs to feature support matrix docs https://review.openstack.org/574890
14:17:27 openstackgerrit Balazs Gibizer proposed openstack/nova master: Remove max_size parameter from fake_libvirt_utils.fetch_*image methods https://review.openstack.org/574911
14:17:31 mriedem dansmith: you likely need to read the spec to get caught up
14:17:40 tssurya okay I am working on both :D
14:17:56 dansmith mriedem: shame accepted
14:18:02 mriedem ha
14:18:06 mriedem sorry
14:18:25 mriedem just trying to not get backed up
14:18:29 dansmith it's not like I'm twiddling my thumbs around here
14:18:55 gibi bauzas, mriedem: updated with the fixes https://review.openstack.org/563269
14:19:10 mriedem my point is, if dansmith and/or i can help out with the other known things we know we can fix today, let's do that while tssurya works on the handling a down cell alternative poc
14:19:10 tssurya haha, :) I will try to put something up this week (after I finish some downstream work), sorry for the delay
14:19:29 mriedem gibi: acked, in the tab queue
14:21:25 dansmith cdent: new macbook pro keyboard failure?
14:21:33 cdent totes
14:21:36 cdent they suck
14:21:40 dansmith bummer :(
14:30:59 artom sahid, the claim would have to done on the destination once we're sure the migration is really happening (ie, after all the checks), right?
14:32:08 openstackgerrit Chris Dent proposed openstack/nova master: [placement] Add status and links fields to version document at / https://review.openstack.org/575117
14:32:45 sahid artom: hum... which checks are you talking? the claim should be done just after that the scheduling find a destination
14:33:06 sahid scheduler
14:33:24 artom sahid, dammit, I need to find the actual functions how
14:33:25 artom ;)
14:33:36 artom The _check_can_live_migrate stuff
14:34:24 artom I'm asking because in the resource tracker, we do _claim_existing_migration if a Migration already exists, and set the dest node to "ourselves"
14:34:38 artom So, presumably, we have to be sure we're actually doing to receive the instance
14:35:02 mtreinish stephenfin, efried: is stestr run --failing what you're looking for? https://stestr.readthedocs.io/en/latest/MANUAL.html#running-previously-failed-tests
14:35:06 artom And that we're not going to fail a check right after claiming the existing migration
14:35:38 openstackgerrit Dan Smith proposed openstack/nova stable/pike: Change consecutive build failure limit to a weigher https://review.openstack.org/573248
14:35:46 stephenfin mtreinish: It would appear so. Excellent
14:35:54 stephenfin mtreinish: Thanks :)
14:36:53 mtreinish sure, np
14:38:49 mriedem well look who decides to show up
14:38:58 mriedem when testr talk is happening but not when the gate is burning down
14:39:40 mtreinish heh, well complain to my mgt I had to sit in a booth all day yesteday to talk about IBM cloud
14:40:18 mtreinish although, the funny thing is I only got questions about AIX and Z. no one cared about the cloud
14:40:26 mriedem AIX?
14:40:31 mriedem i could maybe understand Z
14:40:57 mtreinish apparently people are still using aix, I was very confused too
14:41:09 mriedem and as400, die hards
14:41:11 efried Because it is still awesome.
14:41:12 dansmith mtreinish: all those people that bought 25 year licenses
14:41:24 cdent second worst unix imp

Earlier   Later