Earlier  
Posted Nick Remark
#openstack-nova - 2022-03-04
11:19:21 gibi and depending on the driver's meeting outcome I can squash it
12:18:33 sean-k-mooney gibi: so that deprecation warning is actully already fixed in secretstorage
12:18:46 sean-k-mooney but i had to manually install the latest version
12:18:51 sean-k-mooney its fixed in 3.3.1
12:19:02 sean-k-mooney but for some reason 2.3.1 was insalled by devstack
12:20:05 sean-k-mooney upperconstaits allwos 3.3.1 so not sure why this was not installed
12:26:34 gibi interesting
12:28:32 gibi I also see 2.3.1 in my devstack too
12:32:02 gibi devstack stack.sh log does not explain where this is coming from
12:36:39 sean-k-mooney it must be a downgrade form say keyring or something else
12:37:35 sean-k-mooney actully it requires >=3.2
12:37:37 sean-k-mooney https://github.com/jaraco/keyring/blob/main/setup.cfg#L24
12:38:25 sean-k-mooney i have a really old verison fo keyring 18.0.1
12:38:45 sean-k-mooney which pulls in <3
12:38:47 sean-k-mooney https://github.com/jaraco/keyring/blob/18.0.1/setup.cfg#L35
12:39:07 sean-k-mooney so somehting is clamping the keyrign version which si then clamping the secretstorage version
12:50:54 sean-k-mooney gibi python3-keyring is installed form the package manager
12:52:04 sean-k-mooney so this might be form the base cloud image
12:53:02 sean-k-mooney i dont have the issue on a centos9 vm so its likely not related to devstack
12:54:47 gibi yeah I don't see that in the bindep either so probably it is the ubunut cloud image
13:53:56 bauzas just in case, folks, I wrote something about the next PTG http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027529.html
13:54:08 bauzas I'd appreciate thoughts about the PTG schedule
13:56:55 gibi looking
14:07:03 gibi bauzas: nice proposals. I made my vote in the etherpad
14:07:11 bauzas thanks
14:08:05 bauzas gibi: about what we could discussing during the Asian time, I don't know yet
14:08:10 bauzas but
14:08:46 bauzas if we have enough quorum, we could discuss about something that US contributors don't need to want to discuss
14:08:55 gibi yeah
14:09:32 gibi and I also see that creating an asian friendly slot might encourage folks from that part of the world to propose topics
14:11:41 bauzas yeah
15:29:40 opendevreview Jan Hartkopf proposed openstack/nova-specs master: update userdata https://review.opendev.org/c/openstack/nova-specs/+/816542
15:42:04 opendevreview Dmitrii Shcherbakov proposed openstack/nova master: Fix migration with remote-managed ports & add FT https://review.opendev.org/c/openstack/nova/+/829974
15:43:35 dmitriis gibi: included your fix into my change, thanks again for finding the issue in the fixture!
15:43:54 gibi dmitriis: no worries I also needed the fix
15:44:11 gibi dmitriis: the fun thing is that it is not the fixture that is faulty it is the nova code handling the migration context
15:44:28 dmitriis gibi: ah, right, it's in the resource tracker
15:44:46 gibi dmitriis: probably it does not cause fault in a real deployment just in the test env, but the logic in the code is wrong
15:45:43 dmitriis gibi: I see. I'll look into storing pf_mac_address and vf_num in extra_info. That's a bit different from the case you were working on
15:46:02 gibi dmitriis: I think the pattern is similar
15:46:10 gibi let me know if you need help
15:46:56 dmitriis gibi: ack, I'll do a follow-up change on top of the current one
15:51:52 sean-k-mooney dmitriis: so im going to take a look at your patch shortly
15:52:05 sean-k-mooney the fix your are talking about is for revert?
15:52:16 dmitriis sean-k-mooney: yes, it's cold migration + revert
15:52:37 sean-k-mooney ok so i mihgt need that too
15:52:51 dmitriis sean-k-mooney: https://review.opendev.org/c/openstack/nova/+/829974/4..5
15:53:03 sean-k-mooney am i was hoping to get acces to 2 node system to do some vdpa move operation testing
15:53:25 sean-k-mooney right now we are having issue with froman to get it to repovision with centos9
15:53:46 sean-k-mooney so im debating if i can use the test fixture to test vdpa move operations
15:54:30 sean-k-mooney i think everything or mostly everything is in place to do that but i like to test things with real hardware too
15:55:20 sean-k-mooney ah the fix is to do a deepcopy
15:56:17 sean-k-mooney ya im not sure that a real deployment would hit the issue since we likely wont have the same instnace object
15:57:10 sean-k-mooney that kind of rasies the question should we be deepcopying the instance.numa_topotlogy or any of the other data
15:57:53 gibi sean-k-mooney: yeah I debated to add more deepcopy. I did not tried to reproduce the issue with the other fields
15:58:34 gibi it is only a problem for the pci_device as the tracker _appends_ the newly claimed devices so maybe it is not an issue to the other fields
15:58:53 gibi but I haven't digged down into it
15:59:20 sean-k-mooney ya
16:21:14 opendevreview sean mooney proposed openstack/nova stable/wallaby: libvirt: Add announce-self post live-migration workaround https://review.opendev.org/c/openstack/nova/+/825178
16:26:55 opendevreview sean mooney proposed openstack/nova stable/victoria: libvirt: Add announce-self post live-migration workaround https://review.opendev.org/c/openstack/nova/+/825175
16:30:05 opendevreview sean mooney proposed openstack/nova stable/ussuri: libvirt: Add announce-self post live-migration workaround https://review.opendev.org/c/openstack/nova/+/825176
16:32:00 opendevreview sean mooney proposed openstack/nova stable/train: libvirt: Add announce-self post live-migration workaround https://review.opendev.org/c/openstack/nova/+/825177
17:03:39 opendevreview Takashi Natsume proposed openstack/placement master: Add zed spec directory https://review.opendev.org/c/openstack/placement/+/829532
17:04:08 opendevreview Takashi Natsume proposed openstack/os-vif master: Change minversion of tox to 3.18.0 https://review.opendev.org/c/openstack/os-vif/+/791970
17:04:26 opendevreview Takashi Natsume proposed openstack/os-resource-classes master: Change minversion of tox to 3.18.0 https://review.opendev.org/c/openstack/os-resource-classes/+/791974
17:04:59 opendevreview Takashi Natsume proposed openstack/placement master: Change minversion of tox to 3.18.0 https://review.opendev.org/c/openstack/placement/+/791971
19:27:07 noonedeadpunk hey there! I know it's friday evening, but I was wondering if you see https://review.opendev.org/c/openstack/nova/+/822749 as appropriate backport to stable branches?
19:27:53 noonedeadpunk as powervm is really pita on older releases where you have py3.6
19:35:32 noonedeadpunk or well, should likely patch u-c instead to map pypowervm back to 1.1.24 where it was at least installing
20:41:25 elodilles noonedeadpunk: req changes are not allowed to backport, but as I see it actually does not change them, just moves them to setup.cfg's [extra] section, so I think this is OK to backport
23:00:40 opendevreview Mauricio Faria de Oliveira proposed openstack/nova stable/victoria: [stable-only] libvirt: UEFI: skip OVMF_CODE.secboot.fd on pc if possible https://review.opendev.org/c/openstack/nova/+/828979
23:01:18 opendevreview Mauricio Faria de Oliveira proposed openstack/nova stable/victoria: [stable-only] libvirt: UEFI: skip OVMF_CODE.secboot.fd on pc if possible https://review.opendev.org/c/openstack/nova/+/828979
23:02:46 opendevreview Mauricio Faria de Oliveira proposed openstack/nova stable/ussuri: [stable-only] libvirt: UEFI: skip OVMF_CODE.secboot.fd on pc if possible https://review.opendev.org/c/openstack/nova/+/828980
#openstack-nova - 2022-03-05
07:25:31 opendevreview Merged openstack/nova master: Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963
09:30:38 opendevreview kiran pawar proposed openstack/nova master: VMware: Split out VMwareAPISession https://review.opendev.org/c/openstack/nova/+/832156
10:20:13 opendevreview kiran pawar proposed openstack/nova master: VMware: Split out VMwareAPISession https://review.opendev.org/c/openstack/nova/+/832156
14:03:32 opendevreview kiran pawar proposed openstack/nova master: VMware: StableMoRefProxy for moref recovery https://review.opendev.org/c/openstack/nova/+/832164
14:07:14 opendevreview kiran pawar proposed openstack/nova master: VMware: StableMoRefProxy for moref recovery https://review.opendev.org/c/openstack/nova/+/832164
14:17:47 opendevreview kiran pawar proposed openstack/nova master: VMware: Split out VMwareAPISession https://review.opendev.org/c/openstack/nova/+/832156
14:17:48 opendevreview kiran pawar proposed openstack/nova master: VMware: StableMoRefProxy for moref recovery https://review.opendev.org/c/openstack/nova/+/832164
15:48:27 opendevreview Merged openstack/nova stable/wallaby: compute: Avoid duplicate BDMs during reserve_block_device_name https://review.opendev.org/c/openstack/nova/+/803718
#openstack-nova - 2022-03-07
02:05:14 opendevreview HYSong proposed openstack/nova master: fix local volume extend https://review.opendev.org/c/openstack/nova/+/832180
03:29:18 opendevreview Xuan Yandong proposed openstack/nova master: Remove redundant symbols https://review.opendev.org/c/openstack/nova/+/832185
09:41:36 opendevreview kiran pawar proposed openstack/nova master: VMware: StableMoRefProxy for moref recovery https://review.opendev.org/c/openstack/nova/+/832164
09:41:36 opendevreview kiran pawar proposed openstack/nova master: VMware: Split out VMwareAPISession https://review.opendev.org/c/openstack/nova/+/832156
10:10:47 ignaziocassano_ Hello, sometimes the volume retype from a netapp nfs storage to another netapp nfs storage does not work. I do not know the reason but I think something is going wrong in nova:
10:11:14 ignaziocassano_ File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1593, in _swap_volume\n raise exception.VolumeRebaseFailed(reason=six.text_type(exc))\n', "VolumeRebaseFailed: Volume rebase failed: Requested operation is not valid: pivot of disk 'vda' requires an active copy job\n"]: VolumeAttachmentNotFound: Volume attachment 2cd820e0-85e8-498d-a62a-800260d0cf31 could not be found
10:11:24 ignaziocassano_ Any helo please ?
10:11:30 ignaziocassano_ Any help please ?
10:41:52 kashyap ignaziocassano_: No direct answer, but that error (from libvirt) means: the "volume retype" (i.e volume migration) itself is not active
10:42:14 kashyap "active copy" == the copy that is on the NFS and is being mirrored from the NetApp storage
10:42:36 kashyap Also what version of OSP is this? And also mention libvirt/QEMU versions
10:45:26 ignaziocassano_ kashyap: I am using queens on centos 7 libvirt 4.5.0 QEMU emulator version 2.12.0 (qemu-kvm-ev-2.12.0-33.1.el7_7.4)
10:48:45 ignaziocassano_ Somettimes retyped volumes are corrupted and file system on instances went in read only
11:05:29 kashyap ignaziocassano_: The versions seems moderately old (~2017/2018); lots of storage bugs have been fixed in this area. And that corruption doesn't sound good.
11:05:47 kashyap I don't know if this is even reproducible consistenlty in your env.
11:05:53 kashyap So many variables :-(
11:15:42 sean-k-mooney ignaziocassano_: what version of nfs are you using
11:16:16 sean-k-mooney ignaziocassano_: nova recommends v4.0 as a minium preferably 4.2
11:17:17 ignaziocassano_ sean-k-mooney: I do not knkow why, but the controlles mount cinder with version 4.0 while the compute nodes are using nfs vers 3

Earlier   Later