Earlier  
Posted Nick Remark
#openstack-nova - 2021-07-01
12:57:27 sean-k-mooney thelounge55: i know that openstack-helm used ot have broken code for cells at one point
12:57:52 sean-k-mooney they were settign config options that dont exist
12:58:25 thelounge55 sean-k-mooney then that might be related to it as i victoria release works out of the box
13:00:14 sean-k-mooney https://github.com/openstack/openstack-helm/commit/94642833dd97e9ff397ef1af26449a51572d5b68 this might be related
13:02:10 sean-k-mooney thelounge55: for what its worth openstack helm does not look that activly maintained
13:02:38 sean-k-mooney there are some commits i gues
13:03:03 sean-k-mooney so its not abandoned by any means
13:03:23 sean-k-mooney they just dont seam to follow our normal branching model so its hard to tell what version of openstack they support
13:04:59 sean-k-mooney thelounge55: anyway it look like the api db was not initalise before it tried to update teh cell mapping
13:05:15 sean-k-mooney so you proably just need to do teh api db sync to do that then continue
13:07:13 thelounge55 sean-k-mooney mmm you seems to be right but i was just cross checking if i have the necessary changes as mentioned in the commits. And yes i do have it so it shouldn't be the problem. But it could be possible that the wallaby release nova docker image is not good
13:08:18 sean-k-mooney unlikely that this woudl be related to the docker image
13:08:32 sean-k-mooney there may be other issues in the helml charts
13:09:18 thelounge55 sean-k-mooney yes possible . But i am playing with it yesterday and i am lost at the moment :D
13:09:22 sean-k-mooney openstack helm is one of the less used installer and the nova team is not really invovled in it at all so we dont really have much expeirince with it
13:09:51 sean-k-mooney have you connected to the db server and checked that the api db exists and if it has the tables
13:14:12 thelounge55 `Empty set (0.00 sec)`
13:14:12 thelounge55 `MariaDB [nova]> show tables; `
13:14:12 thelounge55 sean-k-mooney yeah i did try that but there is no tables got created in nova
13:14:30 sean-k-mooney and nova_api
13:14:46 sean-k-mooney i assume the same
13:15:12 sean-k-mooney this look like an openstack helm bug to me so there irc channel can proably help you more
13:17:07 thelounge55 sean-k-mooney nope there is one http://paste.openstack.org/show/807105/ which is got created nova_api
13:17:13 thelounge55 yeah it looks like its nova issue
13:17:32 sean-k-mooney well no its an openstack-helm issue
13:18:16 thelounge55 sean-k-mooney yeah i mean openstack-helm nova helm chart issue :D
13:18:40 sean-k-mooney but ya so what likely has wrong here is that openstack-helm did not initalise the db with the db schema before it tried ot populate teh tables with data
13:18:51 thelounge55 sean-k-mooney anyway thanks for help :)
13:19:32 sean-k-mooney https://github.com/openstack/openstack-helm/blob/master/nova/templates/job-db-init.yaml does not actully seam to init anything
13:20:15 sean-k-mooney but honestly i dont really know how those charts work
13:28:57 thelounge55 sean-k-mooney nvm thanks again :)
15:31:39 opendevreview Kashyap Chamarthy proposed openstack/nova-specs master: Re-propose "CPU selection with hypervisor consideration" https://review.opendev.org/c/openstack/nova-specs/+/799096
17:27:21 opendevreview Merged openstack/nova master: fix sr-iov support on Cavium ThunderX hosts. https://review.opendev.org/c/openstack/nova/+/777679
19:52:15 opendevreview Merged openstack/nova master: db: Fold in ForeignKey constraints https://review.opendev.org/c/openstack/nova/+/786297
19:52:42 opendevreview Merged openstack/nova master: db: Remove 'nova.db.base' module https://review.opendev.org/c/openstack/nova/+/786298
19:58:22 opendevreview sean mooney proposed openstack/os-vif master: update os-vif ci to account for devstack default changes https://review.opendev.org/c/openstack/os-vif/+/798038
19:58:23 opendevreview sean mooney proposed openstack/os-vif master: add configurable per port bridges https://review.opendev.org/c/openstack/os-vif/+/798055
20:13:48 opendevreview sean mooney proposed openstack/os-vif master: update os-vif ci to account for devstack default changes https://review.opendev.org/c/openstack/os-vif/+/798038
20:13:49 opendevreview sean mooney proposed openstack/os-vif master: add configurable per port bridges https://review.opendev.org/c/openstack/os-vif/+/798055
20:16:03 opendevreview Merged openstack/nova master: db: Copy docs from 'nova.db.*' to 'nova.db.sqlalchemy.*' https://review.opendev.org/c/openstack/nova/+/786299
20:16:32 opendevreview Merged openstack/nova master: db: Synchronize function signatures https://review.opendev.org/c/openstack/nova/+/786300
#openstack-nova - 2021-07-03
02:35:23 opendevreview Eric Xie proposed openstack/nova master: Add logs when cannot fit numa https://review.opendev.org/c/openstack/nova/+/798187
05:08:08 opendevreview Merged openstack/nova stable/wallaby: Update SRIOV port pci_slot when unshelving https://review.opendev.org/c/openstack/nova/+/790711
05:23:49 opendevreview Merged openstack/nova master: db: Clean up migration code https://review.opendev.org/c/openstack/nova/+/786301
#openstack-nova - 2021-07-04
18:41:45 opendevreview Ghanshyam proposed openstack/placement master: Fix oslo policy DeprecatedRule warnings https://review.opendev.org/c/openstack/placement/+/799418
21:01:22 opendevreview Ghanshyam proposed openstack/nova master: Fix oslo policy DeprecatedRule warnings https://review.opendev.org/c/openstack/nova/+/799422
23:05:19 opendevreview Ghanshyam proposed openstack/placement master: Fix oslo policy DeprecatedRule warnings https://review.opendev.org/c/openstack/placement/+/799418
#openstack-nova - 2021-07-05
01:12:42 opendevreview Eric Xie proposed openstack/nova master: Add logs when cannot fit numa https://review.opendev.org/c/openstack/nova/+/798187
08:42:15 opendevreview Yongli He proposed openstack/nova master: Smartnic support - cyborg drive https://review.opendev.org/c/openstack/nova/+/771362
08:42:24 opendevreview Yongli He proposed openstack/nova master: smartnic support - new vnic type https://review.opendev.org/c/openstack/nova/+/771363
08:42:46 opendevreview Yongli He proposed openstack/nova master: smartnic support - create arqs https://review.opendev.org/c/openstack/nova/+/758944
08:42:53 opendevreview Yongli He proposed openstack/nova master: smartnic support - build instance with smartnic arqs https://review.opendev.org/c/openstack/nova/+/798249
08:43:01 opendevreview Yongli He proposed openstack/nova master: smartnic support - cleanup arqs https://review.opendev.org/c/openstack/nova/+/798054
08:43:15 opendevreview Yongli He proposed openstack/nova master: smartnic support - reject server move and suspend https://review.opendev.org/c/openstack/nova/+/779913
08:43:26 opendevreview Yongli He proposed openstack/nova master: smartnic support - functional tests https://review.opendev.org/c/openstack/nova/+/780147
09:04:38 lyarwood stephenfin / gibi ; https://review.opendev.org/c/openstack/nova/+/720769 - would you mind hitting this today, https://launchpad.net/bugs/1860913 spells out the usecase pretty well.
09:05:10 gibi lyarwood: looking
09:06:05 lyarwood many thanks
09:08:36 stephenfin sure
09:29:21 gibi lyarwood, stephenfin: what was the solution for the failure of test_archive_task_logs functional test ?
09:29:51 stephenfin um...
09:30:06 stephenfin gibi: can you give me a bit more context? It's Monday morning :-P
09:30:26 gibi I saw multiple patches failing with https://ef75749a93c952a7bcbb-88cdb958b5e15841b787b658e9835738.ssl.cf5.rackcdn.com/720769/16/check/nova-tox-functional-py39/f1f266b/testr_results.html
09:30:52 gibi and I cloudly recall somebody pinged melwitt about it last week
09:30:57 gibi but I cannot reproduce the issue locally
09:31:18 stephenfin oh, I have no idea. Didn't know there was an issue there
09:31:28 alex_xu gibi: I feel smartnic patches are ready for your review https://review.opendev.org/q/topic:%22bp%252Fsriov-smartnic-support%22+(status:open%20OR%20status:merged)
09:32:09 gibi alex_xu: thanks. I will try to get to them, but based on how many times I made promise review it without actually getting there I don't want to promise any more. I will try
09:32:22 alex_xu gibi: thanks!
09:32:26 gibi stephenfin: no worries
09:32:44 alex_xu I think the major logic is on the third and fourth patch
09:41:05 lyarwood gibi: I think that was me pinging about it
09:41:12 lyarwood gibi: iirc it suddenly stopped failing
09:41:18 gibi strange
09:41:35 lyarwood https://zuul.opendev.org/t/openstack/builds?job_name=nova-tox-functional-py38&project=openstack%2Fnova&branch=master&pipeline=check
09:41:38 lyarwood https://bugs.launchpad.net/nova/+bug/1934519
09:41:41 lyarwood yeah really odd
09:42:03 lyarwood I can only assume something was reverted in a dep that fixed it
10:14:47 lyarwood test_volume_backed_live_migration is still failing
10:14:49 lyarwood argh
10:15:23 lyarwood actually that might be an issue with the change
10:15:52 lyarwood becuase https://zuul.opendev.org/t/openstack/builds?job_name=nova-live-migration&project=openstack%2Fnova&branch=master&pipeline=check looks pretty good
10:48:45 lyarwood http://paste.openstack.org/show/807166/ - made some progress with this, it isn't related to the patch AFAICT
11:01:07 gibi lyarwood: good finding
11:02:51 kashyap gibi: Heh, I once did a bit of it on list:
11:03:56 kashyap gibi: You need to follow the request/response "libvirt-$ID": http://lists.openstack.org/pipermail/openstack-dev/2016-October/105158.html
11:04:11 kashyap Each request and response will have the same libvirt-ID: libvirt-30 (or whatever number)
11:04:32 kashyap lyarwood: I saw the brief chat on #virt; it's the dreaded "Device or resource busy" problem
11:04:57 kashyap It is my list of top two "most notorious libvirt errors"
11:05:02 lyarwood kinda
11:05:12 lyarwood that's causing libvirtd to lockup
11:05:19 lyarwood the migration is in a different thread
11:05:27 lyarwood and the dest times out before the src
11:05:31 lyarwood but the src then continues
11:05:51 lyarwood that's a separate behavioural issue in libvirtd tbh
11:06:16 kashyap Me nods
11:06:34 kashyap There's also the SIGTERM / SIGKILL dance. Often times only killing the instance and restarting seems to be the "solution"
11:07:55 kashyap (Aside: if you're wondering what is the other error in my top-2 list, it's the "cannot acquire state change lock")
11:11:34 gibi kashyap: thank I will read that
12:05:29 opendevreview Merged openstack/nova-specs master: [template]suggest work item ordering https://review.opendev.org/c/openstack/nova-specs/+/793197

Earlier   Later