January 2022 - openstack-discuss - lists.openstack.org

[TripleO] Gate/Check blocker - tripleo-ci-centos-9-content-provider
by Chandan Kumar 18 Jan '22

18 Jan '22

Hello All, tripleo-ci-centos-9-content-provider is failing in Check and gate pipeline with following error ``` Last metadata expiration check: 0:01:21 ago on Tue 18 Jan 2022 03:13:29 AM UTC. centos-stream-release-9.0-6.el9.noarch.rpm 7.9 MB/s | 26 kB 00:00 warning: centos-stream-release-9.0-6.el9.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 8483c65d: NOKEY Verifying... ######################################## Preparing... ######################################## package centos-stream-release-9.0-8.el9.noarch (which is newer than centos-stream-release-9.0-6.el9.noarch) is already installed ``` A bug is already logged against the failure: https://bugs.launchpad.net/tripleo/+bug/1958202 and wip fix is here: https://review.opendev.org/c/openstack/tripleo-common/+/825038 Please hold your recheck on the tripleo patches where the CS9 content provider runs. Will update this thread once we have fixes merged. Thanks, Chandan Kumar

1 1

Can neutron-fwaas project be revived?
by Dazhong Qin (秦海中)-云数据中心集团 18 Jan '22

18 Jan '22

Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

4 10

[neutron] Bug Deputy Report January 10 - 107
by Jakub Libosvar 17 Jan '22

17 Jan '22

Hi, I was bug deputy last week, there are no bugs that require immediate attention. Here is the week summary Critical -------- - [tempest ] neutron-tempest-plugin-dynamic jobs are failing - https://bugs.launchpad.net/neutron/+bug/1957453 - Unassigned - As per Lajos it's fixed in os-ken - https://review.opendev.org/q/58a39392397cd01e174c4736fa31a9a5617f1ff0 High ---- - Functional tests for HA routers fails due to router transitioned to FAULT state - https://bugs.launchpad.net/neutron/+bug/1956958 - Assigned to Slawek - [FT] Test "test_port_dhcp_options" failing - https://bugs.launchpad.net/neutron/+bug/1956965 - Unassigned - Regular user can remove qos from a port despite the policy - https://bugs.launchpad.net/neutron/+bug/1957175 - Assigned to Yatin - OVS: except MappingNotFound instead of KeyError - https://bugs.launchpad.net/neutron/+bug/1957931 - Unassigned - Patch: https://review.opendev.org/c/openstack/neutron/+/824727 - test_network_basic_ops failing on centos-8-stream job - https://bugs.launchpad.net/neutron/+bug/1957941 - Unassigned - fixed in packaging but needs repo update Medium ------ - Wrong ACTIVE status of subports attached to a trunk whose parent is DOWN - https://bugs.launchpad.net/neutron/+bug/1957161 - patch: https://review.opendev.org/c/openstack/neutron/+/824378 - Assigned to Luis - NAT reflection with OVN on xena not working - https://bugs.launchpad.net/neutron/+bug/1957185 - Unassigned - DVR Router Update Error - https://bugs.launchpad.net/neutron/+bug/1957189 - Unassigned - qrouter ns leak while last service port delete because of router gw port - https://bugs.launchpad.net/neutron/+bug/1957794 - Assigned to Krzysztof - Patch: https://review.opendev.org/c/openstack/neutron/+/824008 - ha backup router ipv6 accept_ra broken - https://bugs.launchpad.net/neutron/+bug/1958149 - Unassigned Low --- - Neutron l3 agent keeps restarting (Ubuntu) - https://bugs.launchpad.net/neutron/+bug/1958128 - Unassigned - Related to fwaas and docs Needs more info --------------- - Incorrect openstack xena neutron install repo in documentation - https://bugs.launchpad.net/neutron/+bug/1956847 - Unassigned - Requires input from the reporter

1 0

[magnum] New meeting Wednesday Jan 19 09:00 AM UTC 2022 #openstack-containers
by Spyros Trigazis 17 Jan '22

17 Jan '22

Hello all, Let's restart the magnum team weekly meetings. The next meeting will happen on Wed Jan 19 09:00: AM UTC 2022 https://www.timeanddate.com/worldclock/converter.html?iso=20220119T090000&p… We can keep track of the meeting agenda in: https://etherpad.opendev.org/p/magnum-weekly-meeting Cheers, Spyros

1 0

[kolla-ansible] Gather facts strange error
by Satish Patel 17 Jan '22

17 Jan '22

Folks, I have a working cluster but today when I ran the following command I got very nasty error like the following. Even 192.168.75.144 is function node but giving super log error output that i can't copy paste here. $ sudo kolla-ansible -i /etc/kolla/multinode deploy -t nova-cell --limit 192.168.75.144 ... .... ....... PLAY [Gather facts for all hosts] ******************************************************************************************************************************************************************** TASK [Gather facts] ********************************************************************************************************************************************************************************** ok: [192.168.75.144] TASK [Group hosts to determine when using --limit] *************************************************************************************************************************************************** ok: [192.168.75.144] PLAY [Gather facts for all hosts (if using --limit)] ************************************************************************************************************************************************* TASK [Gather facts] ********************************************************************************************************************************************************************************** skipping: [192.168.75.144] => (item=192.168.75.144) ok: [192.168.75.144 -> 192.168.75.145] => (item=192.168.75.145) ok: [192.168.75.144 -> 192.168.75.146] => (item=192.168.75.146) failed: [192.168.75.144 -> 192.168.75.178] (item=192.168.75.178) => {"ansible_loop_var": "item", "item": "192.168.75.178", "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.75.178 port 22: No route to host", "unreachable": true} ok: [192.168.75.144 -> 192.168.75.179] => (item=192.168.75.179) failed: [192.168.75.144 -> 192.168.75.180] (item=192.168.75.180) => {"ansible_loop_var": "item", "item": "192.168.75.180", "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.75.180 port 22: No route to host", "unreachable": true} ok: [192.168.75.144 -> 192.168.75.181] => (item=192.168.75.181) ok: [192.168.75.144 -> 192.168.75.147] => (item=192.168.75.147) ok: [192.168.75.144 -> localhost] => (item=localhost) fatal: [192.168.75.144 -> {{ item }}]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"ansible_loop_var": "item", "changed": false, "item": "192.168.75.144", "skip_reason": "Conditional result was False", "skipped": true}, {"ansible_facts": {"ansible_all_ipv4_addresses": ["192.168.75.145"], "ansible_all_ipv6_addresses": ["fe80::3eec:efff:fe1f:1776", "fe80::f802:e3ff:fe71:e58c"], "ansible_apparmor": {"status": "disabled"}, "ansible_architecture": "x86_64", "ansible_bios_date": "02/27/2020", "ansible_bios_version": "3.3", "ansible_br_ex": {"active": false, "device": "br-ex", "features": {"esp_hw_offload": "off [fixed]", "esp_tx_csum_hw_offload": "off [fixed]", "fcoe_mtu": "off [fixed]", "generic_receive_offload": "on", "generic_segmentation_offload": "on", "highdma": "on", "hw_tc_offload": "off [fixed]", "l2_fwd_offload": "off [fixed]", "large_receive_offload": "off [fixed]", "loopback": "off [fixed]", "netns_local": "off [fixed]", "ntuple_filters": "off [fixed]", "receive_hashing": "off [fixed]", "rx_all": "off [fixed]", "rx_checksumming": "off [fixed]", "rx_fcs": "off [fixed]", "rx_gro_hw": "off [fixed]", "rx_gro_list": "off", "rx_udp_tunnel_port_offload": "off [fixed]", "rx_vlan_filter": "off [fixed]", "rx_vlan_offload": "off [fixed]", "rx_vlan_stag_filter": "off [fixed]", "rx_vlan_stag_hw_parse": "off [fixed]", "scatter_gather": "on", "tcp_segmentation_offload": "on", "tls_hw_record": "off [fixed]", "tls_hw_rx_offload": "off [fixed]", .... .... END PLAY RECAP ******************************************************************************************************************************************************************************************* 192.168.75.144 : ok=2 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0 Command failed ansible-playbook -i /etc/kolla/multinode -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla --tags nova-cell --limit 192.168.75.144 -e kolla_action=deploy /usr/local/share/kolla-ansible/ansible/site.yml

3 2

[TripleO] Gate blocker - tripleo-ci-centos-9-content-provider
by Ronelle Landy 16 Jan '22

16 Jan '22

Hello All, We have gate/check blocker which started late on Friday - and still seems to be hitting jobs in check and gate: 2022-01-16 02:53:58.796730 | primary | Error: 2022-01-16 02:53:58.796795 | primary | Problem: cannot install the best update candidate for package gcc-11.2.1-6.1.el9.x86_64 2022-01-16 02:53:58.796813 | primary | - nothing provides libgomp = 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 2022-01-16 02:53:58.796828 | primary | - nothing provides libgcc >= 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 2022-01-16 02:53:58.796904 | primary | (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) https://composes.stream.centos.org/production/latest-CentOS-Stream/compose/… does show libgomp-11.2.1-7.4.el9.x86_64.rpm <https://composes.stream.centos.org/production/latest-CentOS-Stream/compose/…> 2022-01-11 11:59 283K but http://mirror.iad3.inmotion.opendev.org/centos-stream/9-stream/BaseOS/x86_6… (for example) does not. It looks like the mirrors do not have this latest content. The failure is logged at: https://bugs.launchpad.net/tripleo/+bug/1957950. We will respond to this posting once the failure has been cleared. Thank you.

3 4

[ops][kolla][kolla-ansible][neutron] Xena upgrade connectivity issues
by Alexandros Soumplis 16 Jan '22

16 Jan '22

Hello all, I am doing an upgrade with kolla ansible from Wallaby to Xena, using source containers on ubuntu and openvswitch. After the upgrade, there is no connectivity from the VMs to the network (both provider networks and self-service) and also neutron services (dhcp, l3-agent, metadata) do not work. For the VMs I had no errors related, while for neutron services, probably due to lack of connectivity a continuous flapping of virtual routers and dhcp agents. I have downgraded neutron_openvswitch_agent, openvswitch_vswitchd and openvswitch_db to wallaby again and it everything works. I suspect there is something related to the flows created from the neutron agent but was not able to identify anything specific. Any help to debug this and identify the root cause is greatly appreciated. Thank you! a.

1 0

[all][tc] What's happening in Technical Committee: summary 14th Jan, 21: Reading: 5 min
by Ghanshyam Mann 15 Jan '22

15 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.log.html * Next week's meeting is on 20th Jan Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 19th Jan. 2. What we completed this week: ========================= * Added the cinder-solidfire charm to Openstack charms[2] * Added the cinder-nimblestorage charm to Openstack charms[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 6 open reviews for ongoing activities[5]. Z release cycle name ------------------------- Z release cycle naming process is started[6]. Nomination to collect the name are now open, feel free to propose it on wiki page[7]. TC vote on gender-neutral language change in bylaws 's TC section ------------------------------------------------------------------------------- In this week meeting, TC voted in favor of gender-neutral language change in bylaws 's TC section. They are officially approved and votes are recorded in meeting logs[8]. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[9]. SIG i18n status check -------------------------- Ian (SIG chair) is now back and fixed the IN translation issue also. So we are good here, but if you would like to help in i18n SIG, feel free to reachout to Ian. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[10] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[11]. No other updates from TC on this and we will set up a separate call to continue the discussion. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[12]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[13]. Project updates ------------------- * masakari Transfer PTL role to suzhengwei[14] * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Welcome back from the holidays and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/823805 [3] https://review.opendev.org/c/openstack/governance/+/824585 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026620.… [7] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [8] https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.log.html#… [9] https://review.opendev.org/c/openstack/governance/+/822900 [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [14] https://review.opendev.org/c/openstack/governance/+/824509 [15] https://review.opendev.org/c/openstack/governance/+/798540 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all] Proposed Z cycle schedule
by Előd Illés 15 Jan '22

15 Jan '22

Hi, As we are beyond Yoga milestone 2 it's time to start planning the next, 'Z' cycle and its release schedule, so I've prepared a draft. (Since we don't have the name yet [1] I used the *codename* Zen in the patch, that will be updated whenever the official release name is announced) The patch: https://review.opendev.org/c/openstack/releases/+/824489 (Or see the current patch set's generated schedule page [2] for easier overview.) Feel free to review it and comment on the patch if there is something that should be considered for the schedule. Thanks in advance! [1] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [2] https://1b3db30de08d0b6cba67-15d40643a81384357fc5a6da097a7ab7.ssl.cf5.rackc… Előd Illés irc: elodilles

1 0

[security-sig] Log4j vulnerabilities and OpenStack
by Jeremy Stanley 14 Jan '22

14 Jan '22

Unless you were living under a rock during most of December, you've almost certainly seen the press surrounding the various security vulnerabilities discovered in the Apache Log4j Java library. As everyone reading this list hopefully knows, OpenStack is primarily written in Python, so has little use for Java libraries in the first place, but that hasn't stopped users from asking our VMT members if OpenStack is affected. While OpenStack doesn't require any Java components, I'm aware of one Neutron driver (networking-odl) which relies on an affected third-party service: https://access.redhat.com/solutions/6586821 Additionally, "storm" component of SUSE OpenStack seems to be impacted: https://www.suse.com/c/suse-statement-on-log4j-log4shell-cve-2021-44228-vul… As does an Elasticsearch component in Sovereign Cloud Stack: https://scs.community/security/2021/12/13/advisory-log4j/ Users should, obviously, rely on their distribution vendors/suppliers to notify them of available updates for these. Is anyone aware of other, similar situations where OpenStack is commonly installed alongside Java software using Log4j in vulnerable ways? -- Jeremy Stanley

4 17