March 2022 - openstack-discuss - lists.openstack.org

[ops][cinder] reminder: resource count survey - win fabulous prizes!
by Brian Rosmaita 10 Mar '22

10 Mar '22

Hello operators, Don't miss out on this chance to take the Cinder Resource Count Survey! Act now before the survey closes on Wednesday 30 March! https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ Details below: The Cinder project is working on the cinder quotas system in an effort to improve its accuracy and remove the necessity for operators to go through and clean it up occasionally when it gets out of sync with reality. One way to do this is to use dynamic database counting (instead of storing the usage info in a table where it can become outdated). Whether this will be a good change depends on how many records the database has to process during a transaction, which in turn depends on how many Cinder resources a project has. So we need to get some information from you. Please take this brief survey: https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ The survey closes on Wednesday 30 March at 1200 UTC, so that we can have data to discuss during the Zed PTG. But please don't procrastinate, it's only 6 questions and the answers are all positive integers. It shouldn't take long to fill out! Thanks! brian

1 0

[openstack][queens][cinder] volume retype errors
by Ignazio Cassano 10 Mar '22

10 Mar '22

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: /var/log/nova/nova-compute.log:2022-02-02 14:23:39.992 194288 ERROR root [req-ebbf749f-359f-4282-94c5-0913cffe97a3 66adb965bef64eaaab2af93ade87e2ca 68feefdf7c5847388534e9214dc13366 - default default] Original exception being dropped: ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5655, in _swap_volume\n mountpoint, resize_to)\n', ' File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1647, in swap_volume\n self._disconnect_volume(context, new_connection_info, instance)\n', ' File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__\n self.force_reraise()\n', ' File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise\n six.reraise(self.type_, self.value, self.tb)\n', ' File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1644, in swap_volume\n self._swap_volume(guest, disk_dev, conf, resize_to)\n', ' 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 Must I try to change some parameters in nova.conf on compute nodes about volume attachment ? Thanks Ignazio

3 7

[trove][tc][all] Call for volunteers to be a PTL and maintainers
by Slawek Kaplonski 10 Mar '22

10 Mar '22

Hi, After last PTL elections [1] Trove project still don't have any PTL elected. So this is call for maintainers for Trove. If You are using it or interested in it, and if You are willing to help maintaining this project, please contact TC members through this mailing list or directly on the #openstack-tc channel @OFTC. We can talk possibilities to make someone a PTL of the project or going with this project to the Distributed Project Leadership [2] model. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [2] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[kuryr] Zed PTG planning
by Maysa De Macedo Souza 10 Mar '22

10 Mar '22

Hello everyone, The virtual PTG will happen between 4th-8th April. I've created a doodle[1] to try finding a time slot that works for most of us. There is also an etherpad[2] to propose topics to be discussed, feel free to fill it if you have one. Thank you. Kind regards, Maysa Macedo. [1] https://doodle.com/meeting/participate/id/0dN1Movb [2] https://etherpad.opendev.org/p/kuryr-zed-ptg

1 1

Ussuri: Magnum failed to get the size of cluster
by Eugen Block 10 Mar '22

10 Mar '22

Hi *, sorry for the repost, I forgot to edit the subject line. I'm trying to get magnum to work in an Ussuri environment. There are some issues I'm facing and would like to ask you for some pointers what I might be doing wrong. The control nodes would have access to the internet through a proxy, I would like to avoid that but I don't know yet what my local registry needs to look like. So to get it working I'll go with the http_proxy. The first attempts failed due to various reasons, now I'm stuck at the invalid discovery_url. After some search I found that I need to create a new discovery_url like this: controller02:~ # curl --silent -H "Accept: text/plain" https://discovery.etcd.io/new?size=1 Using that new URL I try to create a cluster like this: controller02:~ # openstack coe cluster create kubernetes-cluster-8 --cluster-template 9c7cfeff-3807-4b06-a4e6-a76f2ae0f612 --master-count 1 --node-count 1 --keypair eblock --discovery-url https://discovery.etcd.io/<UUID> The template contains the http and https proxy. The resulting error is this: ---snip--- HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)): requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] magnum.common.exception.GetClusterSizeFailed: Failed to get the size of cluster from 'https://discovery.etcd.io/<UUID>'. ---snip--- The stack trace is a little longer, of course, but this is the relevant part. Can anyone point me in the right direction? What am I missing? I also tried quay.io since discovery.etcd.io seems to be not maintained anymore, but there I can't even generate a new URL. Any help is greatly appreciated! Thanks Eugen

1 1

Ussuri: Magnum
by Eugen Block 10 Mar '22

10 Mar '22

Hi *, I'm trying to get magnum to work in an Ussuri environment. There are some issues I'm facing and would like to ask you for some pointers what I might be doing wrong. The control nodes would have access to the internet through a proxy, I would like to avoid that but I don't know yet what my local registry needs to look like. So to get it working I'll go with the http_proxy. The first attempts failed due to various reasons, now I'm stuck at the invalid discovery_url. After some search I found that I need to create a new discovery_url like this: controller02:~ # curl --silent -H "Accept: text/plain" https://discovery.etcd.io/new?size=1 Using that new URL I try to create a cluster like this: controller02:~ # openstack coe cluster create kubernetes-cluster-8 --cluster-template 9c7cfeff-3807-4b06-a4e6-a76f2ae0f612 --master-count 1 --node-count 1 --keypair eblock --discovery-url https://discovery.etcd.io/<UUID> The template contains the http and https proxy. The resulting error is this: ---snip--- HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)): requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] magnum.common.exception.GetClusterSizeFailed: Failed to get the size of cluster from 'https://discovery.etcd.io/<UUID>'. ---snip--- The stack trace is a little longer, of course, but this is the relevant part. Can anyone point me in the right direction? What am I missing? I also tried quay.io since discovery.etcd.io seems to be not maintained anymore, but there I can't even generate a new URL. Any help is greatly appreciated! Thanks Eugen

1 0

[Neutron][Octavia][ovn-octavia-provider] proposing Luis Tomas Bolivar for ovn-octavia-provider core reviewer
by Lajos Katona 10 Mar '22

10 Mar '22

Hi I would like to propose Luis Tomas Bolivar (ltomasbo) as a core reviewer to the ovn-octavia-provider project. Luis is very active in the project (see [1] and [2]) and has experience with Kuryr side also which uses ovn-octavia-provider. As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration [1]: https://review.opendev.org/q/owner:ltomasbo%2540redhat.com+branch:master [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

8 8

[ironic] Zed PTG slots
by Iury Gregory 10 Mar '22

10 Mar '22

Hello Ironicers! For the Zed PTG I'm planning to have some slots that will allow APAC contributors to participate in the discussions. Keep in mind that we have some guidelines we should try to follow: 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Based on this I have the following proposals: (Feel free to provide more ideas also) =) *Option #1* *16hrs* Monday till Thursday 1h (APAC night + EMEA morning) 2hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) *Option #2* *15hrs* Tuesday till Friday 1h (APAC night + EMEA morning) 2hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) * On Friday the NA + APAC session won't happen because is saturday for APAC contributors * *Option #3* *16hrs* Monday till Thursday 3hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) *Option #4* *15hrs* Tuesday till Friday 3hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) * On Friday the NA + APAC session won't happen because is saturday for APAC contributors * Please choose two options and we will vote during our upstream meeting on March 7th. Thank you! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 3

[all][tc] Technical Committee next weekly meeting on Mar 10th at 1500 UTC
by Ghanshyam Mann 10 Mar '22

10 Mar '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Mar 10th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Mar 9th , at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[puppet] Gate blocker: CentOS 9 integration jobs are broken
by Takashi Kajinami 10 Mar '22

10 Mar '22

Hi, Please be aware that currently CentOS 9 integration jobs are broken because of the two problems caused by recent updates in c9s repos. https://bugs.launchpad.net/puppet-openstack-integration/+bug/1962506 https://bugs.launchpad.net/puppet-openstack-integration/+bug/1962507 I'm currently working on implementing workaround[1], but in case it would take some time, I'll make c9s integration jobs non-voting again to unblock our gate. [1] https://review.opendev.org/c/openstack/puppet-openstack-integration/+/831197 Please avoid approving changes which require integration jobs. Thank you, Takashi

2 4