Earlier  
Posted Nick Remark
#openstack-nova - 2020-04-23
18:57:06 dansmith it'll be a few before we can remove it
18:57:21 artom OK, so for a bugin that driver, it'd be fair to say wontfix?
18:57:35 artom In order to set realistic exptectations?
18:57:55 dansmith that's really for the owners of the driver to say I guess
18:58:14 dansmith I would maybe mark it as triaged or whatever, if it looks valid and tag it so it's clearly vmware-related
18:58:35 dansmith and maybe comment that it's unlikely to get fixed, but marking it as wontfix is probably too aggressive
18:58:46 artom It's already tagged, I have no idea if it's valid, I'll leave it alone then
18:59:45 openstack Launchpad bug 1800204 in OpenStack Compute (nova) "n-cpu.service consuming 100% of CPU indeterminately" [Undecided,Won't fix]
18:59:45 artom And now you're making me doubt closing https://bugs.launchpad.net/nova/+bug/1800204 as wontfix
19:02:39 dansmith I would argue that bugs that rely on intercepting the rpc message and changing it are not worth our time, yes
19:03:31 artom \o/
19:33:05 openstackgerrit Merged openstack/nova master: Revert "Temporarily skip TestNovaMigrationsMySQL" https://review.opendev.org/718630
20:21:51 gibi bauzas: fyi updated the RC1 release patch
20:32:32 melwitt gibi: is the prelude update in there too? sorry I don't see yet
20:32:42 melwitt for the policy doc
20:34:17 melwitt or wait, maybe I'm getting confused. cycle highlight updated with link... did we need an update to the prelude, I thought we were going to but maybe not really needed
20:41:05 melwitt no I think I got confused with the cycle highlights. nevermind me
20:43:29 melwitt we did update it https://review.opendev.org/722220 ok good
21:19:49 openstackgerrit Merged openstack/nova stable/stein: Reset the cell cache for database access in Service https://review.opendev.org/720587
21:37:36 openstackgerrit OpenStack Release Bot proposed openstack/nova stable/ussuri: Update .gitreview for stable/ussuri https://review.opendev.org/722518
21:37:42 openstackgerrit OpenStack Release Bot proposed openstack/nova stable/ussuri: Update TOX_CONSTRAINTS_FILE for stable/ussuri https://review.opendev.org/722520
21:37:46 openstackgerrit OpenStack Release Bot proposed openstack/nova master: Update master for stable/ussuri https://review.opendev.org/722521
21:37:52 openstackgerrit OpenStack Release Bot proposed openstack/nova master: Add Python3 victoria unit tests https://review.opendev.org/722523
22:00:27 gmann melwitt: yeah both are updated.
23:04:55 openstackgerrit Takashi Natsume proposed openstack/nova master: Add placeholder migrations for Ussuri backports https://review.opendev.org/722546
23:06:58 openstackgerrit Merged openstack/python-novaclient master: [Community goal] Update contributor documentation https://review.opendev.org/722391
#openstack-nova - 2020-04-24
01:46:13 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Update SPEC: Using PUT instead of PATCH API to update delete_on_termination https://review.opendev.org/722194
02:50:57 openstackgerrit Kevin Zhao proposed openstack/nova master: [WIP] CI: add tempest-integrated-compute-aarch64 job https://review.opendev.org/714439
02:54:16 openstackgerrit Kevin Zhao proposed openstack/nova master: [WIP] CI: add tempest-integrated-compute-aarch64 job https://review.opendev.org/714439
03:02:47 openstackgerrit Takashi Natsume proposed openstack/nova master: Add placeholder migrations for Ussuri backports https://review.opendev.org/722546
06:02:48 openstackgerrit Kevin Zhao proposed openstack/nova master: [WIP] CI: add tempest-integrated-compute-aarch64 job https://review.opendev.org/714439
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 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:10:21 bauzas lyarwood: permission to close this bug ? https://bugs.launchpad.net/nova/+bug/1738297
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 openstack Launchpad bug 1836681 in OpenStack Compute (nova) "attach volume succeeded but device not found on guest machine" [Undecided,Incomplete]
08:18:28 gibi bauzas: artom triaged some https://bugs.launchpad.net/nova/+bug/1836681
08:18:41 bauzas that'd explain then
08:18:41 lyarwood bauzas: permission granted, fire.
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

Earlier   Later