| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-01-25 | |||
| 15:39:22 | mdbooth | In Nova we typically do this by atomically changing task state. | |
| 15:40:09 | mriedem | mdbooth: they do that here https://github.com/openstack/cinder/blob/master/cinder/volume/api.py#L1699 | |
| 15:40:37 | mdbooth | So we'd do: if instance.status == 'all good': atomic_update(instance.task_state = 'doing my thang', expected task_state = 'whatever') | |
| 15:40:37 | jgriffith | mdbooth: We have a conditional on the volume object IIRC | |
| 15:41:11 | jgriffith | mdbooth: after that yeah we don't lock or anything if that's what you mean | |
| 15:41:26 | openstackgerrit | Jackie Truong proposed openstack/nova master: Implement certificate_utils https://review.openstack.org/479949 | |
| 15:41:26 | openstackgerrit | Jackie Truong proposed openstack/nova master: Add trusted_image_certificates to REST API https://review.openstack.org/486204 | |
| 15:41:53 | SpazZz | IBM CI looks like it's cleaning up.. can hopefully get the my +1 back and look sexier for the Core Reviewers | |
| 15:42:03 | SpazZz | Walk by and be like, "girlll look at all these +1's over here.." | |
| 15:42:50 | openstackgerrit | Jackie Truong proposed openstack/nova master: Add trusted_certs object https://review.openstack.org/489408 | |
| 15:43:12 | mdbooth | jgriffith: Ah, yes. So in this case we'd want to modify 'expected' on line 1685 to contain only available. | |
| 15:43:57 | mdbooth | Assuming conditional_update is an atomic CAS, that would completely close the race window. | |
| 15:44:13 | mdbooth | But yeah, it's currently very short. | |
| 15:47:22 | jgriffith | mdbooth: yeah, IMO there's probably going to be some additions/fixes that are more critical to this before we get to things like closing that up. | |
| 15:48:03 | mdbooth | jgriffith: Easy to close, hard to spot... | |
| 16:02:44 | openstackgerrit | Brianna Poulos proposed openstack/nova master: Reduce complexity of _from_db_object https://review.openstack.org/537728 | |
| 16:11:20 | Tengu | hello, anyone can tell me what the error "NovaException: Unsupported VIF type unbound convert '_nova_to_osvif_vif_unbound'" means? it apparently prevents launching a new instance in a specific project/tenant on openstack pike. | |
| 16:11:50 | mriedem | Tengu: probably means an unexpected vif type for the port and nova doesn't know how to handle it | |
| 16:11:53 | mriedem | sean-k-mooney: ^ | |
| 16:12:13 | Tengu | mriedem: hmm. weird thing is: this happens only in one project :/. | |
| 16:12:21 | bpoulos | giodeco: The checksum error you're seeing isn't related to image signature verification. It looks like it's a Glance Exception raised if the MD5 checksum of the image isn't as expected (signature verification doesn't use MD5). See http://git.openstack.org/cgit/openstack/python-glanceclient/tree/glanceclient/common/utils.py#n415 | |
| 16:12:27 | mriedem | Tengu: then i don't know | |
| 16:12:31 | Tengu | and I didn't change anything in the configuration :/. | |
| 16:12:41 | Tengu | might it be related to some kind of quota? | |
| 16:12:49 | mriedem | not on the nova side | |
| 16:12:54 | Tengu | hmm. | |
| 16:13:02 | Tengu | shall I ping on neutron channel? | |
| 16:13:27 | mriedem | http://codesearch.openstack.org/?q=Unsupported%20VIF%20type&i=nope&files=&repos= | |
| 16:13:57 | Tengu | hmmm, nova-network is deprecated and not in use anymore in pike, is it? | |
| 16:14:08 | mriedem | this isn't nova-network | |
| 16:14:17 | Tengu | oh. | |
| 16:14:29 | mriedem | the libvirt driver in nova needs to know how to handle the vif type to setup the guest xml properly when attaching the network interface | |
| 16:15:03 | Tengu | hmm. | |
| 16:15:28 | Tengu | if it was for all project in the openstack deploy, I'd say "due to update"… but this isn't the case. | |
| 16:15:46 | mriedem | what is the vif type? the error is saying the vif type is "unbound" for some reason | |
| 16:15:47 | mriedem | which isn't correct | |
| 16:15:48 | sean-k-mooney | mriedem: it means some how the ovs_vif_utill.py fucntion with a neutron port that we have not done port binding on yet | |
| 16:16:06 | sean-k-mooney | mriedem: e.g. vif_unbound is the state a port is in before it is added to a vm | |
| 16:16:15 | Tengu | mriedem: how may I check that? | |
| 16:16:19 | mriedem | Tengu: check the neutron logs for an error with port binding | |
| 16:16:27 | mriedem | it's probably a port binding failure on the neutron side | |
| 16:16:31 | mriedem | causing a side effect issue in nova | |
| 16:16:43 | mriedem | which could possibly be due to quota in neutron, idk | |
| 16:17:09 | Tengu | mriedem: hmm ok. I'll check on the neutron channel then. | |
| 16:17:20 | ildikov | jgriffith: mriedem: smcginnis: jungleboyj: sorry, I admit I'm a bit more disorganized this week than I expected :/ | |
| 16:17:30 | ildikov | jgriffith: mriedem: smcginnis: jungleboyj: shall we have a short meeting? | |
| 16:17:32 | Tengu | mriedem: thank you for your support :). | |
| 16:18:27 | mriedem | ildikov: i'd like to skip this week if possible | |
| 16:18:34 | mriedem | lots of stuff to deal with today | |
| 16:18:41 | mriedem | Tengu: np | |
| 16:18:57 | ildikov | mriedem: all good, just wanted to check in whether there's anything we should talk about today or we can skip | |
| 16:19:05 | ildikov | mriedem: tnx | |
| 16:23:54 | sean-k-mooney | mriedem: if it was a port binding failure in neutron it should be VIF_BINDING_FAILED not unbound | |
| 16:25:34 | openstackgerrit | melanie witt proposed openstack/nova master: Add release note for QEMU native LUKS decryption https://review.openstack.org/537642 | |
| 16:27:31 | openstackgerrit | Brianna Poulos proposed openstack/nova master: Add trusted_certs to instance_extra https://review.openstack.org/537897 | |
| 16:27:31 | openstackgerrit | Brianna Poulos proposed openstack/nova master: Add trusted_certs object https://review.openstack.org/489408 | |
| 16:27:32 | openstackgerrit | Brianna Poulos proposed openstack/nova master: Implement certificate_utils https://review.openstack.org/479949 | |
| 16:27:32 | openstackgerrit | Brianna Poulos proposed openstack/nova master: Add trusted_image_certificates to REST API https://review.openstack.org/486204 | |
| 16:27:51 | mriedem | gmann: here is the patch that adds the nova-multiattach job to tempest: https://review.openstack.org/#/c/537957/ | |
| 16:30:44 | Tengu | sahid: hello! are you here? | |
| 16:32:52 | efried | jaypipes I've now noticed that weird stalling behavior without having rechecked anything nearby, so it was probably just coincidence. I still don't like it, though. | |
| 16:33:33 | Tengu | sean-k-mooney: hello! are you here? | |
| 16:34:16 | Tengu | mriedem: I was sent back here in order to get info from either sahid or sean-k-mooney - as they are the devs of the os-vif-core :). Pretty sure they will know a bit more about my issue. | |
| 16:35:28 | Tengu | :) | |
| 16:45:36 | efried | gibi stephenfin If you're still around, care to push this 'un? https://review.openstack.org/#/c/536624/ | |
| 16:47:58 | efried | or mriedem dansmith if you don't mind jumping into the middle of this series. The change itself is fairly small and straightforward, though understanding how and where it fits in is a bigger job. | |
| 16:49:45 | ameeda | gmann: can you please check this "https://review.openstack.org/#/c/526900/" ? | |
| 16:50:36 | stephenfin | efried: Yeah, I can grab that | |
| 16:50:41 | efried | stephenfin Thanks! | |
| 16:51:00 | mriedem | looking | |
| 16:51:04 | mriedem | why was it using sets? | |
| 16:51:14 | gibi | efried: done | |
| 16:51:16 | mriedem | and are there problems if we're not ensuring uniqueness now? | |
| 16:51:31 | efried | gibi Thanks! stephenfin ^ | |
| 16:51:36 | gibi | stephenfin: sorry | |
| 16:51:47 | stephenfin | gibi: Nope, suits me :) | |
| 16:51:49 | efried | mriedem The only real reason it was using sets before was for O(1) operations. | |
| 16:51:59 | stephenfin | bauzas has been bugging me about this vGPU thing anyway | |
| 16:52:10 | mriedem | stephenfin: the vgpu stuff is all approved | |
| 16:52:14 | efried | mriedem And as super-double-insurance that we don't have cycles in the "tree". But that's prevented elsewise in a number of ways. | |
| 16:52:16 | stephenfin | Ha! | |
| 16:52:22 | stephenfin | I should work on bugs more often | |
| 16:52:25 | mriedem | god this provider tree stuff, | |
| 16:52:31 | stephenfin | Everyone does my work for me | |
| 16:52:43 | mriedem | all reminds me of some graph traversal stuff i wrote like 10 years ago at ibm | |
| 16:52:54 | efried | mriedem But the trees should be small enough that O(lognN) is no big deal, and is a rounding error anyway against all the placement API calls that feed it. | |
| 16:52:57 | mriedem | back when i was young and smart | |
| 16:53:20 | efried | Not sure how that makes me feel, considering I'm older than you (pretty sure) | |
| 16:53:36 | mriedem | <- 36 | |
| 16:53:40 | efried | 41 | |
| 16:53:44 | mriedem | jesus you're old | |
| 16:53:47 | efried | ikr | |
| 16:53:54 | efried | Man, when I was 36 I could do anything. | |
| 16:54:07 | efried | Now I sound like a bowl of rice krispies getting out of bed. | |
| 16:55:25 | efried | So anyway, I think I now have 8 patches at the mercy of zuul. Bottom one of that series has been thrashing around for three full days. | |
| 16:55:36 | mriedem | ooo nice osc-placement docs are published https://docs.openstack.org/osc-placement/latest/ | |
| 16:57:40 | mriedem | and releasenotes, although the version isn't what i expected https://docs.openstack.org/releasenotes/osc-placement/unreleased.html | |
| 16:59:16 | edmondsw | stephenfin if you're looking for something to review... :) https://review.openstack.org/#/c/526094/ | |
| 16:59:49 | stephenfin | edmondsw: Darn, I thought I'd got away with the powerVM stuff | |
| 17:00:01 | edmondsw | and they just reel ya back in... | |