August 2021 - openstack-discuss - lists.openstack.org

Snapshot Attachment support in cinder
by Katari Kumar 09 Aug '21

09 Aug '21

2 2

[ops] Openstack Victoria SPICE configuration not working
by number9 09 Aug '21

09 Aug '21

I have posted this on stackexchange, but am also asking here: Running openstack on Ubuntu 20.04 with a controller node and four compute nodes. I am reading the instructions on configuring SPICE here. I will admit, I found out about which packages to install from other sites, as the instructions at the link do not actually list any software that needs to be installed. On the compute nodes and controller, I installed nova-spiceproxy On the controller I installed nova-spiceproxy and spice-html5 I followed the instructions in the link on configuring /etc/nova/nova.conf on the controller and all compute nodes. In a nutshell, when you click on console in the dashboard, it simply says: Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator. I have parsed every log in /var/log on the compute and controller nodes and found nothing that would indicate it is failing. On the compute node, I can do a ps aux and see that spice is running on the instance I am trying to connect to. I am really not sure where to go. I have tried VNC and noVNC also to no avail, each time completely removing the old configs and only adding the new. I have reverted back to SPICE to try the "simple" approach. My relevant config items in /etc/nova/nova.conf from a compute node are: [DEFAULT] vnc_eanabled = false # yes, I know it is redundant, I am following the docs... [vnc] enabled = false [spice] enabled = true agent_enabled = true html5proxy_base_url = http://10.131.39.40:6082/spice_auto.html # the above IP is the IP of the controller. server_listen = 0.0.0.0 server_proxyclient_address = 10.131.29.42 # the above IP is the IP of the controller that I pulled this config from html5proxy_host = 0.0.0.0 html5proxy_port = 6082 Back on the controller node, in /etc/nova/nova.conf I have: [spice] enabled = true agent_enabled = false html5proxy_host = 0.0.0.0 html5proxy_port = 6082 keymap = en_us I also have vnc false, as it is on the compute nodes. I will admit further, I have tried at least 20 iterations of this, just leaving off proxy ports, or thinking for a moment that the proxyclientaddress was the controller node, but none of them work. I do restart nova on the controller and all compute nodes after every change. Any ideas or directions would be appreciated. I wish there were logs, I am perhaps missing them or need to turn on debugging of some kind.

4 10

[neutron] Bug Deputy Report Aug 2 - 8th
by Oleg Bondarev 09 Aug '21

09 Aug '21

Hi everyone, Please find Bug Deputy report for the week Aug 2 - 8th below. One Critical Bug waits for an assignee, also one Medium bug is unassigned. Otherwise all good. Critical - https://bugs.launchpad.net/neutron/+bug/1938766 - Functional tests related to ovn failing with No such file or directory: '/tmp/tmps9cyr99c/ovn_northd.log' Ed · Confirmed · Unassigned High - https://bugs.launchpad.net/neutron/+bug/1938685 - ofctl timeouts lead to dvr-ha-multinode-full failures · Fix released: https://review.opendev.org/c/openstack/neutron/+/803211 · Assigned to obondarev - https://bugs.launchpad.net/neutron/+bug/1938788 - Validate if fixed_ip given for port isn't the same as subnet's gateway_ip · Won't Fix: https://review.opendev.org/c/openstack/neutron/+/803334 - abandoned after discussion - https://bugs.launchpad.net/neutron/+bug/1939144 - [OVN] Router Availability Zones doesn't work with segmented networks Edit · In Progress: https://review.opendev.org/c/openstack/neutron/+/803759 · Assigned to Lucas Alvares Gomes (lucasagomes) Medium - https://bugs.launchpad.net/neutron/+bug/1938910 - Duplicate default SG error when new system scopes are used · In progress: https://review.opendev.org/c/openstack/neutron/+/803489 · Assigned to slaweq - https://bugs.launchpad.net/neutron/+bug/1938972 - Trunk and port are residual in VM deleting scenario when southbound plugin/agent failed · Triaged · Unassigned - https://bugs.launchpad.net/neutron/+bug/1939125 - Incorect Auto schedule new network segments notification listner · Triaged · Assigned to Szymon Wróblewski (bluex) Low - https://bugs.launchpad.net/neutron/+bug/1939137 - ovn + log service plugin reports AttributeError: 'NoneType' object has no attribute 'tenant_id' · Triaged · Assigned to Kamil Sambor RFEs - https://bugs.launchpad.net/neutron/+bug/1938966 - [RFE] pps limitation on neutron ports for openvswitch agent · New: to be discussed on Drivers meeting · Unassigned Invalid - https://bugs.launchpad.net/neutron/+bug/1938826 - Install and configure controller node in Neutron · bug in deployment - https://bugs.launchpad.net/neutron/+bug/1938913 - Install and configure compute node in Neutron · not a Neutron issue Thanks, Oleg --- Advanced Software Technology Lab Huawei

1 0

[interop][cinder] review of next.json (part 2)
by Brian Rosmaita 09 Aug '21

09 Aug '21

Hello Interop WG, The Cinder team completed its discussion of what capabilities should be added as advisory in next.json at yesterday's weekly cinder meeting [0]. The tldr; is that we don't have anything to propose for inclusion in next.json at the present time. The team does have some general questions that would help us determine the suitability of some proposed capabilities. We'd like to invite someone from the Interop WG to the cinder xena R-9 virtual midcycle (Wednesday 4 August 2021, 1400-1600 UTC) so we can discuss this "live". So if someone could put 1400 UTC 4 August on their schedule for a 20 minute discussion, that would be very helpful. cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00…

3 8

Support for Automating Source Code Documentation
by Felipe Ebert 09 Aug '21

09 Aug '21

Hi, I am currently working on designing a bot to support open-source software development: the idea is that the bot can analyze code review comments, detect those related to explaining the reasons behind the implementation choices and suggest these reasons as source code comments. As the first step of this design process we would like to ask developers involved in code reviews to answer a survey (we expect it to take not more than 25 minutes): https://forms.office.com/r/9nD4HtNbTK Thanks in advance, -- Felipe Ebert Eindhoven University of Technology, The Netherlands

1 0

Re: [neutron-vpnaas][kolla-ansible][victoria] Growing memory consumption with only one VPN connection
by at 09 Aug '21

09 Aug '21

Hi, 1. There is only one, bidirectional vpn connection between project networks in two regions 2. there is no (or almost no) traffic on this vpn link 3. second region is on one host (kolla all-in-one) and situation looks the same- with vpn service enabled there is excessive Memory use (growing also about 5-6MB/ minute and forcing the system to use swapfile) there is no big cpu usage (ofcourse also due to no traffic inside VPN) It's the same case even if there's no vpn connection configured. Best regards Adam Tomas Wysłane z iPhone'a > Wiadomość napisana przez Vinh Nguyen Duc <vinhducnguyen1708(a)gmail.com> w dniu 29.06.2021, o godz. 11:04: > > > Hi Adam, > Do you think the VPN connection is use CPU and memory to encrypt the VPN traffic? > > On Mon, Jun 28, 2021 at 14:30 Adam Tomas <bkslash(a)poczta.onet.pl <mailto:bkslash@poczta.onet.pl>> wrote: > Hi, > I have problem with neutron vpnaas - after enabling vpnaas plugin everything was ok at first. I was able to create VPN connection and communication is correct. But after a week of running vpnaas (only one VPN connection created/working!) I’ve noticed, that neutron-vpnaas takes more and more memory. I have 5 processes on each controller (there should be always five? Or it is changing dynamically?): > > 42435 1545384 0.6 8.6 5802516 5712412 ? S Jun15 110:50 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545389 0.6 8.5 5735832 5645856 ? S Jun15 112:16 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545378 0.5 8.5 5734192 5643620 ? S Jun15 108:09 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545372 0.5 8.5 5731128 5641436 ? S Jun15 109:07 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545369 0.6 8.4 5637084 5547392 ? S Jun15 114:21 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > > now neutron_server takes over 27G of RAM on each controller: > > neutron_server running 10.2 27.2G > > After stopping all neutron containers and starting it again neutron takes a lot less memory: > > neutron_server running 0.5 583M > > but memory usage keeps growing (about 5-6 M every minute). > What’s wrong? When I disable vpnaas globally there’s no problem with excessive memory usage, so it’s vpnaas for sure… > > Best regards > Adam Tomas

3 2

"[Kolla][Kolla-Ansible] Ironic Node Deployment"
by Lokendra Rathour 09 Aug '21

09 Aug '21

Hi Team, I was trying to deploy Ironic Node on Kolla Ansible Setup. Document used for reference: https://docs.openstack.org/kolla-ansible/latest/reference/bare-metal/ironic… Although this document says : *" Ironic works well in Kolla, though it is not thoroughly tested as part of Kolla CI, so may be subject to instability"* We have tried 2 node Kolla Ansible *12.0.0* in order to deploy OpenStack *wallaby* release with enabled ironic for Bare-metal nodes provisioning. But facing issues in "Node Provisioning" So, has anyone tried the Baremetal Provisioning on Koll Setup? Please share /suggest any approach to achieve this. -- ~ Lokendra skype: lokendrarathour

3 4

Masakari with Kolla-ansible
by Karera Tony 08 Aug '21

08 Aug '21

Hello Team, I have deployed Openstack with Kolla-ansible on Centos8 and also enabled Masakari but I keep getting the error below in the masakari-hostmonitor.log on the controller nodes. Has anyone faced such a challenge ? 2021-08-02 18:08:52.409 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] ' controller1.aos.rw' is unstable state on cluster.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2021-08-02 18:08:52.409 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] hostmonitor skips monitoring hosts. 2021-08-02 18:09:57.476 7 WARNING masakarimonitors.hostmonitor.host_handler.handle_host [-] Corosync communication using 'ens33' is failed.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Regards Tony Karera

2 6

[all][tc] What's happening in Technical Committee: summary 6th Aug, 21: Reading: 5 min
by Ghanshyam Mann 07 Aug '21

07 Aug '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Added tap-as-a-service back to neutron stadium[1] * Defined Yoga release testing runtime[2] * Migration from Freenode to OFTC[3]. Only a few repo patches are pending to merge and can be merged in their own time[4]. 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-05-15.00.log.html * We will have next week's meeting on Aug 12th, Thursday 15:00 UTC[5]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[6] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Two open reviews for ongoing activities[7]. Wallaby testing runtime for centos8 vs centos8-stream ----------------------------------------------------------------- * Centos8 which is testing runtime for stable/wallaby cannot run on stable/wallaby testing anymore[8]. * We are discussing in TC whether to update the wallaby testing runtime from centos8->centos8-stream or stop testing centos8 itself. We will continue discussing it in the next TC meeting, feel free to join us if you have any input on this topic. Project Skyline(dashboard) proposal ------------------------------------------ * This is a new proposal about a new GUI for OpenStack name 'Skyline'. Discussion is in the initial stage and TC is not so clear if it is a proposal for a new separate project application or new repo/deliverables within the Horizon project. As the next step, TC asked to start the ML thread with all the details and then we can continue the discussion. * Meanwhile we will continue the discussion of 'required things (zuul, devstack integration etc ) we need to know about this proposal' in the next TC meeting Project updates ------------------- * Retiring js-openstack-lib [9] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [10]. * Current status: Proposed "Secure RBAC" to select for Yoga cycle[11]. PTG planning ---------------- * TC booked three slots: ** 1. Monday 15-17 UTC for TC + Community Leaders ** 2. Thursday 13-17 UTC ** 3. Friday 13-17UTC * We are collecting the PTG topics in etherpad[12], feel free to add any topic you want to discuss. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[13], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [16] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/802833 [2] https://review.opendev.org/c/openstack/governance/+/799927 [3] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [4] https://review.opendev.org/q/topic:%2522oftc%2522+status:open [5] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [6] https://etherpad.opendev.org/p/tc-xena-tracker [7] https://review.opendev.org/q/project:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/devstack/+/803071 [9] https://review.opendev.org/c/openstack/governance/+/798540 [10] https://etherpad.opendev.org/p/y-series-goals [11] https://review.opendev.org/c/openstack/governance/+/803783 [12] https://etherpad.opendev.org/p/tc-yoga-ptg [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [16] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

2 4

[neutron][ops] VLAN Provider Network
by DHilsbos＠performair.com 07 Aug '21

07 Aug '21

All; We're using OpenStack Victoria, with OVS networking (no OVN). I'm having some problems with a VLAN provider network that I added to my OpenStack. I have other VLAN provider networks, that I based this one off of. Instances are getting the tap interfaces, but these interfaces are not getting IP addresses, and when a static IP is given, they can't ping either the DHCP address or the gateway address. I have checked the switch configuration, to verify the VLAN is bound appropriately. I rebooted the whole cluster to ensure the configuration change applied. Here's a snip our plugin.ini [ml2_type_vlan] network_vlan_ranges = provider_core:55:55,provider_core:64:64,... 64 works, 55, doesn't. I'm not seeing anything concerning in /var/log/openvswitch/ovs-vswitchd.log I'm sure it's something dumb, but I'm not seeing it. Any suggestions for what else to look at? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 2