- openstack-discuss - lists.openstack.org

OPS Meetup Meeting tomorrow
by Amy Marrich 19 Apr '22

19 Apr '22

Just a reminder that the OPS Meetup team will meet tomorrow morning at 13:00 UTC in the #openstack-operators room on OFTC. See you there!

1 0

[TripleO] Final TripleO repos release for stable/victoria - any requests?
by Marios Andreou 18 Apr '22

18 Apr '22

Hello The stable/victoria branch for all tripleo repos will transition to Extended Maintenance in 2 weeks [1]. To prevent delays I have prepared a final victoria release at [2]. That [2] will be updated after its depends-on merges (puppet metadata bump) to pickup the latest victoria commits at that point. If there are any patches you want included then please speak up and I'll wait for and include those commits before updating releases/+/836921 [2]. This is the last ever release to be made from stable/victoria. Once it goes to Extended Maintenance we can no longer release. I'll hold it for a few days.. Unless I hear otherwise I will update [2] on Monday and try to get it merged next week. thanks, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028013.ht… [2] https://review.opendev.org/c/openstack/releases/+/836921

2 3

[Neutron] Bug deputy report April 11 - April 18
by Jakub Libosvar 18 Apr '22

18 Apr '22

Hi all, I was the bug deputy for the previous week. There is one critical bug from Slawek with proposed revert. Here is the report: Critical -------- - Test tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_update_instance_port_admin_state is failing constantly since 7.04.2022 https://bugs.launchpad.net/neutron/+bug/1968896 Revert proposed: https://review.opendev.org/c/openstack/neutron/+/837685 Medium ------ - neutron-dhcp-agent memory leak on network sync failure https://bugs.launchpad.net/neutron/+bug/1969270 Needs an assignee - [L3-DVR]l3-agent arp table will not update https://bugs.launchpad.net/neutron/+bug/1968860 Needs an assignee - network DHCP agent ports status is DOWN in multi network creation simultaneously https://bugs.launchpad.net/neutron/+bug/1968859 Needs an assignee - Importing neutron.common.config module registers config options https://bugs.launchpad.net/neutron/+bug/1968606 Proposed fix: https://review.opendev.org/c/openstack/neutron/+/837392 Incomplete ---------- - unable to attach an interface to an external network https://bugs.launchpad.net/neutron/+bug/1968893 Looks like configuration issue, more logs are needed - too many l3 dvr agents got notifications after a server got deleted https://bugs.launchpad.net/neutron/+bug/1968837 I'm not sure I understand what the issue is Invalid ------- - ovn-controller don't update new flows https://bugs.launchpad.net/neutron/+bug/1969354 It looks like misconfigured environment, provided some tips

1 0

[ironic] Skipping today's upstream meeting
by Iury Gregory 18 Apr '22

18 Apr '22

Hi Ironicers, We will skip the weekly meeting this week, since we have Easter Holidays and other holidays in some countries =) ) -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[neutron] Mysql FK Errors
by Ammad Syed 18 Apr '22

18 Apr '22

Hi, I am using neutron 19.1 with OVN backend. I am receiving below mentioned errors in my percona xtradb cluster logs for neutron database. 2022-04-04T15:39:17.342175+05:00 187579 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron_ml2`.`portsecuritybindings` 2022-04-05T14:18:19.801183+05:00 275503 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron_ml2`.`ml2_port_binding_levels` Can you guys advice about these errors. Is there anything to worry about? or should I just ignore them ? Ammad

1 0

[Trove][Xena] Error building Trove image
by wodel youchi 17 Apr '22

17 Apr '22

Hi, When trying to build Trove I am getting this error message : 2022-04-10 08:55:25.497 | *+ install_deb_packages install iscsi-initiator-utils* 2022-04-10 08:55:25.497 | + DEBIAN_FRONTEND=noninteractive 2022-04-10 08:55:25.497 | + http_proxy= 2022-04-10 08:55:25.497 | + https_proxy= 2022-04-10 08:55:25.497 | + no_proxy= 2022-04-10 08:55:25.497 | + apt-get --option Dpkg::Options::=--force-confold --option Dpkg::Options::=--force-confdef --assume-yes install iscsi-initiator-utils 2022-04-10 08:55:25.541 | Reading package lists... 2022-04-10 08:55:25.788 | Building dependency tree... 2022-04-10 08:55:25.788 | Reading state information... 2022-04-10 08:55:25.825 | *E: Unable to locate package iscsi-initiator-utils* 2022-04-10 08:55:25.838 | ++ diskimage_builder/lib/img-functions:run_in_target:59 : check_break after-error run_in_target bash 2022-04-10 08:55:25.843 | ++ diskimage_builder/lib/common-functions:check_break:143 : echo '' 2022-04-10 08:55:25.844 | ++ diskimage_builder/lib/common-functions:check_break:143 : egrep -e '(,|^)after-error(,|$)' -q 2022-04-10 08:55:25.851 | + diskimage_builder/lib/img-functions:run_in_target:1 : trap_cleanup 2022-04-10 08:55:25.855 | + diskimage_builder/lib/img-functions:trap_cleanup:36 I am not an Ubuntu person but I think the package's name is open-iscsi. This is the command I used to build the image : ./trovestack build-image ubuntu bionic true ubuntu /home/stack/trove-xena-guest-ubuntu-bionic-dev.qcow2 My OS is a Centos 8 Stream. you can find the whole log of the operation attached. Thanks in advance. Regards.

2 1

Re: [Trove][Xena] Error building Trove image
by Hirotaka Wakabayashi 16 Apr '22

16 Apr '22

Hi Wodel, I think you need to fix DIB element files to build a guest image as CentOS Stream. Officially supported operating system in Trove is currently Ubuntu[1]. I am preparing Installation instructions Fedora/CentOS Stream users[2] but that is not completed. You may not really need to build a guest image as CentOS Stream if you are a mysql or postgresql user, because Trove supports Docker Since Victoria. This means database service can runs as docker container inside the Trove instance. You can define the datastore image by using the "docker_image" config option[4]. --- [1]: https://docs.openstack.org/trove/latest/admin/building_guest_images.html [2]: https://storyboard.openstack.org/#!/story/2009918 [3]: https://opendev.org/openstack/trove/src/branch/master/integration/scripts/f… [4]: https://docs.openstack.org/trove/latest/admin/run_trove_in_production.html#… Regards,Hirotaka On Wednesday, April 13, 2022, 10:04:53 PM GMT+9, <openstack-discuss-request(a)lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [Trove][Xena] Error building Trove image (wodel youchi) ---------------------------------------------------------------------- Message: 1 Date: Wed, 13 Apr 2022 00:16:59 +0100 From: wodel youchi <wodel.youchi(a)gmail.com> To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [Trove][Xena] Error building Trove image Message-ID: <CAJV_UBCZVOKmjvwdDJW0w17g39L8MVHuZNOQJ7yH2DZNFnqZbA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, When trying to build Trove I am getting this error message : 2022-04-10 08:55:25.497 | *+ install_deb_packages install iscsi-initiator-utils* 2022-04-10 08:55:25.497 | + DEBIAN_FRONTEND=noninteractive 2022-04-10 08:55:25.497 | + http_proxy= 2022-04-10 08:55:25.497 | + https_proxy= 2022-04-10 08:55:25.497 | + no_proxy= 2022-04-10 08:55:25.497 | + apt-get --option Dpkg::Options::=--force-confold --option Dpkg::Options::=--force-confdef --assume-yes install iscsi-initiator-utils 2022-04-10 08:55:25.541 | Reading package lists... 2022-04-10 08:55:25.788 | Building dependency tree... 2022-04-10 08:55:25.788 | Reading state information... 2022-04-10 08:55:25.825 | *E: Unable to locate package iscsi-initiator-utils* 2022-04-10 08:55:25.838 | ++ diskimage_builder/lib/img-functions:run_in_target:59 : check_break after-error run_in_target bash 2022-04-10 08:55:25.843 | ++ diskimage_builder/lib/common-functions:check_break:143 : echo '' 2022-04-10 08:55:25.844 | ++ diskimage_builder/lib/common-functions:check_break:143 : egrep -e '(,|^)after-error(,|$)' -q 2022-04-10 08:55:25.851 | + diskimage_builder/lib/img-functions:run_in_target:1 : trap_cleanup 2022-04-10 08:55:25.855 | + diskimage_builder/lib/img-functions:trap_cleanup:36 I am not an Ubuntu person but I think the package's name is open-iscsi. This is the command I used to build the image : ./trovestack build-image ubuntu bionic true ubuntu /home/stack/trove-xena-guest-ubuntu-bionic-dev.qcow2 My OS is a Centos 8 Stream. you can find the whole log of the operation attached. Thanks in advance. Regards.

1 0

[Kolla-ansible][Glance] Glance HA deployment with shared file backend
by Rodrigo Lima 16 Apr '22

16 Apr '22

Hi Guys, hope all is well! According with the kolla-ansible documentation, " By default when using file backend only one glance-api container can be running." So my questions is quite simple: Can I deploy multiple glance_api containers in HA mode (like if I used ceph or swift backend) if I use a shared filesystem (eg. NFS) in all glance nodes? If I can do so, what I need to change in deployment files/scripts/yaml?

2 1

[all][tc] What's happening in Technical Committee: summary April 15th, 21: Reading: 10 min
by Ghanshyam Mann 16 Apr '22

16 Apr '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We cancelled this week's meeting. * Next TC weekly meeting will be on April 21st Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by April 20th. 2. What we completed this week: ========================= * Added goal readiness checklist[2] * Retired openstack-health[3] * Retired tempest-lib[4] * Add Ganesha based Ceph NFS Charm[5] * PTG summary sent to ML[6] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * With the Zed cycle kickoff[7], I have started the Zed cycle TC tracker by listing all the items we discussed in PTG but we will add more during the cycle also if something important comes up[8] Open Reviews ----------------- * Seven open reviews for ongoing activities[9]. Drop the lower constraints maintenance ------------------------------------------------ This has been going on for many months, if I remember correctly it was first brought up in Dec 2021. During those discussions, we figured out that maintaining and testing the lower constraints has many challenges. TC discussed all those challenges in Zed PTG and agreed to drop lower-constraints.txt file and its testing but keep them in requirements.txt with our best effort. I proposed the TC resolution on this[10], feel free to feedback there if there is any strong objection in this direction. Also sent it on ML[11] Consistent and Secure Default RBAC -------------------------------------------- I summarized the RBAC PTG discussion[12], we did not finish the discussion over the open question and decided to continue it in RBAC meetings later. I will schedule the next meeting soon. If you have any other questions than the current one, please add them to the etherpad[13] Removing the TC tag framework ---------------------------------- In TC tag framework, every TC member used to assign a few projects to check their health, needs from TC etc. It was meant to improve the interaction between TC and PTLs and contact points for any projects when TC needs it. But it did not go that way and even many of us do not know if that still exists or not. With TC weekly meetings and PTG interaction sessions, we anyways are more contacted with leaders and discussed it in PTG and agreed to remove this framework. I have proposed the removal[14] 2021 User Survey TC Question Analysis ----------------------------------------------- Jay has summarized the TC's user survey in PTG and it is up in gerrit for review[15]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Zaqar PTL assigned is merged[16], with that only Adjutant project is leaderless/maintainer-less. We will check Adjutant's situation again on ML and hope Braden will be ready with their company side permission[17]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[18]. Project updates ------------------- * Add the cinder-three-par charm to Openstack charms[19] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[20]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [21] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/835102 [3] https://review.opendev.org/c/openstack/governance/+/836706 [4] https://review.opendev.org/c/openstack/governance/+/836704 [5] https://review.opendev.org/c/openstack/governance/+/835429 [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028104.ht… [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028206.ht… [8] https://etherpad.opendev.org/p/tc-zed-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://review.opendev.org/c/openstack/governance/+/838004 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028199.ht… [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028103.ht… [13] https://etherpad.opendev.org/p/rbac-zed-ptg [14] https://review.opendev.org/c/openstack/governance/+/837891 [15] https://review.opendev.org/c/openstack/governance/+/836888 [16] https://review.opendev.org/c/openstack/governance/+/831123 [17] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [18] https://etherpad.opendev.org/p/zuul-config-error-openstack [19] https://review.opendev.org/c/openstack/governance/+/837781 [20] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [21] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][tc] Technical Committee Zed cycle Kick-Off
by Ghanshyam Mann 16 Apr '22

16 Apr '22

Hello Everyone, In PTG, we decided to continue the TC per-cycle-tracker which help us to finish the things within the timeframe of one cycle. During PTG week (TC+leader interaction and TC-related sessions), we had a lot of productive discussions[1] and collected many working items for TC. The Technical Committee's main goal is to drive more technical work to solve the OpenStack existing technical challenges. This is the main feedback from the community to TC working and I am happy to have that feedback, as well as TC, started working on it in a more productive way. Of course, we will continue doing the governance part too which does not take much bandwidth of TC members and we will also try to minimize such process-related tasks as per the current situation and needs of the community. In the Zed cycle also, we will continue to focus on the Technical works. I have created the Zed cycle TC tracker and we will be targeting 7 Technical items + 4 process/governance-focused items. Also, we will be open to taking more items if anything important comes up in between the cycle. - https://etherpad.opendev.org/p/tc-zed-tracker With that, let's continue to work together and have another successful cycle. Feel free to reach out to TC at any time (does not need to wait for the weekly meeting) for your queries or help. Also, you can find all the cycle wise trackers on this wiki page[2] [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028104.ht… [2] https://wiki.openstack.org/wiki/Technical_Committee_Tracker -gmann

1 0