July 2022 - openstack-discuss - lists.openstack.org

[horizon] Cancelling Today's Weekly meeting
by vishal manchanda 13 Jul '22

13 Jul '22

Hello Team, As discussed in the last weakly meeting, I am on vaccination this week. So there will be no horizon weekly meeting today. If anything urgent, please reach out to horizon core team. Thanks & regards, Vishal Manchanda

1 0

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 12 Jul '22

12 Jul '22

Hey team, Since there's nothing on the agenda, tomorrow's meeting is cancelled. We will plan on meeting again same time next week.

1 0

[CLOUDKITTY] Missed CloudKitty meeting today
by Rafael Weingärtner 12 Jul '22

12 Jul '22

Hello guys, I would like to apologize for missing the CloudKitty meeting today. I was concentrating on some work, and my alarm for the meeting did not ring. If you need something, just let me know. Again, sorry for the inconvenience; see you guys at our next meeting. -- Rafael Weingärtner

1 0

[Openstack-Ansible] br-vlan configuration and intended usage?
by Dave Hall 12 Jul '22

12 Jul '22

Hello. I'm preparing to do my first deployment (of Yoga) on real hardware. The documentation regarding br-vlan was hard for me to understand. Could I get a clarification on what to do with this? Note: my intended use case is as an academic/instructional environment. I'm thinking along the lines of treating each student as a separate tenant that would be preconfigured with templated set of VMs appropriate to the course content. Any other thoughts regarding this scenario would also be greatly appreciated. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

4 6

[all][dev] Where are cross-repository blueprints and specs located?
by Manuel Bentele 11 Jul '22

11 Jul '22

Hi all, I have two general developer questions: * Where are the blueprints and specs located that address changes across the code base? * How to deal with changes that have dependencies on multiple repositories (where a specific merge and release order needs to be satisfied)? For example: An enumeration member has to be added and merged in repository A before it can be used in repository B and C. If this order is not satisfied, a DevStack setup may break. Regards, Manuel

3 3

[neutron] Bug Deputy Report July 04 - 11
by Lucas Alvares Gomes 11 Jul '22

11 Jul '22

Hi, This is the Neutron bug report from July 4th to 11th. Quieter week than usual. High: * https://bugs.launchpad.net/neutron/+bug/1980967 - "get_hypervisor_hostname helper function is failing silently" Assigned to: Miro Tomaska * https://bugs.launchpad.net/neutron/+bug/1981077 - "Remove import of 'imp' module" Unassigned * https://bugs.launchpad.net/neutron/+bug/1981113 - "OVN metadata agent can be slow with large amount of subnets" Assigned to: Miro Tomaska Medium: * https://bugs.launchpad.net/neutron/+bug/1980671 - "Neutron-dynamic-routing: missing transaction wrapper" Assigned to: Dr. Jens Harbott Cheers, Lucas

1 0

Re: [service-announce] Updating Zuul's Default Ansible Version to Ansible v5
by Ian Wienand 11 Jul '22

11 Jul '22

On Wed, Jun 15, 2022 at 12:11:00PM -0700, Clark Boylan wrote: > The OpenDev team will be updating the default Ansible version in our > Zuul tenants from Ansible 2.9 to Ansible 5 on June 30, 2022. Zuul > itself will eventually update its default, but making the change in > our tenant configs allows us to control exactly when this happens. Note this has been merged with https://review.opendev.org/c/openstack/project-config/+/849120 Just for visibility I've cc'd this to openstack-discuss; but please subscribe to service-announce [1] if you're interested in such OpenDev infra updates. Thanks, -i [1] https://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce

1 0

Podman issue when building custom horizon container
by Swogat Pradhan 11 Jul '22

11 Jul '22

Hi, I am following the https://access.redhat.com/documentation/zh-cn/red_hat_openstack_platform/16… link to custom build the container image. but when trying to push i am getting the following error: Error: writing blob: initiating layer upload to /v2/tripleomaster/openstack-horizon/blobs/uploads/ in 172.25.201.68:8787: StatusCode: 404, <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">... [root@hkg2director httpd]# tail -f image_serve_error.log [Fri Jul 08 12:58:09.788817 2022] [core:error] [pid 5033:tid 140483665843968] [client 172.25.163.196:33866] AH00126: Invalid URI in request GET /././.. HTTP/1.1 [Sun Jul 10 21:42:59.744102 2022] [negotiation:error] [pid 33922:tid 140484739585792] (2)No such file or directory: [client 172.25.201.106:58678] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 21:43:01.280405 2022] [negotiation:error] [pid 5035:tid 140483917494016] (2)No such file or directory: [client 172.25.201.97:45222] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 21:43:02.024126 2022] [negotiation:error] [pid 33922:tid 140484043319040] (2)No such file or directory: [client 172.25.201.103:34508] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 21:43:16.852186 2022] [negotiation:error] [pid 33922:tid 140484076889856] (2)No such file or directory: [client 172.25.201.105:53542] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 22:10:05.220181 2022] [negotiation:error] [pid 33922:tid 140485133846272] (2)No such file or directory: [client 172.25.201.106:56804] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 22:10:06.679326 2022] [negotiation:error] [pid 5035:tid 140485108668160] (2)No such file or directory: [client 172.25.201.103:54208] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 22:10:07.026650 2022] [negotiation:error] [pid 5035:tid 140483917494016] (2)No such file or directory: [client 172.25.201.97:35056] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Sun Jul 10 22:10:22.600075 2022] [negotiation:error] [pid 33922:tid 140484060104448] (2)No such file or directory: [client 172.25.201.105:45446] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-8.type-map [Mon Jul 11 01:23:45.354025 2022] [negotiation:error] [pid 129344:tid 139984250070784] (2)No such file or directory: [client 172.25.201.68:59514] AH00683: cannot access type map file: /var/lib/image-serve/v2/tripleomaster/openstack-horizon/manifests/0-9.type-map [stack@hkg2director horizon-themes]$ sudo podman push 172.25.201.68:8787/tripleomaster/openstack-horizon:0-9 WARN[0000] Failed to decode the keys ["network.network_backend"] from "/usr/share/containers/containers.conf". WARN[0000] Failed to decode the keys ["network.network_backend"] from "/usr/share/containers/containers.conf". WARN[0000] Failed to decode the keys ["network.network_backend"] from "/usr/share/containers/containers.conf". Getting image source signatures Copying blob 80c0be683ac9 skipped: already exists Copying blob bab1c7b6a899 [--------------------------------------] 8.0b / 59.5KiB Copying blob f9f09cbae066 [--------------------------------------] 8.0b / 59.5KiB Copying blob b7b591e3443f [--------------------------------------] 8.0b / 20.0KiB Copying blob bb83a400dc7e [--------------------------------------] 8.0b / 7.0KiB Copying blob 1ca9ec783ad6 [--------------------------------------] 8.0b / 7.0KiB Copying blob 3a6b7f2864e6 [--------------------------------------] 8.0b / 7.0KiB Copying blob ffd77c9907b7 [--------------------------------------] 8.0b / 9.0KiB Copying blob 6ae06b1bf643 [--------------------------------------] 8.0b / 7.5KiB Copying blob bc3dd4002908 [--------------------------------------] 8.0b / 7.5KiB Copying blob 8b974d9968c1 [--------------------------------------] 8.0b / 14.0KiB Copying blob 30f87a7de8b5 [--------------------------------------] 8.0b / 6.0KiB Copying blob aa02c13deb86 [--------------------------------------] 0.0b / 4.0KiB Copying blob 89b853af1aa2 [--------------------------------------] 8.0b / 14.0KiB Copying blob 3ee1ead6db5f [--------------------------------------] 8.0b / 59.5KiB Copying blob fd1baa2a1cd0 [--------------------------------------] 8.0b / 59.5KiB Copying blob 33afb269824d [--------------------------------------] 8.0b / 7.0KiB Copying blob f1117feaa844 [--------------------------------------] 8.0b / 7.0KiB Copying blob b36e5fbb3eab [--------------------------------------] 8.0b / 7.0KiB Copying blob 5d6773201dfb [--------------------------------------] 8.0b / 7.5KiB Copying blob f9ae49c1e307 [--------------------------------------] 8.0b / 7.5KiB Copying blob 64e624a7f305 [--------------------------------------] 8.0b / 6.0KiB Copying blob 2fa93f4f2a45 [--------------------------------------] 8.0b / 128.6MiB Copying blob ccf04fbd6e19 [--------------------------------------] 8.0b / 201.0MiB Copying blob 8a36fc7d2feb [--------------------------------------] 8.0b / 281.3MiB Error: writing blob: initiating layer upload to /v2/tripleomaster/openstack-horizon/blobs/uploads/ in 172.25.201.68:8787: StatusCode: 404, <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">... Can someone please guide me to fix this issue? With regards, Swogat pradhan

1 0

[OpenStack-Ansible] Log Aggregation in Yoga
by Dave Hall 11 Jul '22

11 Jul '22

Hello, I've been told that Openstack now uses journald rather than rsyslog, but the Yoga docs still show a log aggregation host. Although I still prefer rsyslog, what I really prefer is to have logs for all hosts in the cluster collected in one place. How do I configure this for a fresh installation? Is it reasonable to assign this duty to an infrastructure host? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

3 5

[event] OpenInfradays Mexico 2022 (Virtual)
by Alvaro Soto 10 Jul '22

10 Jul '22

You're all invited to participate in the CFP for OID-MX22 https://openinfradays.mx Let me know if you have any questions. --- Alvaro Soto Escobar Note: My work hours may not be your work hours. Please do not feel the need to respond during a time that is not convenient for you. ---------------------------------------------------------- Great people talk about ideas, ordinary people talk about things, small people talk... about other people.

1 2

[heat][horizon] heat-dashboard-core maintenance
by Akihiro Motoki 09 Jul '22

09 Jul '22

Hi, I added heat-core gerrit group to heat-dashboard-core [1]. Heat team and horizon team agreed to maintain heat-dashboard together a while ago and horizon-core was added to heat-dashboard-core. At that time heat-dashboard had active contributors so head-dashboard-core did not include heat-core team. The active contributors in heat-dashboard-core have gone and Rico is the only person from the heat team, so it is time to add heat-core to heat-dashboard-core. In addition, I would like to drop the following folks from heat-dashboard-core. They were active in heat-dashboard but they had no activities for over three years. If there is no objection, I will drop them next week. - Kazunori Shinohara - Keiichi Hikita - Xinni Ge [1] https://review.opendev.org/admin/groups/8803fcad46b4bce76ed436861474878f36e… Thanks, Akihiro Motoki (amotoki)

1 1

[all][tc] What's happening in Technical Committee: summary 08 July 2022: Reading: 5 min
by Ghanshyam Mann 09 Jul '22

09 Jul '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 07 July. Most of the meeting discussions are summarized in this email. As it was video meeting, full recording is available @https://www.youtube.com/watch?v=zeJG6Mujalo&t=29s and brief logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-07-07-15.00.log.html * Next TC weekly meeting will be on 14 July Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by 13 July. 2. What we completed this week: ========================= * Nothing specific in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[3]. CentOS-stream-9 testing stability and collaboration with centos-stream maintainers --------------------------------------------------------------------------------------------------- We discussed this topic in the TC meeting and I summarized the discussion in separate ML[4]. Create the Environmental Sustainability SIG --------------------------------------------------- Not much update on this except what we discussed last time, feel free to add your feedback in review[5]. Consistent and Secure Default RBAC ------------------------------------------- We have a good amount of discussion and review in the goal document updates[6] and I have updated the patch by resolving the review comments. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[7]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[8]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[9][10]. Project updates ------------------- * None 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [12] 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/+/847413 [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029468.ht… [5] https://review.opendev.org/c/openstack/governance-sigs/+/845336 [6] https://review.opendev.org/c/openstack/governance/+/847418 [7] https://review.opendev.org/c/openstack/governance/+/836888 [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [9] https://etherpad.opendev.org/p/zuul-config-error-openstack [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][qa][centos stream] CentOS-stream-9 testing stability and collaboration with CentOS-stream maintainers
by Ghanshyam Mann 09 Jul '22

09 Jul '22

Hello Everyone, As you know, CentOS-stream-9 is in Zed cycle testing runtime and we are facing some stability issues to make its testing voting (detach volume, qemu issues are some known ones). Currently, it is a non-voting job which is not good for the long term as non-voting job failures are mostly ignored. We called CentOS stream folks to discuss how to make it stable testing or a better way to improve the communication between both communities as well as coordinated debugging. Alan, Brian, and Aleksandra from the CentOS stream team joined the TC call on 7 July. With the CentOS stream model of having the latest packages version like libvirt etc it is good to test and capture the potential issues in advance but at the same time, there will more failure than other distros like ubuntu etc. Knowing the failure in the early stage is good but we have a few challenges to triage such failure. OpenStack or CentOS team alone might not be able to know the root cause of the issue at first glance, whether it is in OpenStack component or in CentOS stream. CentOS team has less experience in debugging devstack or tempest tests. And if such failures are more frequent (current case) then having it as a voting testing on every patch is another challenge for OpenStack smooth development cycle. We could not find any best solution to solve all these challenges but we all agree that we need some coordinated debugging. We need some of the initial level of failure debugging in OpenStack and pass the information to CentOS team for further debugging. That is one possible step forward and we will see how it goes. Basically doing the following : * If OpenStack members see failure in CentOS stream then do some initial level of debugging to know which OpenStack component is failing and collect some log information. * Report the bug with all those information at https://bugzilla.redhat.com/ * Contact CenntOS Stream team (you can address/ping Alan, Brian or Aleksandra ) via ** ML: https://lists.centos.org/mailman/listinfo/centos-devel ** IRC channel on Libera chat #centos-devel and #centos-stream Alan, Brian, Aleksandra, or any TC members feel free to add the things if I missed something. -gmann

1 0

[all][tc][gerrit] Ownership of *-stable-maint groups
by Stephen Finucane 09 Jul '22

09 Jul '22

tl;dr: Who should be able project-specific stable-maint groups on Gerrit: members of the projects-specific stable-maint group itself or members of stable- maint-core? A recent discussion on #openstack-sdks highlighted some discrepancies in the ownership of various project-specific "stable-maint" groups on Gerrit. As a reminder, any project that specifies "stable:follows-policy" is required to follow the stable branch policy (suprise!). This is documented rather well at [1]. We expect people who have the ability to merge patches to stable branches to understand and apply this policy. Initially the only people that could do this were peopled added to a central Gerrit group called "stable-maint-core" group, however, in recent years this responsibility has been devolved to the projects themselves. Each project with a stable branch now has a project- specific stable maintenance Gerrit group called PROJECTNAME-stable-maint (e.g. nova-stable-maint [2]. The issue here is who should *own* these groups. The owner of a Gerrit group is the only one that's able to modify it. In general, the owner of a Gerrit group is the group itself so for example the owner of python-openstackclient-core is python-openstackclient-core [3]. This means that if you're a member of the group then you can add or remove members, rename the group, set a description etc. However, _most_ PROJECTNAmE-stable-maint groups are owned by the old 'stable- maint-core' group, meaning only members of this global group can modify the project-specific groups. I say _most_ because this isn't applied across the board. The following projects are owned by 'stable-maint-core': * barbican-stable-maint * ceilometer-stable-maint * cinder-stable-maint * designate-stable-maint * glance-stable-maint * heat-stable-maint * horizon-stable-maint * ironic-stable-maint * keystone-stable-maint * manila-stable-maint * neutron-stable-maint * nova-stable-maint * oslo-stable-maint * python-openstackclient-stable-maint * sahara-stable-maint * swift-stable-maint * trove-stable-maint * zaqar-stable-maint However, the following stable groups "own themselves": * ansible-collections-openstack-stable-maint * aodh-stable-maint * congress-stable-maint * freezer-stable-maint * karbor-stable-maint * mistral-stable-maint * neutron-dynamic-routing-stable-maint * neutron-lib-stable-maint * neutron-vpnaas-stable-maint * octavia-stable-maint * openstacksdk-stable-maint * oslo-vmware-stable-maint * ovn-octavia-provider-stable-maint * panko-stable-maint * placement-stable-maint * sahara-dashboard-stable-maint * senlin-dashboard-stable-maint * senlin-stable-maint * telemetry-stable-maint This brings me to my question (finally!): do we want to resolve this discrepancy, and if so, how? Personally, I would lean towards delegating this entirely to the projects but I don't know if this requires TC involvement to do. If we want to insist on the stable-maint group owning all PROJECT-stable-maint branches then we have a lot of cleanup to do! Cheers, Stephen PS: This might be a good moment to do a cleanup of members of various stable branches that have since moved on... [1] https://docs.openstack.org/project-team-guide/stable-branches.html [2] https://review.opendev.org/admin/groups/21ce6c287ea33809980b2dec53915b07830… [3] https://review.opendev.org/admin/groups/aa0f197fcfbd4fcebeff921567ed3b48cd3…

4 6

[TripleO] PTL outage
by James Slagle 09 Jul '22

09 Jul '22

Hello TripleO, I'll be out on PTO for the next 2 weeks. Not that I'm typically needed :), but If anything urgent requires attention, please reach out to the kind folks directly in #tripleo. -- -- James Slagle --

1 0

[release] Release countdown for week R-12, Jul 11 - 15
by Előd Illés 09 Jul '22

09 Jul '22

Development Focus ----------------- The Zed-2 milestone is next week, on July 14th, 2022! Zed-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/zed/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Zed' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in Zed have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Zed, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Zed-2 Milestone: July 14th, 2022 Next PTG: October 17-20, 2022 (Columbus, Ohio) Előd Illés irc: elodilles

1 0

[cinder] Spec Freeze Exception Request
by Gorka Eguileor 09 Jul '22

09 Jul '22

Hi, I would like to request a spec freeze exception for the new Cinder Quota System spec [1]. Analysis of the required spec changes needed to implement the second quota driver, as agreed in the PTG/mid-cycle, were non trivial. In the latest spec update I just pushed there are considerable changes: - General improvements to existing sections to increase readability. - Description of the additional driver and reasons why we decided to implement it. - Spell out through the entire spec the similarities and differences of both drivers. - Change in tracking of the reservations to accommodate the new driver. - Description on how switching from one driver to the other would work. - Updated the driver interface to accommodate the particularities of the new driver. - Updated the performance section with a very brief summary of the performance tests done with some code prototipe. - Updating the phases of the effort as well as the work items. Cheers, Gorka. [1]: https://review.opendev.org/c/openstack/cinder-specs/+/819693

2 2

[neutron] CI meeting on Tuesday 12.07.2022 cancelled
by Slawek Kaplonski 08 Jul '22

08 Jul '22

Hi, I will be on PTO next week. As there is nothing really critical to our CI currently, lets cancel next week's meeting. See You on CI meeting on Tuesday 19th of July. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[baremetal-sig][ironic] Tue July 12, 2022, 2pm UTC: "Bare metal Kubernetes at G-Research"
by Arne Wiebalck 08 Jul '22

08 Jul '22

Dear all, The Bare Metal SIG will meet next week on Tue July 12, 2022, 2pm UTC featuring a topic of the day presentation by Scott Solkhon & Jamie Poole: "Bare metal Kubernetes at G-Research" Everyone is welcome, all details on how to join can be found on the SIG's etherpad: https://etherpad.opendev.org/p/bare-metal-sig Hope to see you there! Arne -- Arne Wiebalck CERN IT

1 0

[nova][neutron] do not recheck failing nova-next or nova-ovs-hybird-plug failures.
by Sean Mooney 08 Jul '22

08 Jul '22

hi o/ it looks like neutron recently moved linuxbridge to be experimental Jul 06 16:21:46.640517 ubuntu-focal-rax-ord-0030301377 neutron-server[90491]: ERROR neutron.common.experimental [-] Feature 'linuxbridge' is experimental and has to be explicitly enabled in 'cfg.CONF.experimental' we do not actully deploy it in nova-next or nova-ovs-hybrid-plug but it is enabeld in our job config as one of the configured mech drivers even if we dont install the agent. i have not looked up what change in neutron change this yet but im going to propose a patch to nova to disable it and i likely need to fix os-vif too so if you see a post fialure in either the nova-next of novs hybrid plug jobs (and or look into it and see " die 2385 'Neutron did not start'" in the Run devstack task summery that is why this is failing. ill update this thread once we have fixed the issue.

2 3

Cluster management tool for Openstack
by KK CHN 08 Jul '22

08 Jul '22

List, 1. Is there any specific tool or project component available to maintain multiple OpenStack Clusters 2. Is there any concept of Supervisory cluster ? Regards, Krish

1 0

Nova-conductor is having trouble with AMQP authentication
by Airamek 08 Jul '22

08 Jul '22

Hello everyone! I've installed OpenStack Ussuri on my home servers (one controller and one compute node, both running OpenSuse Leap 15.3) based on the instructions in the docs(https://docs.openstack.org/install-guide/openstack-services.html#minim… Everything works until I launch an instance in Horizon. The instance gets stuck on "Scheduling". Looking trough the logs I've came across nova-conductor.log(on the controller), which contained the following error log(full log in the attachments): 2022-07-08 00:48:08.846 25886 ERROR oslo_messaging.rpc.server [req-eb225ffd-9b12-4e80-987b-34f0317082c6 741cb0b6280cb6fbedf1d8c6df4fc854b3e177e331441e019b961839089154d6 9b41f3e228984401a7642f94cd47dc73 - 4596c7f3b97740b3adfa8f82b6240654 4596c7f3b97740b3adfa8f82b6240654] Exception during message handling: amqp.exceptions.AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile. I'm 100% sure my RabbitMQ username and password are set correctly in nova.conf. I've included my nova.conf too, with the passwords removed. I would be really thankful, if someone could point me in the right direction! P.S: Please excuse me for any grammatical or spelling mistakes, English is not my first language.

1 0

[neutron] Drivers meeting agenda - 08.07.2022.
by Lajos Katona 08 Jul '22

08 Jul '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE] Adding the "rekey" parameter to the api for strongswan like "dpd_action" (#link https://bugs.launchpad.net/neutron/+bug/1979044) * [RFE] Firewall Group Ordering on Port Association (#link https://bugs.launchpad.net/neutron/+bug/1979816) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[tc] Reminder: August 2022 OpenInfra Board Sync
by Jeremy Stanley 08 Jul '22

08 Jul '22

If you're interested in participating in an informal discussion between the OpenStack TC, OpenInfra board members, and other interested community collaborators, don't forget to mark your preferred dates and times by Friday, 2022-07-15, so that I can let the board members know what our collective availability looks like: https://framadate.org/atdFRM8YeUtauSgC If you don't know what this is about, see my earlier post for details (I intentionally avoided replying to it in order to increase visibility for the reminder): https://lists.openstack.org/pipermail/openstack-discuss/2022-June/029352.ht… -- Jeremy Stanley

1 0

[manila] Stepping down from manila core
by Rodrigo Barbieri 08 Jul '22

08 Jul '22

Hello fellow zorillas, It has been a long time since I started to hope every day I'd able to dedicate more time to manila core activities and so far that hasn't happened and I don't see it happening in the near foreseeable future. I had been following the meetings notes weekly until ~2 months ago but I recently ended up dropping those as well. Therefore I am stepping down from the manila core role. I would like to thank everyone that I worked closely with from 2014 to 2019 on this project. I hold this project and all of you dear to my heart and I am extremely glad and grateful to have worked with you and met you on summits/PTGs, as the life memories around Manila are among the best I have from that period. If someday circumstances change, the manila project and its community will be ones I will be very happy to go back to working closely with again. Kind regards, -- Rodrigo Barbieri MSc Computer Scientist

3 2