November 2021 - openstack-discuss

[neutron]Some floating IPs inaccessible after restart of L3 agent
by Kamil Madáč 29 Nov '21

29 Nov '21

Hello Everyone, We have openstack Victoria deployed since the beginning of the year with kolla/ansible in docker containers. Everything was running OK, but few weeks ago we noticed issues with networking. Our installation uses Openvswitch networking with DVR non HA routers. Everything is running smoothly until we restart L3 agent. After that, some floating ips of VMs running on the node where L3 agent is running becomes inaccessible. Workaround is to reassign floating IP to affected VM. Every restart affects same floating IPs and VMs. No errors/excpetions found in logs. I was able to find out that after restart there are missing routes for those particular floating IPs in fip- namespace, which causes that proxy arp responses are not working. After floating IP address is reassigned, routes are added by L3 agent and floating IP is working again. Looks like some sort of race condition in L3 agent, but I was not able to identify any possible existing bug. L3 agent is in version 17.0.1.dev44. Is anyone aware of any existing bug which could explain such behavior, or does anyone have idea how to solve the issue? Kamil Madáč Slovensko IT a.s.

2 3

[Image Encryption] No meeting today
by Josephine Seifert 29 Nov '21

29 Nov '21

Hi, due to a conflicting meeting today I will not be able to hold the popup team meeting. Next meeting will be next week. greetings Josphine (Luzi)

1 0

[neutron] Bug deputy, 22Nov - 28Nov
by Rodolfo Alonso Hernandez 29 Nov '21

29 Nov '21

Hello Neutrinos: This is the bug report from last week. Critical: https://bugs.launchpad.net/neutron/+bug/1952004: “ovn: Functional test may fail if northd hasn't initialized DBs yet”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819032 https://bugs.launchpad.net/neutron/+bug/1952023: “Neutron functional tests don't properly clean up ovn-northd”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819049 <https://bugs.launchpad.net/neutron/+bug/1952066> https://bugs.launchpad.net/neutron/+bug/1952066: “Scenario test test_mac_learning_vms_on_same_network fails intermittently in the ovn job”. Assigned. https://bugs.launchpad.net/neutron/+bug/1952357: “Functional tests job in the ovn-octavia-provider is broken“. Assigned. Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/819377 <https://bugs.launchpad.net/neutron/+bug/1952393> https://bugs.launchpad.net/neutron/+bug/1952393: “[OVN] neutron-tempest-plugin-scenario-ovn broken with "ovn-northd did not start"“. Assigned. Patch: https://review.opendev.org/c/openstack/devstack/+/819402 <https://bugs.launchpad.net/neutron/+bug/1952508> https://bugs.launchpad.net/neutron/+bug/1952508: “[OVN] "TestAgentMonitor.test_agent_change_controller" failing randomly“. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819502 High: https://bugs.launchpad.net/neutron/+bug/1952567: “[ml2][ovs] ports tag are missing and flood on those”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819567 <https://bugs.launchpad.net/neutron/+bug/1952550> https://bugs.launchpad.net/neutron/+bug/1952550: “[OVN] neutron_ovn_metadata_agent retrying on UUID errors infinitely”. *Unassigned* . Medium: https://bugs.launchpad.net/neutron/+bug/1951816: “[OVN] setting a IPv6 address in dns_servers is broken”. *Unassigned*. https://bugs.launchpad.net/neutron/+bug/1951872: “OVN: Missing reverse DNS for instances”. *Unassigned*. https://bugs.launchpad.net/neutron/+bug/1952055: “native firewall driver - conntrack marks too much traffic as invalid“. *Unassigned*. Low: https://bugs.launchpad.net/neutron/+bug/1951569: “[L3] L3 agent extension should always inherit from "L3AgentExtension"”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/818540 <https://bugs.launchpad.net/neutron/+bug/1952409> https://bugs.launchpad.net/neutron/+bug/1952409: “SQLAlchemy "ConnectionEvents.before_execute" signature has changed in 1.4“. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819420 Undecided/Opinion/Invalid: https://bugs.launchpad.net/neutron/+bug/1951720: "Virtual interface creation failed". More information is needed to debug this issue. https://bugs.launchpad.net/neutron/+bug/1952249: "[OVN] Created VM name overrides predefined port dns-name". The extension works as expected. Regards.

1 0

[all][tc] What's happening in Technical Committee: summary 26th Nov, 21: Reading: 10 min
by Ghanshyam Mann 26 Nov '21

26 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * 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/2021/tc.2021-11-25-15.00.log.html * Next week's meeting is video call on 2nd Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 1st Dec. 2. What we completed this week: ========================= * Add ProxySQL repository for OpenStack-Ansible[2] * Mark 'Technical Writing' SIG 'complete' as it is merged into TC [3] * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’ [4] * Retire training-labs repo [5] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[6]. Open Reviews ----------------- * 8 open reviews for ongoing activities[7]. Yoga testing runtime ------------------------- We updated the Yoga testing runtime to move from CentOS stream 8 to CentOS stream 9 and so drop the py3.6[8]. But while updating projects to drop py3.6, and discussion on whether we should change 'python_requires'>= 3.8 in setup.cfg, another (but good) discussion started on ML about whether we should continue testing py3.6 and support CentOS stream 8 and 9 both in yoga which is what RDO community plan is[8]. After discussing on ML and then with Alfredo Moralejo on TC IRC channel, we have a potential way forward on this which I have summarized on ML thread[9]. I will keep that open to get feedback or any objection to the proposed plan and accordingly we will conclude it early next week. I hope I have summarized the discussion here if not please read the ML thread for this. Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planing to fix those[10] RBAC discussion: continuing from PTG ---------------------------------------------- After last week meeting discussion, we are almost ready with this goal, if you would like to review the current direction as well as the schedule, please review it[11]. Next plan is to merge the proposed goal and then select it ASAP as m-1 is already passed for Yoga cycle. Community-wide goal updates ------------------------------------ * Two goals are proposed currently and under review. ** RBAC goal is pretty much in good shape now, feel free to review it[11] ** 'FIPS compatibility and compliance' [12]. Adjutant need maintainers and PTLs ------------------------------------------- We are waiting to hear from Braden, Albert on permission to work in this project[13]. New project 'Skyline' proposal ------------------------------------ * TC is still waiting for skyline team to respond on open queries[14]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[15]. Project updates ------------------- * Add ansible-collection-kolla repo to Kolla project[16] * Retire js-openstack-lib [17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 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/+/817245 [3] https://review.opendev.org/c/openstack/governance-sigs/+/815868 [4] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [5] https://review.opendev.org/c/openstack/governance/+/817511 [6] https://etherpad.opendev.org/p/tc-yoga-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026001… [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026024… [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] https://review.opendev.org/c/openstack/governance/+/815158 [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [16] https://review.opendev.org/c/openstack/governance/+/819331 [17] https://review.opendev.org/c/openstack/governance/+/807163 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Project-scoped app creds - Best practice
by Ryan Bannon 26 Nov '21

26 Nov '21

Hello all, Relatively new to OpenStack. To my understanding, application credentials are bound to users. Is there a way to bind them to Projects (I assume not) or, perhaps, Groups? My naive thought on a possible solution is that if a group has access to a Project, a "generic" user account that everybody has access to could be used for the application credentials. (The use case here is to not bind an app cred to an individual who might leave the organization, thus making the app cred secret lost.) Thanks, Ryan

2 5

Nova Local Disk Storage
by Seena Fallah 26 Nov '21

26 Nov '21

Hi, Is there any support for creating instances on a whole separate disk, not an LVM?

1 0

[Openstack-victoria] [IRONIC] error in network interface | baremetal node validate
by Swogat Pradhan 25 Nov '21

25 Nov '21

Hi, I am currently trying to setup openstack ironic using driver IPMI. I followed the official docs of openstack for setting everything up. When i run openstack baremetal node validate $NODE_UUID, i am getting the following error: * Unexpected exception, traceback saved into log by ironic conductor service that is running on controller: 'ServiceTokenAuthWrapper' object has no attribute '_discovery_cache' * in the network interface in command output. When i check the ironic conductor logs i see the following messages: <attached <https://mail.google.com/mail/u/0?ui=2&ik=7bb3543b01&attid=0.1&permmsgid=msg…> > Can anyone suggest a solution or a way forward. With regards Swogat Pradhan

2 4

[aodh][tacker] Support for pyparsing v 3.0.6 is required in python-aodhclient
by ueha.ayumu＠fujitsu.com 25 Nov '21

25 Nov '21

Hi aodh team, Hi I'm Ueha from tacker team. Tacker CI fails with the following error since a few days ago: ---from h-eng log--- Traceback (most recent call last): ... File "/usr/local/lib/python3.8/dist-packages/aodhclient/utils.py", line 43, in <module> expr = pp.operatorPrecedence(condition, [ AttributeError: module 'pyparsing' has no attribute 'operatorPrecedence' -------------------- As I have researched, the version of pyparsing has been updated to v3.0.6 in global requirements [1]. And operatorPrecedence was already deprecated in pyparsing v3.0.6. A patch to fix this appears to have already been posted to python-aodhclient [2]. Could you consider merging the fixes to avoid errors in the CI? For your information, it have been merged similar fixes in cinder [3] and manila [4]. [1] https://review.opendev.org/c/openstack/requirements/+/818614 [2] https://review.opendev.org/c/openstack/python-aodhclient/+/819054 [3] https://review.opendev.org/c/openstack/cinder/+/818834 [4] https://review.opendev.org/c/openstack/manila/+/818829 Regards, Ueha

1 0

[puppet] Propose retiring old stable branches(Stein, Rocky and Queens)
by Takashi Kajinami 25 Nov '21

25 Nov '21

Hello, In puppet repos we have plenty of stable branches still open, and the oldest is now stable/queens. However recently we haven't seen many backports proposed to stein, rocky and queens [1], so I'll propose retiring these three old branches now. Please let me know if anybody is interested in keeping any of these three. Note that currently CI jobs are broken in these three branches and it is likely we need to investigate the required additional pinning of dependent packages. If somebody is still interested in maintaining these old branches then these jobs should be fixed. [1] https://review.opendev.org/q/(project:%255Eopenstack/puppet-.*)AND(NOT+proj… Thank you, Takashi Kajinami

2 2

[neutron] Drivers meeting - Friday 26.11.2021 - cancelled
by Lajos Katona 25 Nov '21

25 Nov '21

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0