| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-04-24 | |||
| 06:06:01 | gibi | good morning | |
| 06:06:17 | gibi | melwitt: thanks for checking the RC1 release patch | |
| 07:08:38 | bauzas | good morning Nova | |
| 07:37:47 | openstackgerrit | Kevin Zhao proposed openstack/nova master: [WIP] CI: add tempest-integrated-compute-aarch64 job https://review.opendev.org/714439 | |
| 08:04:57 | bauzas | gibi: have you triaged some bugs ? | |
| 08:10:21 | bauzas | lyarwood: permission to close this bug ? https://bugs.launchpad.net/nova/+bug/1738297 | |
| 08:10:21 | openstack | Launchpad bug 1738297 in OpenStack Compute (nova) "Nova Destroys Local Disks for Instance with Broken iSCSI Connection to Cinder Volume Upon Resume from Suspend" [Undecided,New] | |
| 08:11:22 | bauzas | looks to me that suspend after host reboot is not available (but there is a conf flag for resuming the guests upon reboot the reporter should use) and since nova no longer deletes the ephemeral files, I don't think there is anything to resolve | |
| 08:13:45 | gibi | bauzas: nope, sorry | |
| 08:14:00 | bauzas | okay it's weird then | |
| 08:14:10 | gibi | bauzas: we lost bugs? | |
| 08:14:18 | bauzas | I was seeing 50 open bugs this morning and now there are only 44 | |
| 08:14:24 | bauzas | 6 just gone | |
| 08:14:32 | gibi | interesting | |
| 08:14:35 | bauzas | but meh, it's maybe PEBKAC | |
| 08:14:49 | bauzas | anyway, moving on | |
| 08:15:03 | gibi | I have a tab open with 52 new bugs | |
| 08:15:37 | gibi | so we can compare | |
| 08:16:16 | gibi | i haven refreshed that tab since last evening | |
| 08:16:38 | bauzas | https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New | |
| 08:16:44 | bauzas | ^ gives me 44 opens | |
| 08:17:58 | bauzas | (and gosh, it's nearly impossible to triage Newton bugs) | |
| 08:18:07 | bauzas | the code is so old | |
| 08:18:28 | gibi | bauzas: artom triaged some https://bugs.launchpad.net/nova/+bug/1836681 | |
| 08:18:28 | openstack | Launchpad bug 1836681 in OpenStack Compute (nova) "attach volume succeeded but device not found on guest machine" [Undecided,Incomplete] | |
| 08:18:41 | lyarwood | bauzas: permission granted, fire. | |
| 08:18:41 | bauzas | that'd explain then | |
| 08:18:53 | bauzas | lyarwood: ack thanks, easy peasy | |
| 08:19:28 | gibi | bauzas: after refresh I see 46 on that list | |
| 08:21:24 | bauzas | gibi: lol, I only see 44 with a refresh | |
| 08:21:26 | bauzas | brain split ! | |
| 08:22:01 | gibi | bauzas: I might see private bugs you dont ? | |
| 08:22:25 | bauzas | gibi: possibly | |
| 08:22:29 | bauzas | you have powers. | |
| 08:22:57 | bauzas | (and that'd explain why I was saying 51 and you 53 on the nova meeting :p ) | |
| 08:23:55 | bauzas | gibi: I'm not part of the nova VMT but you could have been added since you wear the leader hat | |
| 08:26:31 | bauzas | gibi: mmm, you aren't in the coresec team https://launchpad.net/~nova-coresec | |
| 09:08:03 | aarents | Hi nova | |
| 09:08:33 | aarents | kashyap: lyarwood to followup yesterday chat regarding machine type and live-migration issue, I recover our story: | |
| 09:08:55 | aarents | we follow Ubuntu LTS qemu (and their machine-type without pinning it in conf) no issue here. One day, a guy introduce a no LTS qemu propably for fixing a bug ← this was a mistake, When we go back later to newer LTS qemu that did not support this machine type, we discover the issue, and we had to rebuild the newer LTS qemu with the support of this machine type in order to avoid hard reboot.. | |
| 09:18:28 | openstackgerrit | OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.opendev.org/722644 | |
| 09:19:14 | lyarwood | aarents: yeah as the non-LTS version likely jumped forward | |
| 09:19:51 | aarents | yep | |
| 09:20:23 | kashyap | aarents: Yeah, that's the cost of "you're on your own" non-LTS variants :) | |
| 09:20:43 | kashyap | There's water under your feet before you realize | |
| 09:20:53 | aarents | exacly :p | |
| 09:21:21 | kashyap | (Not necessarily bad, some people like to 'enjoy' debugging such needless water. ;-)) | |
| 09:26:30 | brinzhang_ | lyarwood, gibi: Our cloud used Rocky version, we want to upgrade to the latest version, do you have some documents to see? | |
| 09:27:06 | openstackgerrit | Takashi Natsume proposed openstack/nova master: Update contributor guide for Victoria https://review.opendev.org/722647 | |
| 09:28:00 | brinzhang_ | lyarwood, gibi: one way is upgrade all openstack project, nova/cinder/neutron/glance/manila/... and so on. Another way is just only upgrade nova/cinder/neutron/glance the mainly project | |
| 09:28:45 | brinzhang_ | above two way, anyone is better based on your experience? | |
| 09:29:41 | lyarwood | brinzhang_: depends on your deployment tooling really but rolling upgrades through each release are the best approach | |
| 09:30:10 | lyarwood | brinzhang_: so rocky to stein, stein to train, train to ussuri etc. | |
| 09:30:18 | brinzhang_ | lyarwood: we used kolla to deploy | |
| 09:30:19 | lyarwood | brinzhang_: and that's for everything | |
| 09:31:02 | brinzhang_ | It cannot upgrade from rocky to ussuri? jump stein and train? | |
| 09:31:39 | lyarwood | brinzhang_: AFAIK no, Kolla rolls through each release https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html#upgrade-procedure | |
| 09:32:11 | brinzhang_ | lyarwood: ack, I will see this docs later | |
| 09:32:59 | brinzhang_ | your suggestion that we should step by step to upgrade (rocky to stein, stein to train, train to ussuri), right? | |
| 09:33:57 | lyarwood | brinzhang_: yes with kolla I think that's your only option | |
| 09:34:12 | lyarwood | brinzhang_: but you might want to ask that team :) | |
| 09:34:17 | lyarwood | brinzhang_: or sean-k-mooney ;) | |
| 09:35:16 | brinzhang_ | lyarwood: thanks, got it, if there are some question before upgrade, I will ask sean-k-mooney or kolla team ^^ | |
| 09:38:12 | brinzhang_ | I just only care of the placement, upgrade Rocky version, the placement was splite from nova, will this be affected? | |
| 09:39:49 | openstackgerrit | Wenping Song proposed openstack/nova master: error may occur when filter scheduler with accelerator https://review.opendev.org/722651 | |
| 09:40:42 | lyarwood | brinzhang_: questions for the kolla folks, I'm sure they handle that as part of the upgrade. | |
| 09:40:56 | lyarwood | actually I know they do as I think I helped them with that while working on the TripleO part | |
| 09:42:54 | bauzas | brinzhang_: aarents: btw. welcome in our subteam ! | |
| 09:44:35 | aarents | bauzas: thanks | |
| 09:49:39 | brinzhang_ | lyarwood: yeah, good to know this, thank you very much | |
| 09:49:57 | bauzas | I think kolla supports rolling upgrades | |
| 09:50:49 | lyarwood | yeah I think brinzhang_'s last question was about placement extraction that they also support AFAIK | |
| 09:51:23 | brinzhang_ | bauzas: from the kolla upgrade docs, it seems that can support, I will looked into the docs, and than have a decision | |
| 09:51:37 | lyarwood | cool, good luck :) | |
| 09:52:55 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Use compression by default for 'SshDriver' https://review.opendev.org/684393 | |
| 09:56:19 | openstackgerrit | Stephen Finucane proposed openstack/nova master: objects: Add MigrationTypeField https://review.opendev.org/706013 | |
| 09:58:19 | openstackgerrit | Stephen Finucane proposed openstack/nova master: libvirt: Remove MIN_LIBVIRT_MULTIATTACH https://review.opendev.org/710238 | |
| 10:22:26 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Rework how we check for neutron extensions https://review.opendev.org/705792 | |
| 10:39:15 | zigo | When building Nova for buster-backports, I get 26 failures of this kind: | |
| 10:39:15 | zigo | http://paste.openstack.org/show/792658/ | |
| 10:39:32 | zigo | Does anyone have an idea of what's going on? | |
| 10:40:40 | lyarwood | zigo: what's buster-backports? | |
| 10:40:51 | lyarwood | Debian? | |
| 10:40:58 | zigo | lyarwood: OpenStack Stable backported to Debian stable. | |
| 10:40:59 | zigo | Yeah. | |
| 10:41:09 | lyarwood | zigo: which branch of OpenStack? | |
| 10:41:15 | zigo | lyarwood: Ussuri RC1. | |
| 10:41:38 | lyarwood | zigo: do you have a source tree somewhere or are you just using the tarball directly? | |
| 10:41:40 | zigo | It did build fine in Debian Experimental though (and I already uploaded there...) | |
| 10:41:59 | zigo | lyarwood: I'm using the git tag, which is kind of close to the tarball. | |
| 10:42:23 | zigo | My tooling does a "git archive" to generate the tarball, I've been doing this since the begining of OpenStack. | |
| 10:42:23 | lyarwood | yup, smells like something is off with the version of mock it's pulling in | |
| 10:42:35 | zigo | It's pock 3.0.5. | |
| 10:42:37 | zigo | mock | |
| 10:43:46 | zigo | So I'm guessing it's a problem with another dependency ... | |
| 10:45:01 | lyarwood | yeah looks like we are using 3.0.5 at the moment | |
| 10:45:06 | lyarwood | upstream that is | |
| 10:55:49 | zigo | Would it be possible that it's because of a newer oslotest package? | |
| 10:56:02 | zigo | In Experimental, I built with oslotest 3.8.0, not 4.1.0 | |
| 11:02:56 | zigo | Oh, I'm lagging behind, it should be olsotest 4.2.0 maybe? | |