- openstack-discuss - lists.openstack.org

No server with a name or ID of "blabla' exists
by Pete Zhang 02 Jul '21

02 Jul '21

Hey, We are seeing this for the FIRST time once we rebuilt MariaDB/Galera and RabbitMQ cluster, after a period of failure/downtime. Probably there are some inconsistencies among components/services. How to clean up those hosts in BUILD state? thx. 1) There are multiple uuid of the same host stuck in BUILD 2) Deleting server failed with this error: No server with a name or ID of "blabal" exists. ERROR (CommandError): Unable to delete the specified server(s). [image: Screen Shot 2021-07-02 at 2.29.44 PM.png] [image: Screen Shot 2021-07-02 at 2.27.56 PM.png] -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[all] [] Mentors Needed! Open Source Day Summer
by Kendall Nelson 02 Jul '21

02 Jul '21

Hello! As you may or may not know, the Grace Hopper Conference is now running TWO Open Source Day events a year! The upcoming event is on July 15th[0]. If you are interested in mentoring a few individuals- i.e helping them work on some low hanging fruit for your project, please sign up here[1] and let me know! After you've done the signup and replied here, I will reach out to the organizers to make sure you are approved. At that point, please collect a few bugs you think would be good first patches for attendees and link them in the etherpad here[2]. Thank you so much! Can't wait to work with you :) -Kendall Nelson (diablo_rojo) [0] https://anitab-org.github.io/open-source-day/upcoming/ [1] https://anitab-org.github.io/open-source-day/become_a_mentor/ [2] https://etherpad.opendev.org/p/ghc-osd-summer-2021

2 1

[victoria][barbican] - UI installation
by Luke Camilleri 02 Jul '21

02 Jul '21

Hi there, I have an openstack deployment installed as a bare-metal/manual installation and would like to install the Barbican UI. Barbican is already installed and running. In my case Horizon is already installed so I guess if I follow these steps https://github.com/openstack/barbican-ui#manual-installation I would not need to clone the horizon part and also my installation already contains the local_settings.py file with all the required settings mentioned. At this point when moving into the "Install Barbican UI with all dependencies in your virtual environment" step I do not have the tools folder so I cannot really proceed with the pip install (missing virtual environment )and copying the barbican-ui/barbican_ui/enabled/_90_project_barbican_panelgroup.py and barbican-ui/barbican_ui/enabled/_91_project_barbican_secrets_panel.py to the /usr/share/openstack-dashboard/openstack_dashboard/local/enabled obviously fails A similar issue is reported here https://storyboard.openstack.org/#!/story/2008259 Thanks in advance

1 0

Extension of disk in cinder
by Salman Sheikh 02 Jul '21

02 Jul '21

Hi all, How we can add the more disk to cinder, as I have created the cinder-volumes on one disk (/sdb) the sdb is 500Gb, if i want to increase the the size of cinder-volumes then how we extend the size of cinder-volumes. how we can add more disk in order to increase the size of cinder-volume. Kindly advise

2 3

[charms] Trilio Charms 21.06 release is now available
by Billy Olsen 01 Jul '21

01 Jul '21

The 21.06 release of the Trilio charms are now available. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2106_Trilio.html == Highlights == * TrilioVault 4.1 HF1 The charms have added options to support new configurations presented in the TrilioVault 4.1 HF1 release. * S3 Support The charms now support using S3 storage as a backup target. == Thank you == Lots of thanks to the following people who contributed to this release via code changes, documentation updates and testing efforts. Alex Kavanagh Billy Olsen Chris MacNaughton Corey Bryant David Ames Liam Young Marian Gasparovic Peter Matulis -- OpenStack Charms Team

1 0

[release][tc][neutron] how to EOL unofficial branches under offical repositories
by Akihiro Motoki 01 Jul '21

01 Jul '21

Hi, I have a question about how to mark stable branches as EOL when such branches were not part of official releases at the moment of corresponding releases but the repositories which contain them became official after the release. One example happens in a repository under the neutron team. networking-odl is now part of the neutron governance but as of Ocata release it was not official. Ocata branches under the neutron stadium were marked as EOL recently, but networking-odl was not marked as EOL as it was not an official repository as of Ocata. The openstack/releases repository handles official branches under a specific release, but all branches in official repositories are under control of the openstack/releases repo. I wonder how we can mark stable/ocata branch of networking-odl repo as EOL and delete stable/ocata branch. What is the recommended way to mark such branches described above as EOL? Thanks in advance, Akihiro Motoki (irc: amotoki)

3 3

[Kolla-Ansible] Regarding stability of Ironic deployment with Kolla-Ansible
by Amit Mahajan 01 Jul '21

01 Jul '21

Hi All, We are exploring Kolla-Ansible for our multinode production grade deployment. In our setup, some workloads will also run on bare-metal, so Ironic is the key requirement. We came across the following text on the Kolla-Ansible documentation page for Rocky release. "Ironic works well in Kolla, though it is not currently tested as part of Kolla CI, so may be subject to instability." Our query is that is deployment of Ironic using Kolla-Ansible production grade for the latest OpenStack release?

3 6

[kayobe][victoria] no module named docker - deploy fail after deploy successful
by Tony Pearce 01 Jul '21

01 Jul '21

I had a successful deployment of Openstack Victoria via Kayobe with an all-in-one node running controller and compute roles. I wanted to then add 2 controller nodes to make 3 controllers and one compute. The 2 additional controllers have a different interface naming so I needed to modify the inventory. I checked this ansible documentation to figure out the changes I’d need to make [1]. The first try, I misunderstood the layout because kayobe tried to configure the new nodes interfaces with incorrect naming. In my first try I tried this inventory layout: Move existing configuration: [kayobe config] / Inventory / * To [kayobe config] / Inventory / Ciscohosts / Create new from copy of existing:[kayobe config] / Inventory / Ciscohosts / > [kayobe config] / Inventory / Otherhosts / The Otherhosts had its own host file with the 2 controllers and group_vars/controllers network interface configuration as per these two hosts. But anyway it didnt achieve the desired result so I rechecked the ansible doc [1] and decided to do this another way as follows: In my second try I first reversed the inventory change: Delete the new dir: [kayobe config] / Inventory / Otherhosts / Move back the config: [kayobe config] / Inventory / Ciscohosts / * > [kayobe config] / Inventory / Delete the empty dir: [kayobe config] / Inventory / Ciscohosts / Then create host_vars for the two individual hosts: [kayobe config] / Inventory / host_vars / cnode2 [kayobe config] / Inventory / host_vars / cnode3 And updated the single hosts inventory file [kayobe config] / Inventory / hosts This seemed to work fine, the “kayobe overcloud host configure” was successful and the hosts interfaces were set up as I desired. The issue came when doing the “kayobe overcloud service deploy” and failed with "/usr/bin/python3", "-c", "import docker” = ModuleNotFoundError: No module named 'docker' for all three nodes, where previously it (the deployment) had been successful for the all-in-one node. I do not know if this task had run or skipped before but the task is run against "baremetal" group and controllers and compute are in this group so I assume that it had been ran successfully in previous deployments and this is the weird thing because no other changes have been made apart from as described here. Verbose error output: [3] After the above error, I reverted the inventory back to the “working” state, which is basically to update the inventory hosts and removed the 2 controllers. As well as remove the whole host_vars directory. After doing this however, the same error is still seen /usr/bin/python3", "-c", "import docker” = ModuleNotFoundError. I logged into the host and tried to run this manually on the CLI and I see the same output. What I don’t understand is why this error is occurring now after previous successful deployments. To try and resolve /workaround this issue I have tried to no avail: - recreating virtual environments on all-in-one node - recreating virtual environments on ACH - deleting the [kolla config] directory - deleting .ansible and /tmp/ caches - turning off pipelining After doing the above I needed to do the control host bootstrap and host configure before service deploy however the same error persisted and I could not work around it with any of the above steps being performed. As a test, I decided to turn off this task in the playbook [4] and the yml file runs as follows: [2]. This results in a (maybe pseudo) successful deployment again, in a sense that it deploys without failure because that task does not run. After this was successful in deploying once again as it had previously had been, I added the two controller nodes using the “host_vars” and then I was able to successfully deploy again with HA controllers. Well, it is successful apart from Designate issue due to Designate already having the config [5]. I can log in to the horizon dashboard and under system information I can see all three controllers there. Could I ask the community for help with: 1. Regarding the kayobe inventory, is anything wrong with the 2nd attempt in line with Kayobe? 2. Has anyone come across this docker issue (or similar within this context of failing after being successful) and can suggest? I repeatedly get these odd issues where successful deployments then fail in the future. This often occurs after making a config change and then rolling back but the roll back does not return to a working deployment state. The fix/workaround for me in these cases is to “kayobe overcloud service destroy --yes-i-really-really-mean-it” and also re-deploy the host. [1] Best Practices — Ansible Documentation <https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.ht…> [2] modified Checking docker SDK version# command: "{{ ansible_python.execut - Pastebin.com <https://pastebin.com/xXJFHc0N> [3] TASK [prechecks : Checking docker SDK version] ********************************* - Pastebin.com <https://pastebin.com/ZmLs4LUZ> [4] /home/cv-user/kayobe-victoria/venvs/kolla-ansible/share/kolla-ansible/ansible/roles/prechecks/tasks/package_checks.yml [5] TASK [designate : Update DNS pools] ******************************************** - Pastebin.com <https://pastebin.com/USiCAXpT> Kind regards,

2 2

[kayobe][kolla-ansible][victoria]
by Tony Pearce 01 Jul '21

01 Jul '21

How do I configure the glance container to use a host-mounted NFS share? It is not covered in the kolla-ansible documentation [1]. What it does say is to set the file path using "glance_file_datadir_volume". I believe that this is relative to the container (not the host). Do I need to mount the local host (nfs) directory as a docker volume for glance as additional step? If so, how do I achieve this with kayobe / kolla-ansible? Some background: After a successful deployment of 3 controller nodes I have one glance service which is dependent on one of these controller nodes being available always. My intent is to provide a NFS share for glance that removes the dependency. [1] OpenStack Docs: Glance - Image service <https://docs.openstack.org/kolla-ansible/victoria/reference/shared-services…> Kind regards, Tony Pearce

2 2

[nova][placement] Openstack only building one VM per machine in cluster, then runs out of resources
by Jeffrey Mazzone 01 Jul '21

01 Jul '21

Hello, I am installing Openstack Ussuri and am running into an issue when using Availability Zones. I initially thought it was a quota issue but that no longer seems to be the case. I started a thread on serverfault and was recommended to submit these questions here as well. Here is the original link: https://serverfault.com/questions/1064579/openstack-only-building-one-vm-pe… The issue is still, I can successfully build vms on every host, but only one vm per host. The size of the initial vm does not matter. Since I posted the thread above, I have redeployed the entire cluster, by hand, using the docs on openstack.org<http://openstack.org>. Everything worked as it should, I created 3 test aggregates, 3 test availability zones, with no issues for about a month. All of a sudden, the system reverted to no longer allowing more than one machine to be placed per host. There has been no changes to the controller. I have enabled placement logging now so I can see more information but I don’t understand why its happening. Example. Start with a host that has no vms on it: ~# openstack resource provider usage show 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+-------+ | resource_class | usage | +----------------+-------+ | VCPU | 0 | | MEMORY_MB | 0 | | DISK_GB | 0 | +----------------+-------+ Create 1 vm with 4 cores ~# openstack resource provider usage show 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+-------+ | resource_class | usage | +----------------+-------+ | VCPU | 4 | | MEMORY_MB | 0 | | DISK_GB | 0 | +----------------+-------+ The inventory list for that provider is: ~# openstack resource provider inventory list 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+------------------+----------+----------+----------+-----------+--------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | +----------------+------------------+----------+----------+----------+-----------+--------+ | VCPU | 16.0 | 1 | 64 | 0 | 1 | 64 | | MEMORY_MB | 1.5 | 1 | 515655 | 512 | 1 | 515655 | | DISK_GB | 1.0 | 1 | 7096 | 0 | 1 | 7096 | +----------------+------------------+----------+----------+----------+-----------+--------+ Trying to start another vm on that host fails with the following log entries: scheduler.log "status": 409, "title": "Conflict", "detail": "There was a conflict when trying to complete your request.\n\n Unable to allocate inventory: Unable to create allocation for 'VCPU' on resource provider conductor.log Failed to schedule instances: nova.exception_Remote.NoValidHost_Remote: No valid host was found. There are not enough hosts available. placement.log Over capacity for VCPU on resource provider 3f9d0deb-936c-474a-bdee-d3df049f073d. Needed: 4, Used: 8206, Capacity: 1024.0 As you can see, the used value is suddenly 8206 after a single 4 core vm is placed on it. I don’t understand what im missing or could be doing wrong. Im really unsure where this value is being calculated from. All the entries in the database and via openstack commands show the correct values except in this log entry. Has anyone experienced the same or similar behavior? I would appreciate any insight as to what the issue could be. Thanks in advance! -Jeff M

5 14

[neutron] Drivers meeting agenda for 2.07.2021
by Slawek Kaplonski 01 Jul '21

01 Jul '21

Hi, We have 2 RFEs to discuss on tomorrow's meeting: https://bugs.launchpad.net/neutron/+bug/1933517 - [RFE][OVN] Create an intermediate OVS bridge between VM and intergration bridge to improve the live-migration process https://bugs.launchpad.net/neutron/+bug/1930866 - [RFE] preventing from deleting a port used by an instance (locked instance can be rendered broken by deleting port) We also have 2 not yet triaged RFEs: https://bugs.launchpad.net/neutron/+bug/1932154 https://bugs.launchpad.net/neutron/+bug/1933222 Please check them, ask questions/comments/whatever You need to triage them so we can discuss on next drivers meetings :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Fwd: [TRIPLEO] - ZUN Support in TripleO
by Lokendra Rathour 30 Jun '21

30 Jun '21

Hello Everyone, We are curious in understanding the usage of ZUN Sevice in TripleO with respect to which we have questions as below: 1. Does TripleO Support ZUN? 2. If not then, is there any alternative to deploy containerize services in TripleO? Any support with respect to the questions raised will definitely help us in deciding the tripleO usage. -- ~ Lokendra skype: lokendrarathour

6 7

[openstack] [DC-DC Setup] [Replication] Correct approach to a DC-DC setup for Openstack (victoria)
by Swogat Pradhan 30 Jun '21

30 Jun '21

Hi, I am trying to setup a DC-DC setup in openstack victoria, I have 2 numbers of all in one setup (controller, compute) with shared mysql and rabbitmq cluster and am using ceph image replication and configuring cinder replication on top of it. So when the 1st node goes down then i will perform a 'cinder failover-host node1' and then do a nova-evacuate to failover to the 2nd DC setup and once the node 1 comes up i will use cinder failback and live migration from node2 to node1. **i am facing some minor issues in this setup which I will ask once I know this is the right approach to the DC-DC concept. Can you please shed some light on this being the right approach or not and if not then how can i improve it? With regards Swogat pradhan

1 1

[all][tc] Technical Committee next weekly meeting on July 1st at 1500 UTC
by Ghanshyam Mann 30 Jun '21

30 Jun '21

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

1 1

[Swift] Object replication failures on newly upgraded servers
by Mark Kirkwood 30 Jun '21

30 Jun '21

HI, I'm in the process of upgrading a Swift cluster from 2.7/Mitaka to 2.23/Train. While in general it seems to be going well, I'm noticing non-zero object replication failures on the upgraded nodes only, e.g: $ curl http://localhost:6000/recon/replication/object {"replication_last": 1622156911.019487, "replication_stats": {"rsync": 40580, "success": 4141229, "attempted": 2081856, "remove": 4083, "suffix_count": 14960481, "failure": 26550, "hashmatch": 4127197, "failure_nodes": {"10.11.18.67": {"obj08": 2348, "obj09": 60, "obj10": 3030, "obj02": 34, "obj03": 25, "obj01": 44, "obj06": 1498, "obj07": 28, "obj04": 69, "obj05": 36}, "10.11.18.68": {"obj03": 6901, "obj01": 293, "obj06": 1901, "obj04": 10281, "obj10": 1}, "10.12.18.76": {"obj10": 1}}, "suffix_sync": 1785, "suffix_hash": 2778}, "object_replication_last": 1622156911.019487, "replication_time": 1094.7836411476135, "object_replication_time": 1094.7836411476135} Examining the logs (/var/log/swift/object.log and /var/log/syslog) these are not throwing up any red flags (i.e no failing rsyncs noted). Any suggesting about how to get more information about what went wrong e.g: "10.11.18.67": {"obj08": 2348}, how to find what those 2348 errors were? regards Mark P.s: basic sanity checking is ok - uploaded objects go where they should and can be retrieved for 2.7 or 2.23 servers ok (the old and new version servers agree about object placement)

2 4

[Interop] board approved our new process
by Arkady Kanevsky 30 Jun '21

30 Jun '21

Team, I would like to share with you that OIF board had approved our https://opendev.org/osf/interop/src/branch/master/doc/source/process/2021A.… process. That includes that co-chairs of the working group are elected by the group. The Board punted back to WG on how to handle human readable form of guidelines. More on it on Friday. Congratulations to all for making it happen. Thanks, -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

1 0

[kolla][wallaby] OVS drops RARP packets by QEMU upon live-migration
by Gargano Andrea 30 Jun '21

30 Jun '21

Hello all, we have a new kolla-ansible wallaby installation, during live migration we lose a lot of packages as reported on bug 1815989. Could you please give us some advices to fix it? Thank you. Andrea Gargano

3 6

[tc][all] What should we have as community goals for Y series?( Starting community-wide goals ideas)
by Rico Lin 30 Jun '21

30 Jun '21

Dear all, We're now in R-22 week for Xena cycle which sounds like a perfect time to start calling for community-wide goals ideas for Y-series. According to the goal process schedule [1], we need to find potential goals, and champions before Xena milestone-1 and provide proper discussion in the community right after that to give a clear view and detail on each goal. And if we would like to keep up with the schedule, we should start right away to identify potential goals. So please help to provide ideas for Y series community-wide goals in [2]. Community-wide goals are important in terms of solving and improving a technical area across OpenStack as a whole. It has a lot more benefits to be considered from users as well from a developer's perspective. See [3] for more details about community-wide goals and processes. Also, you can refer to the backlogs of community-wide goals from this[4] and victoria cycle goals[5] (also ussuri[6]). We took cool-down cycle goal step for Xena cycle [7], so no selected goals for Xena. [1] https://governance.openstack.org/tc/goals/#goal-selection-schedule [2] https://etherpad.opendev.org/p/y-series-goals [3] https://governance.openstack.org/tc/goals/index.html [4] https://etherpad.openstack.org/p/community-goals [5] https://etherpad.openstack.org/p/YVR-v-series-goals [6] https://etherpad.openstack.org/p/PVG-u-series-goals [7] https://review.opendev.org/c/openstack/governance/+/770616 *Rico Lin* OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

10 13

[TripleO] moving stable/stein and stable/queens to End of Life
by Marios Andreou 30 Jun '21

30 Jun '21

Hello TripleO, I am proposing to move to End of Life for stable/stein and stable/queens branches across all TripleO repos (stein [1] and queens [2]). The proposal was introduced and discussed in recent TripleO irc meetings [3] and there have been no objections so far. The main reason is to allow us to focus our resources on the more active branches, train ussuri victoria wallaby and xena (!). We moved the rocky branch to EOL last cycle with [4] for the same reason. I think this move is well justified as these branches are getting relatively few commits lately (so calling into question the resources we are dedicating to running and maintaining the check, gate and 3rd party periodic/promotion lines). Looking at tripleo-common, python-tripleoclient and tripleo-heat-templates I counted 9 commits to stable/stein and 23 commits to stable/queens since November 2020 (details on those numbers at [5][6]). Please speak up if you have any concerns or questions about the proposal. If there are none then the next step is to post a review against the releases repo to make it official. regards, marios [1] https://releases.openstack.org/teams/tripleo.html#stein [2] https://releases.openstack.org/teams/tripleo.html#queens [3] https://meetings.opendev.org/meetings/tripleo/2021/tripleo.2021-06-08-14.00… [4] https://review.opendev.org/c/openstack/releases/+/774244 [5] https://gist.github.com/marios/b3155fe3b1318cc26bfa4bc15c764a26#gistcomment… [6] https://gist.github.com/marios/b3155fe3b1318cc26bfa4bc15c764a26#gistcomment…

2 2

[release][stable] stale old branches probably should be EOL'd
by Előd Illés 30 Jun '21

30 Jun '21

Hi Release Team, now that stable/ocata is mostly tagged with ocata-eol tag it turned out that there are repositories that did not have any deliverables in ocata (not even a yaml under deliverables/ocata in the release repository). In fact, I've checked and there are several examples from the past where repositories have old stable branches open [1] that should be $series-eol tagged and deleted in my understanding. I think these old stable branches were skipped accidentally during the old EOL processing, so I would suggest to tag these with $series-eol and then delete the old branches. I don't see any reason these branches should be kept open. But let me know if I miss anything! If we stick to the tagging + deletion, then the next question is how to achieve this. There are a couple of options: 1. use the existing tools: such as creating a yaml file under deliverables/$series/ and add the $series-eol tag for the given repositories (I understand that these are not 'real' deliverables, but does that cause any issue for us?) 2. implement some new mechanism, similar to option 1, but clearly indicate that the tagging does not create any deliverables 3. manual tagging + deletion I think the 1st option is the easiest and since we already have the whole process there, we can simply use the existing tool. So what do you think? - Is that OK to tag these open old stable branches with $series-eol tag and then delete them? - If yes, which option from the above list is acceptable, or what else can we do? Thanks for the answers/ideas in advance, Előd [1] http://paste.openstack.org/show/806995/

4 5

Question for Openstack installation!!
by dionysa.varvarigou 30 Jun '21

30 Jun '21

Hello, Is it possible that I could have some guidance for making the Horizon for Wallaby working on ubuntu 20.04? I followed all the steps for its installation and configuration, but I cannot make it to work. The problem is that once I put in my browser my <ip address>/horizon/, it gives me the default apache2 page. So, I tried to find the available site for horizon but I cannot find it by any means. I have triple checked the horizon conf file and I have done everything according to the documentation (https://docs.openstack.org/horizon/wallaby/install/install-ubuntu.html) I tried to google and see if there is any troubleshooting but nothing. I do not know what else to do... So, is it possible that I could get some help??? I hope to hear from you soon.. Have a great day, Dionysia

1 0

[Diversity] Diversity and Inclusion July Meeting Update
by Amy Marrich 30 Jun '21

30 Jun '21

Due to most US companies having July 5th off, we will be moving the Jully D&I WG meeting Please join us Monday, July 19th at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Thanks, Amy (spotz)

1 0

[cinder] Bug deputy report for week of 2021-30-06
by Sofia Enriquez 30 Jun '21

30 Jun '21

Hello, This is a bug report from 2021-16-06 to 2021-23-06. You're welcome to join the Cinder Bug Meeting today. Weekly on Wednesday at 1500 UTC on #openstack-cinder Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium: - https://bugs.launchpad.net/cinder/+bug/1933835 "[storwize svc] In _update_replication_group On failure it should not leave the volume relation in stopped state and RCCG in stopped state". Unassigned Undecided / Invalid - https://bugs.launchpad.net/cinder/+bug/1933443 " Backup deleted but data not deleted". Unassigned Cheers, Sofia Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[cinder] propose Sofia Enriquez for cinder core
by Brian Rosmaita 30 Jun '21

30 Jun '21

Sofia Enriquez (enriquetaso on IRC) has been active the past few cycles submitting patches, doing reviews, and participating in the Cinder weekly meeting, PTGs, and midcycles. She has also been acting as the Cinder Bug Deputy for Xena and has been running the Bug Squad meeting each week. Something I particularly appreciate is that she has included the cinder-tempest-plugin in her range of patches and reviews. Cinder and its various deliverables make up a large code base. Sofia has demonstrated a willingness and capacity to learn about the code, and I anticipate that she will continue to deepen her cinder knowledge as she continues to work in the project. At the same time, I believe that she is self-aware enough to know the limits of her knowledge and can be trusted not to approve patches that she doesn't understand. Above all, she will bring some much needed review bandwidth to the project. In the absence of objections, I'll add Sofia to the core team just before the next Cinder team meeting (Wednesday, 30 June at 1400 UTC). Please communicate any concerns to me before that time. cheers, brian

10 10

[qa] Cancelling Office Hour on July 6th
by Martin Kopec 29 Jun '21

29 Jun '21

Hi everyone, we are cancelling the next Office Hour - July 6th - due to PTOs and public holidays. QA wiki page: https://wiki.openstack.org/wiki/QA#Projects Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

1 0

[nova][osc][api-sig] How strict should our clients be?
by Stephen Finucane 29 Jun '21

29 Jun '21

Hey, We have an interesting problem that I wanted to poll opinions on. In OSC 5.5.0, we closed most of the gaps between novaclient and openstackclient. As part of these changes, we introduced validation of a number of requests such as validating enum-style values. For example, [1][2][3]. This validation already occurs on the server side, but by adding it to the client side we prevent users sending invalid requests to the server in the first place and allow users to discover the correct API behaviour from the client rather than having to read the API docs or use trial and error. Now, an issue has been opened against OSC. Apparently someone has been relying on a bug in Nova to pass a different value to the API that what the schema should have allowed, and they are dismayed that the client no longer allows them to do this. They have asked [4][5] that we relax the client-side validation to allow them to continue relying on this bug. As you can probably tell from my comments, this seems to me to be an open and shut case: you shouldn't fork an OpenStack API and you shouldn't side-step validation. However, I wanted to see if anyone disagreed and thought there was merit in loose or no validation of API requests made via our clients. Let me know what you think, Stephen [1] https://github.com/openstack/python-openstackclient/blob/5.5.0/openstackcli… [2] https://github.com/openstack/python-openstackclient/blob/5.5.0/openstackcli… [3] https://github.com/openstack/python-openstackclient/blob/5.5.0/openstackcli… [4] https://storyboard.openstack.org/#!/story/2008975 [5] https://github.com/openstack/python-openstackclient/commit/ab0b1fe885ee0a21…

9 16

[kolla][wallaby] pull error
by Ignazio Cassano 29 Jun '21

29 Jun '21

Hello, I pulled images two weeks ago and now I am trying to pull again but I got the followings error: TASK [common : include_tasks] ************************************************************************************************************************************************************************************* included: /usr/local/share/kolla-ansible/ansible/roles/common/tasks/pull.yml for localhost TASK [common : Pulling common images] ***************************************************************************************************************************************************************************** failed: [localhost] (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': 'kolla/ubuntu-source-fluentd:wallaby', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) => {"ansible_loop_var": "item", "changed": true, "item": {"key": "fluentd", "value": {"container_name": "fluentd", "dimensions": {}, "enabled": true, "environment": {"KOLLA_CONFIG_STRATEGY": "COPY_ALWAYS"}, "group": "fluentd", "image": "kolla/ubuntu-source-fluentd:wallaby", "volumes": ["/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "kolla_logs:/var/log/kolla/", "fluentd_data:/var/lib/fluentd/data/"]}}, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_w1uzvf82/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1195, in main\\n File \"/tmp/ansible_kolla_docker_payload_w1uzvf82/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 288, in __init__\\n File \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 131, in __init__\\n self._auth_configs = auth.load_config(\\nTypeError: load_config() got an unexpected keyword argument \\'config_dict\\'\\n'"} failed: [localhost] (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': 'kolla/ubuntu-source-kolla-toolbox:wallaby', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/', '/run/openvswitch:/run/openvswitch:shared'], 'dimensions': {}}}) => {"ansible_loop_var": "item", "changed": true, "item": {"key": "kolla-toolbox", "value": {"container_name": "kolla_toolbox", "dimensions": {}, "enabled": true, "environment": {"ANSIBLE_LIBRARY": "/usr/share/ansible", "ANSIBLE_NOCOLOR": "1"}, "group": "kolla-toolbox", "image": "kolla/ubuntu-source-kolla-toolbox:wallaby", "privileged": true, "volumes": ["/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "/dev/:/dev/", "/run/:/run/:shared", "kolla_logs:/var/log/kolla/", "/run/openvswitch:/run/openvswitch:shared"]}}, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_u6x9d04r/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1195, in main\\n File \"/tmp/ansible_kolla_docker_payload_u6x9d04r/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 288, in __init__\\n File \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 131, in __init__\\n self._auth_configs = auth.load_config(\\nTypeError: load_config() got an unexpected keyword argument \\'config_dict\\'\\n'"} failed: [localhost] (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': 'kolla/ubuntu-source-cron:wallaby', 'environment': {'DUMMY_ENVIRONMENT': 'kolla_useless_env'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => {"ansible_loop_var": "item", "changed": true, "item": {"key": "cron", "value": {"container_name": "cron", "dimensions": {}, "enabled": true, "environment": {"DUMMY_ENVIRONMENT": "kolla_useless_env"}, "group": "cron", "image": "kolla/ubuntu-source-cron:wallaby", "volumes": ["/etc/kolla/cron/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "kolla_logs:/var/log/kolla/"]}}, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_z0tqur4o/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1195, in main\\n File \"/tmp/ansible_kolla_docker_payload_z0tqur4o/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 288, in __init__\\n File \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 131, in __init__\\n self._auth_configs = auth.load_config(\\nTypeError: load_config() got an unexpected keyword argument \\'config_dict\\'\\n'"} PLAY RECAP ******************************************************************************************************************************************************************************************************** localhost : ok=5 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 Any help, please ? Ignazio

1 1

[masakari] PTL on vacations, next two meetings cancelled
by Radosław Piliszek 29 Jun '21

29 Jun '21

Hello, Propagating this information from today's meeting: The next two Masakari meetings (July 6 and 13) are cancelled because I will be on vacations. Kind regards, -yoctozepto

1 0

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 29 Jun '21

29 Jun '21

Quick reminder that this week's Cinder team meeting on Wednesday 30 June, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. These are the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. * The meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-xena-meetings cheers, brian

1 0

October 2021 PTG Dates & Registration
by Ashlee Ferguson 29 Jun '21

29 Jun '21

Hi everyone, We're happy to announce the next virtual PTG[1] will take place October 18-22, 2021! Registration is now open[2]. The virtual PTG is free to attend, but make sure to register so you recieve important communications like schedules, passwords, and other relevant updates. Next week, keep an eye out for info regarding team sign-ups. Can't wait to see you all there! Ashlee [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com

1 0

[neutron] bug deputy report (Jun 21-27)
by Akihiro Motoki 29 Jun '21

29 Jun '21

Hi team, I was a bug deputy in neutron last week. Sorry for late. Summary ======= The following needs attentions from OVN and DVR folks. - 1 bug on OVN driver related to security group rule deletion needs investigation - 2 DVR-specific bugs need to be triaged by L3 DVR folks I also marked a bug on explicit deletion of a port used by nova as RFE. Needs attentions ================ * [OVN] neutron with ovn returns Conflict on security group rules delete https://bugs.launchpad.net/bugs/1933638 Medium, unassigned, specific to OVN mechanism driver * Untriaged specific to DVR * snat arp entry missing in qrouter namespace https://bugs.launchpad.net/neutron/+bug/1933092 * Unable to update mtu on DVR snat https://bugs.launchpad.net/bugs/1933273 * OSError: Premature eof waiting for privileged process error in Ussuri release of Neutron https://bugs.launchpad.net/neutron/+bug/1933813 Collecting more information from the bug author * Unassigned Gate failure * [Fullstack] TestLegacyL3Agent.test_mtu_update fails sometimes https://bugs.launchpad.net/neutron/+bug/1933234 Bugs with assignees =================== * New with assignees * [OVN] Live migration of network sensitive VMs breaks communication https://bugs.launchpad.net/neutron/+bug/1933517 New, Medium, assigned to ralonsoh * Explicitly provide a DB context when executing a DB transaction https://bugs.launchpad.net/neutron/+bug/1933321 New, Wishlist, this is a tracker for all patches to decorate db transactions * Confirmed/Triaged * Unable to show security groups for non-admin users if custom policies using. https://bugs.launchpad.net/bugs/1933242 Confirmed, High, Assigned to amotoki * missing global_request_id in neutron_lib context from_dict method https://bugs.launchpad.net/bugs/1933802 Low, Confirmed, potential improvement in neutron-lib Context.from_dict() Unassigned but amotoki can take care of it. * In Progress * [OVN] The type of ovn controller is not recognized as a gateway agent https://bugs.launchpad.net/bugs/1933401 * L3 DB FloatingIP callbacks improvements https://bugs.launchpad.net/bugs/1933502 * Stable branches * [stable/train] Backported patch introduced incompatible method calls for py2.7 https://bugs.launchpad.net/bugs/1933366 High, New, assigned to ralonsoh RFEs ==== * locked instance can be rendered broken by deleting port https://bugs.launchpad.net/bugs/1930866 It was filed as a normal bug, but it requires an API change, so I triaged it as RFE. * [RFE] Add distributed datapath for metadata https://bugs.launchpad.net/neutron/+bug/1933222

1 0

Error creating VMs
by open infra 28 Jun '21

28 Jun '21

Hi After setting up OpenStack environment using STX R5 (two controllers, two storage nodes and one worker), I have deployed a VM. VM ended up with ERROR status. I highly appreciate if someone can guide to dig further (what logs to check ) or to fix this issue. http://paste.openstack.org/show/806626/ Regards Danishka

2 14

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 28 Jun '21

28 Jun '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is cancelled. Our next meeting will be July 06th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

How to get information about the available space in all cinder-volume
by Salman Sheikh 28 Jun '21

28 Jun '21

Dear experts, I have made cinder-volume /dev/sdb on controller as well as compute node, how do i get the information of space available in cinder.

2 2

[cinder] OpenStack lvm and Shared Storage
by pradyumna borge 28 Jun '21

28 Jun '21

Hi, In a mulit-node setup do we need to provide shared storage via Cinder when setting up the second compute node? In a typical mulit-node setup we will have: 1. First node as Controller node acting as a Compute node too. This will have Cinder *lvm*. 2. Second node as Compute node. 1. Will this node have any storage via lvm? If yes then how will the first compute node access storage on the second node? 2. Likewise, how can the VMs on this second node access storage on the first compute node? My other questions are: 1. So if I spawn a VM on the second Compute node, where will the disks of the VM reside? 2. Can I attach attach a disk on the first node to a VM on the second node? 3. Do I have to configure NFS storge as shared storage for Cinder? 4. Does Cinder take care of sharing the disks (I dont think so) 5. What are the steps to setup devstack for multi-node and multi storage (nfs and lvm) ~ shree

3 2

[Ironic] No usptream meeting on July 5th
by Iury Gregory 28 Jun '21

28 Jun '21

Hello Ironicers! During our weekly meeting today we agreed that we will skip the next meeting due to holidays in the US and other countries! -- *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>*

1 0

[dev][infra][tact-sig] Zuul 4.6.0 and associated job changes
by Jeremy Stanley 28 Jun '21

28 Jun '21

Today at 14:00 UTC the OpenDev Collaboratory upgraded its deployment of Zuul, coinciding with the 4.6.0 security release. This release disabled or changed a number of features which could previously be leveraged to take over executors or obtain decrypted copies of secret data, necessitating adjustments to some jobs. I think we've now addressed the majority of the central job resources which were impacted, but there are almost certainly less-frequently-exercised jobs which are still configured to do things which will no longer work. There were likely some strange-looking failures, particularly in promote and post pipeline builds, between 15:00 and 19:00 UTC today, so if you need something rerun for any reason please do reach out. The two main categories of new bugs which will need fixing are: * Use of Jinja2 templating in secret definitions * Setting ansible_connection, ansible_host, ansible_python_interpreter, ansible_shell_executable, or ansible_user The full release notes can be found in the release announcement here: http://lists.zuul-ci.org/pipermail/zuul-announce/2021-June/000096.html If you run into a new problem in one of your jobs and you believe it may be related to the above or similar fallout from the changes in Zuul 4.6.0 and need assistance, please don't hesitate to contact the TaCT SIG in the #openstack-infra channel on the OFTC IRC network or by replying to this mailing list thread. Apologies for any disruption this update may have caused, and thanks for your understanding. -- Jeremy Stanley

6 9

[kolla][monasca] thresh keeps dying
by Tomasz Rutkowski 28 Jun '21

28 Jun '21

can someone direct me where to search for the cause? as I understand failing to submit the topology to storm cluster shouldn't be final, and the process just dissapers there... + exec /opt/storm/bin/storm jar /monasca-thresh-source/monasca-thresh-stable-victoria/thresh/target/monasca-thresh-2.4.0-SNAPSHOT-shaded.jar -Djava.io.tmpdir=/var/lib/monasca-thresh/data monasca.thresh.ThresholdingEngine /etc/monasca/thresh-config.yml monasca-thresh Running: /usr/lib/jvm/java-8-openjdk-amd64/bin/java -client -Ddaemon.name= -Dstorm.options= -Dstorm.home=/opt/storm -Dstorm.log.dir=/var/log/kolla/storm -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib -Dstorm.conf.file= -cp /opt/storm/*:/opt/storm/lib/*:/opt/storm/extlib/*:/monasca-thresh-source/monasca-thresh-stable-victoria/thresh/target/monasca-thresh-2.4.0-SNAPSHOT-shaded.jar:/opt/storm/conf:/opt/storm/bin -Dstorm.jar=/monasca-thresh-source/monasca-thresh-stable-victoria/thresh/target/monasca-thresh-2.4.0-SNAPSHOT-shaded.jar -Dstorm.dependency.jars= -Dstorm.dependency.artifacts={} -Djava.io.tmpdir=/var/lib/monasca-thresh/data monasca.thresh.ThresholdingEngine /etc/monasca/thresh-config.yml monasca-thresh 687 [main] INFO m.t.ThresholdingEngine - -------- Version Information -------- 692 [main] INFO m.t.ThresholdingEngine - monasca-thresh-2.4.0-SNAPSHOT-2021-06-06T08:32:08-${buildNumber} 693 [main] INFO m.t.ThresholdingEngine - Instantiating ThresholdingEngine with config file: /etc/monasca/thresh-config.yml, topology: monasca-thresh 1000 [main] INFO o.h.v.i.u.Version - HV000001: Hibernate Validator 5.2.1.Final 1197 [main] INFO m.t.ThresholdingEngine - local set to false 1312 [main] INFO m.t.i.t.MetricSpout - Created 1340 [main] INFO m.t.i.t.EventSpout - EventSpout created 1516 [main] WARN o.a.s.u.Utils - STORM-VERSION new 1.2.2 old null 1516 [main] INFO m.t.ThresholdingEngine - submitting topology monasca-thresh to non-local storm cluster 1549 [main] INFO o.a.s.StormSubmitter - Generated ZooKeeper secret payload for MD5-digest: -7012431400424907995:-9108807134284416946 1728 [main] INFO o.a.s.u.NimbusClient - Found leader nimbus : storm1:6627 1751 [main] INFO o.a.s.s.a.AuthUtils - Got AutoCreds [] 1756 [main] INFO o.a.s.u.NimbusClient - Found leader nimbus : storm1:6627 Exception in thread "main" java.lang.RuntimeException: Topology with name `monasca-thresh` already exists on cluster at org.apache.storm.StormSubmitter.submitTopologyAs(StormSubmitter.java:237) at org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:387) at org.apache.storm.StormSubmitter.submitTopology(StormSubmitter.java:159) at monasca.thresh.ThresholdingEngine.run(ThresholdingEngine.java:111) at monasca.thresh.ThresholdingEngine.main(ThresholdingEngine.java:82) regards -- Tomasz Rutkowski

2 2

[kolla-ansible] [swift] access denied to various APIs
by Bernd Bausch 28 Jun '21

28 Jun '21

I set up a cloud with the Victoria version of Kolla-Ansible. I enabled Swift and configured Swift as backend for Glance and Cinder-Backup. The Glance backend works, the Cinder-Backup backend doesn't. Furthermore, as a non-admin user I can't do anything with Swift. These two headscratchers that may or may not be related. I seek for help how to troubleshoot this. *Headscratcher 1*: Swift doesn't accept unauthenticated /info API, although expose_info is explicitly set to "true". This is why Cinder-Backup fails; it performs this API when starting up: curl http://192.168.122.253:8080/info {"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}} When I add a valid token, this works. *Headscratcher 2*: Swift refuses access except for the admin role. I get this when I don't have the admin role: $ source demorc.sh $ swift stat Account HEAD failed: http://192.168.122.253:8080/v1/AUTH_06d5618863294187bf46c611c0ebb4a7 403 Forbidden Failed Transaction ID: tx7e8d958e3c7b410880000-0060d81a25 To add insult to injury, I don't see relevant messages in the centralized Elasticsearch log, and logging does not go to any log files. Any thoughts? Thanks, Bernd

2 1

[wallaby][magnum] magnum-conductor service crash
by Ammad Syed 28 Jun '21

28 Jun '21

Hi, I am using openstack wallaby on ubuntu20.04. My service of magnum-conductor is getting crashed with below error in syslog of ubuntu. Jun 26 22:52:17 orchestration magnum-conductor[173714]: /usr/lib/python3/dist-packages/magnum/drivers/common/driver.py:38: PkgResourcesDeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately. Jun 26 22:52:17 orchestration magnum-conductor[173714]: yield entry_point, entry_point.load(require=False) Jun 26 22:52:17 orchestration magnum-conductor[173714]: /usr/lib/python3/dist-packages/kubernetes/client/apis/init.py:10: DeprecationWarning: The package kubernetes.client.apis is renamed and deprecated, use kubernetes.client.api instead (please note that the trailing s was removed). Jun 26 22:52:17 orchestration magnum-conductor[173714]: warnings.warn( Jun 26 22:52:17 orchestration magnum-conductor[173714]: /usr/lib/python3/dist-packages/magnum/drivers/common/driver.py:38: PkgResourcesDeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately. Jun 26 22:52:17 orchestration magnum-conductor[173714]: yield entry_point, entry_point.load(require=False) Jun 26 22:52:17 orchestration magnum-conductor[173714]: Traceback (most recent call last): Jun 26 22:52:17 orchestration magnum-conductor[173714]: File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 476, in fire_timers Jun 26 22:52:17 orchestration magnum-conductor[173714]: timer() Jun 26 22:52:17 orchestration magnum-conductor[173714]: File "/usr/lib/python3/dist-packages/eventlet/hubs/timer.py", line 59, in call Jun 26 22:52:17 orchestration magnum-conductor[173714]: cb(*args, **kw) Jun 26 22:52:17 orchestration magnum-conductor[173714]: File "/usr/lib/python3/dist-packages/eventlet/semaphore.py", line 152, in _do_acquire Jun 26 22:52:17 orchestration magnum-conductor[173714]: waiter.switch() Jun 26 22:52:17 orchestration magnum-conductor[173714]: greenlet.error: cannot switch to a different thread Any advice how to fix it ? -- Regards, Ammad

1 0

[neutron-vpnaas][kolla-ansible][victoria] Growing memory consumption with only one VPN connection
by Adam Tomas 28 Jun '21

28 Jun '21

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

1 0

[kolla] URGENT to cores - DO NOT MERGE patches
by Radosław Piliszek 27 Jun '21

27 Jun '21

Please DO NOT MERGE any changes until issues mentioned in thread [1] are resolved. The reason is that these cause the crucial jobs to never run. I see we have merged one job without proper testing already. [2] You can see only tox testing ran there. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023291.html [2] https://review.opendev.org/c/openstack/kolla-ansible/+/779204 -yoctozepto

1 1

[cinder] [replication] Error in cinder replication | Openstack Victoria
by Swogat Pradhan 25 Jun '21

25 Jun '21

Hi, I am trying to configure cinder replication with ceph as backend and i followed this URL to configure the cinder replication: https://netapp.io/2016/10/14/cinder-replication-netapp-perfect-cheesecake-r… and http://www.sebastien-han.fr/blog/2017/06/19/OpenStack-Cinder-configure-repl… i created a Volume type - REPL, with replication enabled <is> True and colume backend name parameter. But when i am trying to create a volume using the created volume type the volume is getting created in ceph but in cinder the status is showing error. and when checked log getting the following error: 2021-06-24 17:59:39.556 28472 ERROR cinder.volume.drivers.rbd [req-6e6b901e-f2dd-43a4-a089-6c734b279e17 d576181b6a444541b8ec7f37d750a4c1 a9ac2eba50d84d64ac44b179bbcc9183 - default default] Error creating rbd image volume-361f35c4-a589-4653-b404-fb93d2f598cf.: cinder.exception.ReplicationError: Volume 361f35c4-a589-4653-b404-fb93d2f598cf replication error: Failed to enable image replication I tried to create a volume using volume type- default and then later changed the volume type using command 'cinder retype' to the created volume type and it changed without any issue. I am using openstack victoria . With regards, Swogat Pradhan

4 5

[all][tc] What's happening in Technical Committee: summary 25th June, 21: Reading: 5 min
by Ghanshyam Mann 25 Jun '21

25 Jun '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Deprecated panko and puppet-panko project[1] 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-06-24-15.00.log.html * We will have next week's meeting on July 1st, Thursday 15:00 UTC[2]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[3] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Five open review for ongoing activities[4]. Migration from Freenode to OFTC ----------------------------------------- * Not much progress on project side wiki/doc page which is only thing left for this migration. * All the required work for this migration is tracked in this etherpad[5] 'Y' release naming process ------------------------------- * Y release naming election is closed now. As a last step, the foundation is doing trademark checks on elected ranking. Deprecate OpenStack-Ansible nspawn repositories ------------------------------------------------------------ * OpenStack-Ansible nspawn repositories is in process of retirement[6] Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[7], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Retiring governance's in-active repos ------------------------------------------- * The Technical Committee retiring the governance's in-active repos which are not required in current structure[8]. Adding Ceph Dashboard charm to OpenStack charms --------------------------------------------------------------- * Proposal to add Ceph Dashboard charm to OpenStack charms[9] Other Changes ------------------ * Charter change to handle the vacant seat situation[10] * Add DPL model also in 'Appointing leaders' section[11] 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[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [13] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [14] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/796408 [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-xena-tracker [4] https://review.opendev.org/q/project:openstack/governance+status:open [5] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [7] https://review.opendev.org/c/openstack/governance/+/797731 [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [8] https://etherpad.opendev.org/p/governance-repos-cleanup [9] https://review.opendev.org/c/openstack/governance/+/797913 [10] https://review.opendev.org/c/openstack/governance/+/797912 [11] https://review.opendev.org/c/openstack/governance/+/797985 [12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [14] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[tc][all][goal] Migrate RBAC Policy Format from JSON to YAML: COMPLETED
by Ghanshyam Mann 25 Jun '21

25 Jun '21

Hello Everyone, I am happy to update that we have completed the community wide goal for "Migrate RBAC Policy Format from JSON to YAML". - https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-f… Thanks to all the projects/contributors involved in this work. Completion Report: =============== * Projects completed: 33 * Projects do not need any changes: 16 * project left: 0 * This is the complete work we did for this goal: ** Gerrit Topic: https://review.opendev.org/q/topic:%22policy-json-to-yaml%22+(status:open%2… ** Tracking Etherpad: https://etherpad.opendev.org/p/migrate-policy-format-from-json-to-yaml -gmann

1 0

[nova][os-vif][stable] Adding os-vif-core to os-vif stable branches
by Stephen Finucane 25 Jun '21

25 Jun '21

Happy Friday, Per $subject, I'd like to propose that we add os-vif-core to the list of teams with +2 rights on os-vif stable branches. Currently this list is restricted to "Project Bootstrappers", nova-stable-maint and stable-maint-core. os-vif doesn't see many backports, but it is a rather specialist library that requires some domain-specific knowledge to grok and the existing stable reviewers typically insist on reviews from core reviewers before approving changes. By making this change, we can avoid this little dance. We have discussed this already on #openstack-nova, but if there are any concerns, please raise them now. If not, I'll seek to have the relevant changes merged to openstack/project-config by the end of next week. I'll post these changes shortly. Cheers, Stephen [1] https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.20…

3 3

[cinder] upcoming driver deadlines
by Brian Rosmaita 25 Jun '21

25 Jun '21

This is a reminder that the cinder New Driver Merge Deadline is Thursday 15 July 2021 [0]. Please make sure *right now* that you've filed a Launchpad blueprint for your driver and that your blueprint shows up in this list: https://blueprints.launchpad.net/cinder/xena (if it doesn't, contact me off list) If you're adding a new feature to a driver, you should also file a Lanuchpad blueprint (it helps us prioritize reviews). See the Xena release schedule for more info about the Cinder Driver Features Declaration [1]. New features for current drivers follow the regular Feature Freeze policy (that is, must be merged by Milestone 3). cheers, brian [0] https://releases.openstack.org/xena/schedule.html#x-cinder-driver-deadline [1] https://releases.openstack.org/xena/schedule.html#x-cinder-driver-features-…

1 0

[dev][nova] PCI IRQ Affinity for VMS with dedicated CPUs
by Soares Sarto, Ricardo 24 Jun '21

24 Jun '21

Hello Everyone, Does NOVA provide any intelligent affining of IRQs of PCI Devices to CPUs pinned to VMs? i.e. for VMs that have pci-passthrough interfaces to PCI devices and are using ‘dedicated’ CPU policy, does NOVA automatically affine the IRQs for those PCI devices the CPUs that are allocated to the VM? Furthermore, is there any flavor extraspec that can further scope the IRQ affinity of the PCI Devices to a subset of the VM’s dedicated cpus? If not, is this a new capability that the NOVA team would be open to? -rsoaress

2 1

[neutron] can floating IP port forwarding work when agent_mode is dvr or dvr_snat but on compute node?
by Yi Yang (杨燚)-云服务集团 24 Jun '21

24 Jun '21

Hi, folks I’m working on https://bugs.launchpad.net/neutron/+bug/1931953, per my check for neutron-specs/specs/rocky/port-forwarding.rst, it seems port forwarding function only can be done on network node, so I don’t think we need to do it on compute node, can anybody help confirm this? Per my understanding, if a FIP is set port forwarding to two VMS across two compute node, physical switch has no way to know which compute node it should send to if destination IP is this FIP, right? But on centralized mode, this isn’t an issue.

2 2

[ironic] Ansible deploy_interface error output
by Ivan Iotchenko 24 Jun '21

24 Jun '21

Hello We are using Ironic (Train) and Ansible deploy interface. Everything works just awesome and we were able to include all the things we need into deployment/undeployment process (with respect to flexibility provided by Ansible). However, there is an issue. If you have failures during the process - you will be presented with full Ansible output which can be large enough (and thus cut). Almost every failure requires you to review log files (Ironic/Ansible). This is fine if deployment is being done by Ironic admin or person who have required experience. For other users it can be a blocker. Usually you just cannot determine root cause from the error message in last_failure field, which you can get both from console or UI. Error output was pretty straightforward with direct deploy interface. Is there a way to made Ansible error output better? E.g. to make it short and descriptive (“DNS registration failed bla-bla-bla”) Thanks, Ivan

1 0