November 2022 - openstack-discuss

[all][python3.11][debian][horizon] Debian has python 3.11 as available version
by Thomas Goirand 14 Nov '22

14 Nov '22

Hi, Debian unstable now has Python 3.11 as available interpreter. Some packages got rebuilt, and we're starting to see failures. Here's the first one that I'm trying to fix: pyscss. https://github.com/Kronuz/pyScss/issues/428 pykafka also fails to build. There's likely a lot more to come. I'd appreciate help... :) Cheers, Thomas Goirand (zigo)

1 0

assign network subnet to computes
by Parsa Aminian 14 Nov '22

14 Nov '22

hello is there any way to assign a specific subnet in openstack to a specific compute ? For example subnets with ip 192.168.11.0/24 only can assign to instances on compute6 .

2 1

Zun connector for persistent shared files system Manila
by Vaibhav 13 Nov '22

13 Nov '22

Hi, I am using zun for running containers and managing them. I deployed cinder also persistent storage. and it is working fine. I want to mount my Manila shares to be mounted on containers managed by Zun. I can see a Fuxi project and driver for this but it is discontinued now. With Cinder only one container can use the storage volume at a time. If I want to have a shared file system to be mounted on multiple containers simultaneously, it is not possible with cinder. Is there any alternative to Fuxi. is there any other mechanism to use docker Volume support for NFS as shown in the link below? https://docs.docker.com/storage/volumes/ Please advise and give a suggestion. Regards, Vaibhav

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Nov 11: Reading: 5 min
by Ghanshyam Mann 11 Nov '22

11 Nov '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * * We had this week's meeting on Nov 09. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-09-16.00.log.html * Next TC weekly meeting will be on Nov 16 Wed at 16:00 UTC, please make note of the new day/time for TC meetings. Feel free to add the topic to the agenda[1] by Nov 15. 2. What we completed this week: ========================= * None for this week. 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[2]. Open Reviews ----------------- * Ten open reviews for ongoing activities[3]. 2023.1 cycle testing runtime changes (additional testing) ------------------------------------------------------------------- We discussed it in PTG and mainly for smooth upgrade what best we can do/test in testing runtime when we bump the distro version. You might have read my PTG summary email about the agreement on this. Accordingly, I have updated the patch[4] which includes the change in the 2023.1 cycle testing runtime: 1. Keep supporting Ubuntu 20.04: at least one integrated job running at the project gate. 2. Minimum python version will be py3.8 (default in Ubuntu 20.04) This is early heads-up on this and you can review it if any feedback otherwise once it is merged, I will send these updates in a separate email also. TC to stop using storyboard? ---------------------------------- TC has a governance project in the storyboard and it was confusing for many of us. It was used to track the tasks mainly the community-wide goals. But we have not used it for a couple of years and etherpad for TC tracker works very well since Xena cycle[5]. Most TC members are ok to remove the TC storyboard project (after cleaning all story/tasks which I already started) but as we did not have all the TC members in this week's meeting, we will do a formal vote on this in the next TC meeting. Renovate translation SIG i18 ---------------------------------- * rosmaita is coordinating with Weblate and updated that hosting OpenStack translation on Weblate is not free (they can give a 50% discount though). This is a difficult situation now and rosmaita will continue his research and user survey if we can get help from users using the translation. TC Weekly meeting new day and time -------------------------------------------- I am mentioning this again in case anyone missed it. The TC weekly meeting new time is every Wed at 16:00 UTC. TC Video meeting discussion ---------------------------------- JayF resolution patch to move TC all weekly meetings format to IRC is under review[6]. TC chair nomination & election process ----------------------------------------------- I have updated the patch to have the dir structure in the chair nomination. The current two options are up for the review[7][8]. Project updates ------------------- * Add zookeeper role under OpenStack-Ansible governance[9] * Add Skyline repository for OpenStack-Ansible[10] * Add the cinder-infinidat charm to Openstack charms[11] * Add the infinidat-tools subordinate charm to OpenStack charms[12] * Add the manila-infinidat charm to Openstack charms[13] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-zed-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/860599 [5] https://wiki.openstack.org/wiki/Technical_Committee_Tracker [6] https://review.opendev.org/c/openstack/governance/+/863685 [7] https://review.opendev.org/c/openstack/governance/+/862772 [8] https://review.opendev.org/c/openstack/governance/+/862774 [9] https://review.opendev.org/c/openstack/governance/+/863161 [10] https://review.opendev.org/c/openstack/governance/+/863166 [11] https://review.opendev.org/c/openstack/governance/+/863958 [12] https://review.opendev.org/c/openstack/governance/+/864067 [13] https://review.opendev.org/c/openstack/governance/+/864068 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-18, Nov 14 - 18
by Elõd Illés 11 Nov '22

11 Nov '22

Development Focus ----------------- The Antelope-1 milestone is next week, on November 17th, 2022! Project team plans for the 2023.1 Antelope cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the Zed release. PTL's or 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, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Antelope-1 milestone: November 17th, 2022 Final 2023.1 Antelope release: March 22nd, 2023 Előd Illés irc: elodilles

1 0

[neutron][release] Proposing to EOL Queens, Rocky and Stein (all Neutron related projects)
by Rodolfo Alonso Hernandez 11 Nov '22

11 Nov '22

Hello: In the last PTG, the Neutron team has decided [1] to move the stable branches Queens, Rocky and Stein to EOL (end-of-life) status. According to the steps to achieve this [2], we need first to announce it. That will affect all Neutron related projects. The patch to mark these branches as EOL will be pushed in one week. If you have any inconvenience, please let me know in this mail chain or in IRC (ralonsoh, #openstack-neutron channel). You can also contact any Neutron core reviewer in the IRC channel. Regards. [1]https://etherpad.opendev.org/p/neutron-antelope-ptg#L131 [2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l…

1 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 11 Nov '22

11 Nov '22

Hello Neutrinos: Due to the lack of agenda, today's meeting is cancelled. Have a nice weekend!

1 0

[kolla-ansible]Network Problem after server reboot
by Franck VEDEL 10 Nov '22

10 Nov '22

Hello, after a restart of my cluster (and some problems...), I have one last problem with the VMs already present (before the restart). They all work fine….They all work, console access OK, network topology ok… But they can no longer communicate on the network, they do not obtain IP addresses by dhcp. Yet everything seems to be working. If I detach the interface, I create a new interface, it doesn't work. I cannot reach the routers. I cannot communicate with an instance on the same network. On the other hand, if I create a new instance, no problem, it works and can join the other instances and its router. Is there a way to fix this? The problem is where? in the database? Thank you in advance for your help. Franck VEDEL

2 2

Fwd: Need assistance
by Gk Gk 10 Nov '22

10 Nov '22

---------- Forwarded message --------- From: Gk Gk <ygk.kmr(a)gmail.com> Date: Thu, Nov 10, 2022 at 7:01 PM Subject: Re: Need assistance To: <neil(a)shrug.pw> The file which is being picked by uwsgi is '../../nova-20.2.1/lib/python3.6/site-packages/nova/api/openstack/compute/wsgi.py' . But I dont see how this file is being called. Which program loads this file ? Can someone help me here ? Disregard the abive message. This is the file I believe is being called "/openstack/venvs//nova-20.2.1/lib/python3.6/site-packages/nova/api/openstack/wsgi.py" . So how is it being called or which program is calling it ? I want to know the first file which uwsgi loads after being launched. On Wed, Nov 9, 2022 at 5:28 PM Neil Hanlon <neil(a)shrug.pw> wrote: > > > On Wed, Nov 9, 2022, 05:51 Gk Gk <ygk.kmr(a)gmail.com> wrote: > >> Thanks Melanie for the reply. I am able to use pdb successfully for the >> trace. But I am observing a strange behaviour with the python source files. >> Whenever I make any changes to the source files >> , for example, insert a pdb statement in servers.py, it is taking a >> minute or more for the changes to take effect. For example, after the >> change, if I run the uwsgi command at the terminal manually with >> --honour-stdin option, then immediately if I fire the nova list command, >> it is not taking effect. Only after a minute or so of making the change, it >> is taking effect. Somewhat strange. >> >> My next question is, inside the nova-api container, I am trying to trace >> how nova-api service starts. The systemd file has this content: >> --- >> ExecStart = /openstack/venvs/uwsgi-20.2.1-python3/bin/uwsgi --autoload >> --ini /etc/uwsgi/nova-api-os-compute.ini >> ---- >> So I have checked the file /etc/uwsgi/nova-api-os-compute.ini , which has >> the below content: >> --- >> wsgi-file = /openstack/venvs/nova-20.2.1/bin/nova-api-wsgi >> -- >> >> Is the above file '/openstack/venvs/nova-20.2.1/bin/nova-api-wsgi' the >> one from which the nova-api service starts at all ? >> > > That is correct. The nova-api-wsgi and nova-metadata-wsgi entry points > read nova.conf and api-paste.ini to generate the required WSGI application. > > Those scripts are just python entry points so you should be able to follow > along there, barring some setuptools magic invoked. > >> >> >> Thanks >> Kumar >> >> On Wed, Nov 9, 2022 at 5:39 AM melanie witt <melwittt(a)gmail.com> wrote: >> >>> On Tue Nov 08 2022 03:03:18 GMT-0800 (Pacific Standard Time), Gk Gk >>> <ygk.kmr(a)gmail.com> wrote: >>> > Hi All, >>> > >>> > I have a OSA setup. I am trying to trace the control flow of nova-api >>> > using pdb in the file >>> > >>> "/openstack/venvs/nova-20.2.1/lib/python3.6/site-packages/nova/objects/instance.py". >>> > >>> > My goal is to trace the flow for "nova list --all" command. I am >>> > launching the nova-api service manually from the command line as >>> follows: >>> > >>> > #/openstack/venvs/uwsgi-20.2.1-python3/bin/uwsgi --ini >>> > /etc/uwsgi/nova-api-os-compute.ini --workers 1 >>> > >>> > I am executing "nova list --all" command in another terminal. I have >>> > inserted pdb in instance.py as follows: >>> > >>> > ---- >>> > @base.remotable_classmethod >>> > def get_all(cls, context, expected_attrs=None): >>> > import pdb; pdb.set_trace() >>> > """Returns all instances on all nodes.""" >>> > db_instances = db.instance_get_all( >>> > context, >>> columns_to_join=_expected_cols(expected_attrs)) >>> > return _make_instance_list(context, cls(), db_instances, >>> > expected_attrs) >>> > --- >>> > >>> > But when I fire the nova list --all command, I see no pdb prompt being >>> > shown in the nova-api window. Can anyone help me how to use the pdb to >>> > trace the flow of control for "nova list --all" command ? >>> >>> It looks like running nova-api that way is still running as a background >>> process: >>> >>> >>> https://stackoverflow.com/questions/34914704/bdbquit-raised-when-debugging-… >>> >>> I got that result ^ when I tried it locally. >>> >>> I was however able to get success with remote pdb: >>> >>> https://docs.openstack.org/devstack/latest/systemd.html#using-remote-pdb >>> >>> so maybe give that a try. Note that the code where you set the trace in >>> nova/objects/instance.py is not actually hit when doing a server list. >>> You may have instead meant: >>> >>> >>> https://github.com/openstack/nova/blob/c97507dfcd57cce9d76670d3b0d48538900c… >>> >>> Also note that as a community we're trying to get away from using the >>> legacy 'nova' command and recommend using the openstackclient instead: >>> >>> >>> https://docs.openstack.org/python-openstackclient/latest/cli/command-object… >>> >>> The 'nova' CLI is no longer being maintained and we're adding to the >>> novaclient python bindings only when necessary. >>> >>> HTH, >>> -melwitt >>> >>> >>> >>>

2 1

[Openstack][FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 10 Nov '22

10 Nov '22

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2023, to be hosted on February 4th 2023. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 10th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 10th December 2022 Acceptance notifications: 15th December 2022 Final schedule announcement: 20th December 2022 Devroom: First half of 4th February 2023 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Submission Guidelines Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. How to Apply In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://penta.fosdem.org/submission/FOSDEM23 [2] iaas-virt-devroom at lists.fosdem.org

1 0

[ansible-openstack-modules] 2023.1 Antelope PTG summary
by Rafael Castillo 10 Nov '22

10 Nov '22

We held our ansible-collections-openstack PTG a few weeks ago. Thanks to everyone who participated! Here's a belated summary of the discussions that took place. Etherpad: https://etherpad.opendev.org/p/oct2022-ptg-os-ansible-modules The plan for the Antelope cycle is to continue our current course of porting all remaining modules to support the new SDK. Our tentative release date for 2.0.0 is January 1st 2023. While porting modules will be the priority first and foremost, we discussed some proposals for enhancement during our session. These will remain on the backburner and will be addressed on a best effort basis. # Proposals for improvement ## Consistent module naming In order to make the modules more self-describing, avoid prefixes like federation_idp and keep names obvious. Change module names to be consistent with openstack-client. Change return values to match module names where possible. ## Documentation updates Highlight in docs that module results can differ depending on the cloud they use. Our module docs are currently based on devstack. Keep different documentation pages on galaxy between stable and master, as the two differ quite a bit. Update README and docs folder with more current information. ## Migrate current tests to use ansible-test The ansible-test integration test runner has some nice features. There's examples of the OTC modules using this we can take a look at. ## Write sdk logs to module results instead of writing to file Can be more convenient to have logs available right in ansible output. Counter-point is that these logs grow to be huge sometimes. ## Drop pbr based installation? We should focus on supporting ansible-galaxy as the preferred method of installing ansible collections. Again, thanks for participating in the collections process. Have a good weekend.

1 0

[nova][placement] Happy Specs review day next Tuesday (Nov 15) !
by Sylvain Bauza 09 Nov '22

09 Nov '22

Hey, as said above, like every 6-month cycle, we'll have a specs review day to make sure we can jab the open specs. You are a reviewer (even not a core) ? Make sure you can review the specs on Nov 15th. You are a contributor and you have an open spec ? Make sure you can look at Gerrit during this day because you could see new comments and you could then rebase your spec for providing a new revision :) -Sylvain

1 0

Neutron : Routed Provider Networks (no subnets declared in compute placement API: consequences?)
by Andrew West 09 Nov '22

09 Nov '22

Hi neutron experts Have a cloud built with multiple network segments (RPN) . (kolla-ansible, openstack ussuri), things are running OK (on the network level): networks have DHCP agents ok (*os network agent list --agent-type dhcp --network $networkID* ) all network segments are listed in Host Aggregates BUT if I run through all the existing segments , NONE have a (compute service) inventory declared for each segment IPv4 subnet i.e *os resource provider inventory list $segmentID * returns no output. (official doc on RPN says this should exist) What feature may not function if this inventory is missing ? I don't quite understand what role this IPv4 subnet compute service inventory plays here (during placement? port declaration ?) thanks Andrew

2 1

[largescale-sig] Next meeting: Nov 9, 15utc
by Thierry Carrez 09 Nov '22

09 Nov '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. Note that most countries are no longer in DST! You should doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20221109T15 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[oslo] Moving back oslo deliverables to the cycle with intermediary release model
by Herve Beraud 09 Nov '22

09 Nov '22

Hey Osloers, Months ago we moved a couple of oslo deliverables to the independent release model [1][2], however it led us to issues with backports [3]. Backports are not an option for those deliverables. During the previous release management team' PTG we discussed this topic and we decided [4] to move back the oslo deliverables to the cycle-with-intermediary model. You can follow the transition to the CWI model through this patch https://review.opendev.org/c/openstack/releases/+/864095 Do not hesitate to react directly to the patch. Thanks for your time. [1] https://lists.openstack.org/pipermail/openstack-discuss/2020-November/01852… [2] https://opendev.org/openstack/releases/commit/5ecb80c82ed3ab0144c8e5860ee62… [3] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0306… [4] https://etherpad.opendev.org/p/oct2022-ptg-rel-mgt -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

4 5

Need assistance
by Gk Gk 09 Nov '22

09 Nov '22

Hi All, I have a OSA setup. I am trying to trace the control flow of nova-api using pdb in the file "/openstack/venvs/nova-20.2.1/lib/python3.6/site-packages/nova/objects/instance.py". My goal is to trace the flow for "nova list --all" command. I am launching the nova-api service manually from the command line as follows: #/openstack/venvs/uwsgi-20.2.1-python3/bin/uwsgi --ini /etc/uwsgi/nova-api-os-compute.ini --workers 1 I am executing "nova list --all" command in another terminal. I have inserted pdb in instance.py as follows: ---- @base.remotable_classmethod def get_all(cls, context, expected_attrs=None): import pdb; pdb.set_trace() """Returns all instances on all nodes.""" db_instances = db.instance_get_all( context, columns_to_join=_expected_cols(expected_attrs)) return _make_instance_list(context, cls(), db_instances, expected_attrs) --- But when I fire the nova list --all command, I see no pdb prompt being shown in the nova-api window. Can anyone help me how to use the pdb to trace the flow of control for "nova list --all" command ? Thanks Kumar

3 3

[cinder] Bug report from 10-26-2022 to 11-08-2022
by Sofia Enriquez 09 Nov '22

09 Nov '22

This is a bug report from 10-26-2022 to 11-08-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1995204 "Fail to unify allocation_capacity_gb values among multiple Active-Active Cinder-Volume services ." Unassigned. - https://bugs.launchpad.net/python-cinderclient/+bug/1995883 "cinderclient against wallaby fails to create a snapshot." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1995863 "Failed to create multiple instances with boot volumes at the same time in version 20.0.2.dev11." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1996049 " Backup fails with VolumeNotFound but not set to error." Fix proposed to master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1995838 "Reimage results are stuck in downloading state." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1996039 "Volume State Update Failed After Backup Completed." Assigned to wanghelin. Cheers, Sofia -- Sofía 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

[kolla] Weekly meeting 9th Nov 22 cancelled
by Michał Nasiadka 08 Nov '22

08 Nov '22

Hola Koalas, The weekly meeting today is cancelled (I’m on full day workshops) - let’s talk next week. Michal

1 0

(Openstack-Keystone)Regarding Authentication issue of one user while login to Open Stack using AD password
by Adivya Singh 08 Nov '22

08 Nov '22

Hi Team, There is one issue , where a user is getting " Authenticated Failure" all of a sudden, and this user is the only user who is facing this problem. I tried to disable and enable the project if, Check the logs but do not found anything related to Keystone authentication Delete the Project id and Create it again , Results are same , Any insights what i can do more to fix this issue Regards Adivya Singh

2 8

[all][tc] Technical Committee next weekly meeting on 2022 Nov 9 at 1600 UTC (PLEASE NOTE: MEETING DAY/TIME CHANGED)
by Ghanshyam Mann 08 Nov '22

08 Nov '22

Hello Everyone, The technical Committee's weekly meeting day and time have changed to every Wed, 16 UTC. The next weekly meeting is scheduled for 2022 Nov 9, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Nov 8 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[kolla] Kolla-ansible plays with --limit failing if a compute host is down.
by Aidan Collins 08 Nov '22

08 Nov '22

Hello, It seems that the kolla-ansible plays reconfigure, prechecks, bootstrap-servers and deploy all fail when using limit if any compute host is down, even if it is not the one being specified by limit. Is there any way to configure gather-facts in these plays to not fail if this is the case? Due to the size of our plant we sometimes need to take down a compute host for maintenance and still provisiion new ones. We are using Victoria. Thanks a lot -aidan

2 2

[keystone][cache] How to tune role cache
by Eugen Block 08 Nov '22

08 Nov '22

Hi *, one of our customers has two almost identical clouds (Victoria), the only difference is that one of them has three control nodes (HA via pacemaker) and the other one only one control node. They use terraform to deploy lots of different k8s clusters and other stuff. In the HA cloud they noticed keystone errors when they purged a project (cleanly) and started the redeployment immediately after that. We did some tests to find out which exact keystone cache it is and it seems to be the role cache (default 600 seconds) which leads to an error in terraform, it reports that the project was not found and refers to the previous ID of the project. The same deployment seems to work in the single-control environment without these errors, it just works although the cache is enabled as well. I already tried to reduce the cache_time to 30 seconds but that doesn't help (although it takes more than 30 seconds until terraform is ready after the prechecks). But the downside of disabling the role cache entirely leads to significantly longer response times when using the dashboard or querying the APIs. Is there any way to tune the role cache in a way so we could have both a reasonable performance as well as being able to redeploy projects without a "sleep 600"? Any comments or recommendations are appreciated! Regards, Eugen

1 1

[Yoga][Cloudkitty] Some projects have their rate to 0 on some services
by wodel youchi 08 Nov '22

08 Nov '22

Hi, I deployed Cloudkitty with the following metrics.yml file : metrics: cpu: unit: instance alt_name: instance groupby: - id - user_id - project_id metadata: - flavor_name - flavor_id - vcpus mutate: NUMBOOL extra_args: aggregation_method: mean resource_type: instance force_granularity: 300 image.size: unit: MiB factor: 1/1048576 groupby: - id - user_id - project_id metadata: - container_format - disk_format extra_args: aggregation_method: mean resource_type: image force_granularity: 300 * volume.size: unit: GiB groupby: - id - user_id - project_id metadata: - volume_type extra_args: aggregation_method: mean resource_type: volume force_granularity: 300* I created a service for volume.size following the example here : https://docs.openstack.org/cloudkitty/yoga/user/rating/hashmap.html I added the user cloudkitty to the admin project and to another project named Project01. When showing the rates I have 0 rate on the Project01. For example : executing this command : * openstack rating dataframes get | grep volume.size* This volume belongs to an instance in the Admin project, as you can see rating is 4.5: | 2022-11-02T18:25:00 | 2022-11-02T18:30:00 | 31bfb5bcf7b7413da269d7a35a2fe69a |* [{'rating': '4.5', 'service': 'volume.size*', 'desc': {'volume_type': '246853e3-1215-4147-aef2-54012221ecc9', 'id': ' *07811807-474a-4eb5-91b5-ce2dcdd7be26*', 'project_id': '31bfb5bcf7b7413da269d7a35a2fe69a', 'user_id': '2a3f2478e334473e85527102b76f7a2e'}, 'volume': '3.0', 'rate_value': '1.5000'}, {'rating': '4.5', 'service': 'volume.size', 'desc': {'volume_type': '246853e3-1215-4147-aef2-54012221ecc9', 'id': '8a345711-0486-4733-b8bc-fd1966678aec', 'project_id': '31bfb5bcf7b7413da269d7a35a2fe69a', 'user_id': '2a3f2478e334473e85527102b76f7a2e'}, 'volume': '3.0', 'rate_value': '1.5000'}, {'rating': '4.5', 'service': 'volume.size', 'desc': {'volume_type': '246853e3-1215-4147-aef2-54012221ecc9', 'id': 'afd22819-8faa-47ee-8c09-75290d2cf18e', 'project_id': '31bfb5bcf7b7413da269d7a35a2fe69a', 'user_id': '2a3f2478e334473e85527102b76f7a2e'}, 'volume': '3.0', 'rate_value': '1.5000'}] This volume belongs to an instance in the Project01 project, as you can see rating is 0.0 : | 2022-11-03T10:35:00 | 2022-11-03T10:40:00 | 2e80eb3b3d344ef9993065ce689395d9 | *[{'rating': '0.0'*, 'service': 'volume.size', 'desc': {'volume_type': '246853e3-1215-4147-aef2-54012221ecc9', 'id': ' *1c396d46-8954-4e8c-b3e8-8e5e4eb6aba4*', 'project_id': '2e80eb3b3d344ef9993065ce689395d9', 'user_id': 'd9e5696e99954ae1ac87db9cca82c839'}, 'volume': '20.0', 'rate_value': '0.0000'}] I don't understand why it works for one and not the other? More info : (yogavenv) [deployer@rscdeployer ~]$ openstack rating hashmap service list +------------------------+--------------------------------------+ | Name | Service ID | +------------------------+--------------------------------------+ | instance | 06e17b49-8cd4-4cb9-8965-cb929ee12909 | | network.incoming.bytes | 634069b2-ca42-4a28-8778-ac69144fcc23 | | network.outgoing.bytes | 6c1fdaa7-15cb-41b4-be0e-109d64810dde | | volume.size | b6934ab1-8326-4281-89b9-f80294430321 | | image.size | d3652e08-8645-45fd-b7db-b710ae716876 | +------------------------+--------------------------------------+ (yogavenv) [deployer@rscdeployer ~]$ openstack rating hashmap mapping list -s b6934ab1-8326-4281-89b9-f80294430321 +--------------------------------------+-------+--------------------------------+------+----------+--------------------------------------+----------+------------+ | Mapping ID | Value | Cost | Type | Field ID | Service ID |* Group ID | Project ID* | +--------------------------------------+-------+--------------------------------+------+----------+--------------------------------------+----------+------------+ | f81aea1e-0651-4c0a-b043-496fdd892635 | None | 1.5000000000000000000000000000 | flat | None | b6934ab1-8326-4281-89b9-f80294430321 | *None | None * | +--------------------------------------+-------+--------------------------------+------+----------+--------------------------------------+----------+------------+ Regards.

2 1

[Keystone] Confusion about the admin role
by 韩光宇 08 Nov '22

08 Nov '22

Hi, I'd like to ask some questions about the admin role. When I grant the admin role to a user in a project, that user can also get the admin role for other projects in the same domain. If I do the following： ```shell openstack project create --domain default --description "Demo Project" myproject openstack user create --domain default --password-prompt myuser openstack role add --project myproject --user myuser admin ``` Then, the myuser user has the permission to grant himself the admin role of another project in the same domain. I used to understand that 'openstack role add --project myproject --user myuser admin' was simply granted to myuser as admin within the myproject project, but now I find that This is equivalent to having the admin role for the entire domain. Can I ask the design idea here, or what I think is wrong？ Thanks, Han Guangyu

2 2

[barbican] Meeting canceled today (2022-11-08)
by Grzegorz Grasza 08 Nov '22

08 Nov '22

Hi Team, I'm canceling the meeting today, since I'm attending an internal conference/meetup. Looking at the agenda, I see there is the storyboard issue we need to discuss, but this can surely wait another week. / Greg

1 0

[neutron] CI meeting 8th Nov cancelled
by Slawek Kaplonski 08 Nov '22

08 Nov '22

Hi, I can't chair CI meeting this week too. As there is nothing urgent really to speak about I talked with Rodolfo and we agreed to cancel this week's meeting. See You on the meeting next week (Nov 15th) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

(openstack-ansible) Container installation in openstack
by Adivya Singh 07 Nov '22

07 Nov '22

Hi Team, Any input on this, to install container service in openstack using ansible. standard global parametre Regards Adivya Singh

2 5

this is a openstack swift error(s)
by 无数的星球 07 Nov '22

07 Nov '22

After installing swift, I run "swift --debug stat" A serious error occurred, HTTP 401 error. The output information is shown below （ root@controller:~# swift --debug stat DEBUG:keystoneclient.auth.identity.v3.base:Making authentication request to http://controller:5000/v3/auth/tokens DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): controller:5000 DEBUG:urllib3.connectionpool:http://controller:5000 "POST /v3/auth/tokens HTTP/1.1" 201 5316 DEBUG:keystoneclient.auth.identity.v3.base:{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "ebe0c2002931431c9f6057f216c9aad1", "name": "swift", "password_expires_at": null}, "audit_ids": ["uxfmM8EtSDuf4TjLXur8LQ"], "expires_at": "2022-11-04T10:03:08.000000Z", "issued_at": "2022-11-04T09:03:08.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "6c50811c608f44ebb32132f039fd3ac0", "name": "service"}, "is_domain": false, "roles": [{"id": "8eb2665e258844bdb6daa7826ff7fd96", "name": "reader"}, {"id": "527a74431f6349738de18528c6d445e1", "name": "admin"}, {"id": "101015b8b34e41b4962b31440cf61520", "name": "member"}], "catalog": [{"endpoints": [{"id": "6e624d24e7e046e8bda14929bbb345c5", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}, {"id": "bcdb2ad98de94420926cae68b27e4ccc", "interface": "public", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}, {"id": "cc52757d98b04bdd88026d1087ae9a5d", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}], "id": "03943f266612412ebd2ea111596cfb75", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "68950739e40340768da67915b2cf6aac", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}, {"id": "8a68f4ac2d4845959e9515304dd75eb3", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}, {"id": "da32e6e91bff4279bafa3329053e3704", "interface": "public", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}], "id": "33f2243a764d4bdc9a157e6a9d5a9c6a", "type": "network", "name": ""}, {"endpoints": [{"id": "166e07fa638e49b987595323bd3bcf61", "interface": "public", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}, {"id": "cbb01761367e4acf83c658333e2de386", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}, {"id": "db8dd3cb0dd04b29bfb96a608fb72d99", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}], "id": "4f86e32926a64fb99de6e6919c714926", "type": "image", "name": ""}, {"endpoints": [{"id": "93e135f5a0824caa8b8fc9fa0df74bd4", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "f21e50d72b914333952b7d3d8fd2578d", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "f669072bd0a84c5b85ca70714e6b212d", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}], "id": "554089befdd94ee1a87a03de006a33c6", "type": "volumev2", "name": ""}, {"endpoints": [{"id": "7f0d59134e60478ab7fbb0b72772cbab", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}, {"id": "ac50c3fb0af947508497d8344b8e6d0a", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}, {"id": "b41204a96b7a43f68a7f8f2613163df3", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}], "id": "5e09e36a7744495389ea6159048eef5e", "type": "compute", "name": ""}, {"endpoints": [{"id": "1e56c094a9ea4e7a80132280df1925f4", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}, {"id": "896c40aa1ada41ed82bcb0c39d87d8f5", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}, {"id": "b4d50334c3174633aa1372f13b7c19ed", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}], "id": "90e53b94f1b84b99ae6fa03c793a30b1", "type": "placement", "name": ""}, {"endpoints": [{"id": "50653fa05fde458c9e04be6410d3407f", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "794a0750211b4034bc40d4095fab09df", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "951627fca8974f27a21fcb0a075cecc1", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}], "id": "d8cca1398508471f937533ab72ffae96", "type": "volumev3", "name": ""}, {"endpoints": [{"id": "29c38e196a6743aa9ff92c7a26362bb2", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "adce2914f26f4d1ead7036255a690d42", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "bc4246d33f3146be87c49fd47af98172", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8080/v1", "region": "RegionOne"}], "id": "f256c47fcfaa48f78baaf34066c54960", "type": "object-store", "name": "swift"}]}} DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): controller:8080 DEBUG:urllib3.connectionpool:http://controller:8080 "HEAD /v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 HTTP/1.1" 401 0 INFO:swiftclient:REQ: curl -i http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 -I -H "X-Auth-Token: gAAAAABjZNVMHpSugcariFAL92JRrJXtfLTk8sAtac7CZY9BEUoOxg3hnI2xKyv-DBkYuFQNVEAQiL68-5in7gfh3SrWTn_P5s3QB_GWOVGMOobkSYXiiKtqzL46nUySqLKpJiG0IMd06ufiC3ILCZguXu5yfoAA9U9Z--XhBmyhXmcWLaQ1Ybo" INFO:swiftclient:RESP STATUS: 401 Unauthorized INFO:swiftclient:RESP HEADERS: {'Content-Type': 'text/html; charset=UTF-8', 'Www-Authenticate': 'Swift realm="AUTH_6c50811c608f44ebb32132f039fd3ac0"', 'Content-Length': '0', 'X-Trans-Id': 'txe65f29e7acb04920bb9f6-006364d54c', 'X-Openstack-Request-Id': 'txe65f29e7acb04920bb9f6-006364d54c', 'Date': 'Fri, 04 Nov 2022 09:03:08 GMT'} DEBUG:keystoneclient.auth.identity.v3.base:Making authentication request to http://controller:5000/v3/auth/tokens DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): controller:5000 DEBUG:urllib3.connectionpool:http://controller:5000 "POST /v3/auth/tokens HTTP/1.1" 201 5316 DEBUG:keystoneclient.auth.identity.v3.base:{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "ebe0c2002931431c9f6057f216c9aad1", "name": "swift", "password_expires_at": null}, "audit_ids": ["_gjaOZg2TquDXq7PTISWNA"], "expires_at": "2022-11-04T10:03:09.000000Z", "issued_at": "2022-11-04T09:03:09.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "6c50811c608f44ebb32132f039fd3ac0", "name": "service"}, "is_domain": false, "roles": [{"id": "527a74431f6349738de18528c6d445e1", "name": "admin"}, {"id": "8eb2665e258844bdb6daa7826ff7fd96", "name": "reader"}, {"id": "101015b8b34e41b4962b31440cf61520", "name": "member"}], "catalog": [{"endpoints": [{"id": "6e624d24e7e046e8bda14929bbb345c5", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}, {"id": "bcdb2ad98de94420926cae68b27e4ccc", "interface": "public", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}, {"id": "cc52757d98b04bdd88026d1087ae9a5d", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:5000/v3/", "region": "RegionOne"}], "id": "03943f266612412ebd2ea111596cfb75", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "68950739e40340768da67915b2cf6aac", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}, {"id": "8a68f4ac2d4845959e9515304dd75eb3", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}, {"id": "da32e6e91bff4279bafa3329053e3704", "interface": "public", "region_id": "RegionOne", "url": "http://controller:9696", "region": "RegionOne"}], "id": "33f2243a764d4bdc9a157e6a9d5a9c6a", "type": "network", "name": ""}, {"endpoints": [{"id": "166e07fa638e49b987595323bd3bcf61", "interface": "public", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}, {"id": "cbb01761367e4acf83c658333e2de386", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}, {"id": "db8dd3cb0dd04b29bfb96a608fb72d99", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:9292", "region": "RegionOne"}], "id": "4f86e32926a64fb99de6e6919c714926", "type": "image", "name": ""}, {"endpoints": [{"id": "93e135f5a0824caa8b8fc9fa0df74bd4", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "f21e50d72b914333952b7d3d8fd2578d", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "f669072bd0a84c5b85ca70714e6b212d", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8776/v2/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}], "id": "554089befdd94ee1a87a03de006a33c6", "type": "volumev2", "name": ""}, {"endpoints": [{"id": "7f0d59134e60478ab7fbb0b72772cbab", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}, {"id": "ac50c3fb0af947508497d8344b8e6d0a", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}, {"id": "b41204a96b7a43f68a7f8f2613163df3", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8774/v2.1", "region": "RegionOne"}], "id": "5e09e36a7744495389ea6159048eef5e", "type": "compute", "name": ""}, {"endpoints": [{"id": "1e56c094a9ea4e7a80132280df1925f4", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}, {"id": "896c40aa1ada41ed82bcb0c39d87d8f5", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}, {"id": "b4d50334c3174633aa1372f13b7c19ed", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8778", "region": "RegionOne"}], "id": "90e53b94f1b84b99ae6fa03c793a30b1", "type": "placement", "name": ""}, {"endpoints": [{"id": "50653fa05fde458c9e04be6410d3407f", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "794a0750211b4034bc40d4095fab09df", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "951627fca8974f27a21fcb0a075cecc1", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8776/v3/6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}], "id": "d8cca1398508471f937533ab72ffae96", "type": "volumev3", "name": ""}, {"endpoints": [{"id": "29c38e196a6743aa9ff92c7a26362bb2", "interface": "public", "region_id": "RegionOne", "url": "http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "adce2914f26f4d1ead7036255a690d42", "interface": "internal", "region_id": "RegionOne", "url": "http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0", "region": "RegionOne"}, {"id": "bc4246d33f3146be87c49fd47af98172", "interface": "admin", "region_id": "RegionOne", "url": "http://controller:8080/v1", "region": "RegionOne"}], "id": "f256c47fcfaa48f78baaf34066c54960", "type": "object-store", "name": "swift"}]}} DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): controller:8080 DEBUG:urllib3.connectionpool:http://controller:8080 "HEAD /v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 HTTP/1.1" 401 0 INFO:swiftclient:REQ: curl -i http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 -I -H "X-Auth-Token: gAAAAABjZNVNWPHppqLAGxDFedVVT4FiMam_wPsK0HL2siFsQhBz2-LewBYcX5FCspKLclWzrGRj0ChEE2Rd-6auT_fpiI5uHFt11zOpDZRN83zxvGTp_FgtN5p7h5dG6I1yvPVi6ICurC8MhfK7SpfKupdK5TZVt7r2hZkdjd7TdHj3-m-Bgdc" INFO:swiftclient:RESP STATUS: 401 Unauthorized INFO:swiftclient:RESP HEADERS: {'Content-Type': 'text/html; charset=UTF-8', 'Www-Authenticate': 'Swift realm="AUTH_6c50811c608f44ebb32132f039fd3ac0"', 'Content-Length': '0', 'X-Trans-Id': 'txff99e52141174a038c7d1-006364d54d', 'X-Openstack-Request-Id': 'txff99e52141174a038c7d1-006364d54d', 'Date': 'Fri, 04 Nov 2022 09:03:09 GMT'} ERROR:swiftclient.service:Account HEAD failed: http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 401 Unauthorized (txn: txff99e52141174a038c7d1-006364d54d) Traceback (most recent call last):   File "/usr/lib/python3/dist-packages/swiftclient/service.py", line 555, in stat     items, headers = get_future_result(stats_future)   File "/usr/lib/python3/dist-packages/swiftclient/service.py", line 251, in get_future_result     res = f.result(timeout=timeout)   File "/usr/lib/python3.8/concurrent/futures/_base.py", line 444, in result     return self.__get_result()   File "/usr/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result     raise self._exception   File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/lib/python3/dist-packages/swiftclient/multithreading.py", line 201, in conn_fn     return fn(*conn_args, **kwargs)   File "/usr/lib/python3/dist-packages/swiftclient/command_helpers.py", line 24, in stat_account     headers = conn.head_account(headers=req_headers)   File "/usr/lib/python3/dist-packages/swiftclient/client.py", line 1902, in head_account     return self._retry(None, head_account, headers=headers)   File "/usr/lib/python3/dist-packages/swiftclient/client.py", line 1856, in _retry     rv = func(self.url, self.token, *args,   File "/usr/lib/python3/dist-packages/swiftclient/client.py", line 924, in head_account     raise ClientException.from_response(resp, 'Account HEAD failed', body) swiftclient.exceptions.ClientException: Account HEAD failed: http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 401 Unauthorized (txn: txff99e52141174a038c7d1-006364d54d) Account HEAD failed: http://controller:8080/v1/AUTH_6c50811c608f44ebb32132f039fd3ac0 401 Unauthorized Failed Transaction ID: txff99e52141174a038c7d1-006364d54d ） The output of "tail -f/var/log/*"  is as follows Nov 4 13:49:42 controller proxy-server: - - 04/Nov/2022/13/49/42 HEAD /v1/AUTH_6c50811c608f44ebb32132f039fd3ac0%3Fformat%3Djson HTTP/1.0 200 - Swift - - - - tx967ed9b9c29b4828b646d-0063651876 - 0.0039 RL - 1667569782.696980715 1667569782.700921297 - Nov 4 13:49:42 controller proxy-server: 192.168.100.10 192.168.100.10 04/Nov/2022/13/49/42 HEAD /v1/AUTH_6c50811c608f44ebb32132f039fd3ac0%3Fformat%3Djson HTTP/1.0 401 - python-swiftclient-3.11.0 gAAAAABjZRh2... - - - tx967ed9b9c29b4828b646d-0063651876 - 0.0055 - - 1667569782.696368933 1667569782.701885939 - Nov 4 13:49:44 controller proxy-server: 192.168.100.10 192.168.100.10 04/Nov/2022/13/49/44 HEAD /v1/AUTH_6c50811c608f44ebb32132f039fd3ac0%3Fformat%3Djson HTTP/1.0 401 - python-swiftclient-3.11.0 gAAAAABjZRh4... - - - tx4ac048f132544deaaac45-0063651878 - 0.0009 - - 1667569784.155652046 1667569784.156536341 - If you need/etc/swift/proxy-server.conf Please receive in the attachment thank you!!!

2 1

Neutron
by sajeyks mwangi 07 Nov '22

07 Nov '22

Hello! I installed openstack on Ubuntu using devstack and after running "./stack.sh" I tried to log in the dashboard and I got the error "Connection to neutron failed"

2 1

[cinder][kolla][OpenstackAnsible] Zed Cycle-Trailing Release Deadline
by Herve Beraud 07 Nov '22

07 Nov '22

Hello teams with trailing projects, The Zed cycle-trailing release deadline is in ~1 months [1], and all projects following the cycle-trailing release model must release their Zed deliverables by 16 Dec, 2022. The following trailing projects haven't been released yet for Zed (aside the release candidates versions if exists). Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. Thanks for your time. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[Heat] X-OpenStack-Request-ID changed during request processing
by Vadym Markov 07 Nov '22

07 Nov '22

Hi everyone Found that Heat doesn't keep the value of X-OpenStack-Request-ID header during request processing. Simple stack delete leads to 4 different request id, only the last of them corresponds to heat engine processing the request. Investigation shows that req-id "duplicates" twice - when client goes via redirect response returned by API and at version negotiation at every connect to API endpoint. I assume that this situation is not expected, and it really spoils work with heat api logs. Any ideas on how to make the situation more clear? Also looks like that header name is case-dependent in some places, and Oslo-middleware and Heat handles them differently. However, it needs additional investigation. I propose to turn off logging for successful negotiation and re-use req-id in keystoneuth during redirect. If it is ok, I plan to submit corresponding patches to upstream. Here is a piece of log related to stack delete. Only "req-843ac3a4..." exists in the heat-engine log. лис 07 12:21:59 ubuntu devstack(a)h-api.service[172816]: DEBUG heat.api.middleware.version_negotiation [None req-5b613e29-8dd9-458d-b908-4802f90c0b2f admin admin] Processing request: DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1 Accept: application/json {{(pid=172816) process_request /opt/stack/heat/heat/api/middleware/version_negotiation.py:57}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172816]: DEBUG heat.api.middleware.version_negotiation [None req-5b613e29-8dd9-458d-b908-4802f90c0b2f admin admin] Matched versioned URI. Version: 1.0 {{(pid=172816) process_request /opt/stack/heat/heat/api/middleware/version_negotiation.py:69}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172816]: INFO heat.common.wsgi [None req-ec73b5d8-5025-40e0-90d7-4010d39cb450 admin admin] Processing request: DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1 лис 07 12:21:59 ubuntu devstack(a)h-api.service[172816]: DEBUG heat.common.wsgi [None req-ec73b5d8-5025-40e0-90d7-4010d39cb450 admin admin] Calling StackController.lookup {{(pid=172816) __call__ /opt/stack/heat/heat/common/wsgi.py:823}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172816]: [pid: 172816|app: 0|req: 12/24] 192.168.123.5 () {66 vars in 1391 bytes} [Mon Nov 7 12:21:59 2022] DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1 => generated 377 bytes in 167 msecs (HTTP/1.1 302) 5 headers in 289 bytes (1 switches on core 3) лис 07 12:21:59 ubuntu devstack(a)h-api.service[172815]: DEBUG heat.api.middleware.version_negotiation [None req-f1eb3c1b-b76c-42fa-8998-31bb2cc43030 admin admin] Processing request: DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1/05e56d91-6b11-4e20-83f3-e2923667019b Accept: application/json {{(pid=172815) process_request /opt/stack/heat/heat/api/middleware/version_negotiation.py:57}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172815]: DEBUG heat.api.middleware.version_negotiation [None req-f1eb3c1b-b76c-42fa-8998-31bb2cc43030 admin admin] Matched versioned URI. Version: 1.0 {{(pid=172815) process_request /opt/stack/heat/heat/api/middleware/version_negotiation.py:69}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172815]: INFO heat.common.wsgi [None req-843ac3a4-408d-4473-844f-f4b109ad1725 admin admin] Processing request: DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1/05e56d91-6b11-4e20-83f3-e2923667019b лис 07 12:21:59 ubuntu devstack(a)h-api.service[172815]: DEBUG heat.common.wsgi [None req-843ac3a4-408d-4473-844f-f4b109ad1725 admin admin] Calling StackController.delete {{(pid=172815) __call__ /opt/stack/heat/heat/common/wsgi.py:823}} лис 07 12:21:59 ubuntu devstack(a)h-api.service[172815]: [pid: 172815|app: 0|req: 13/25] 192.168.123.5 () {66 vars in 1502 bytes} [Mon Nov 7 12:21:59 2022] DELETE /heat-api/v1/8a76e6c8cc714288823dfe3677174893/stacks/stack_1/05e56d91-6b11-4e20-83f3-e2923667019b => generated 0 bytes in 118 msecs (HTTP/1.1 204) 2 headers in 112 bytes (1 switches on core 0)

1 0

[neutron] Bug Deputy Report October 31 - November 6
by Elvira Garcia Ruiz 07 Nov '22

07 Nov '22

Hi everyone, I was the bug deputy last week. Find the summary below: High: ------- - neutron.privileged.agent.linux.ip_lib.InterfaceOperationNotSupported: Operation not supported on interface https://bugs.launchpad.net/neutron/+bug/1995735 Assigned to Felipe Reyes Fix proposed https://review.opendev.org/c/openstack/neutron/+/863779 - bulk port create: TypeError: Bad prefix type for generating IPv6 address by EUI-64 https://bugs.launchpad.net/neutron/+bug/1995732 Unassigned - OVN: HA chassis group priority is different than gateway chassis priority https://bugs.launchpad.net/neutron/+bug/1995078 I think this is a legit bug. However, a second look by someone else would be appreciated. Unassigned - ORM session: SQL execution without transaction in progress https://bugs.launchpad.net/neutron/+bug/1995738 Assigned to Felipe Reyes Fix proposed https://review.opendev.org/c/openstack/neutron/+/863780 Undecided: --------------- - [ML2/OVN] After upgrading from Xena to Yoga neutron-dhcp-agent is not working for Baremetals https://bugs.launchpad.net/neutron/+bug/1995287 Rodolfo is discussing with the reporter. It has not yet been confirmed to be a bug. - floating ip portforwarding from external not working https://bugs.launchpad.net/neutron/+bug/1995614 Unassigned >From the description this could be legit but I have no experience with the neutron- L3-agent-floatingip, so an experienced opinion would be appreciated on this one. I left a question for the reporter. Kind regards, Elvira

1 0

[Kolla-ansible][Yoga] How to update an Openstack deployment with new containers?
by wodel youchi 07 Nov '22

07 Nov '22

Hi, I followed this link : https://docs.openstack.org/kolla-ansible/yoga/user/operating-kolla.html It says that : This procedure is for upgrading from series to series, not for doing updates within a series. Inside a series, *it is usually sufficient to just update the kolla-ansible package, rebuild (if needed) and pull the images, and run kolla-ansible deploy again. Please follow release notes to check if there are any issues to be aware of.* In my deployment I am using a local registry, so I pulled the new images, tagged them then pushed them into my registry. I can see that the container's images are newer than the ones I had. I then updated my kolla-ansible package using : $ source yogavenv (yogavenv) $ pip install --upgrade git+ https://opendev.org/openstack/kolla-ansible@stable/yoga Finally I launched the deploy, but it seems that nothing has changed. The containers have not been restarted. Any ideas? Is there a way to verify that a container belongs to a particular image build? How can I be sure that my deployment has been updated with new containers? Regards.

2 1

openstack mentee
by Deeghayu Baddegama 06 Nov '22

06 Nov '22

Hi, I hope to use openstack as the platform in one of my projects. I would like to be a mentee to study about openstack. But when I try to sign up as a mentee it shows an error message. The screenshot attached here. Could you please guide me through this? Thank you. Best regards, Deeghayu Baddegama, Sri Lanka

1 0

openstack multi region with internal ip
by Parsa Aminian 05 Nov '22

05 Nov '22

hello Im using kolla-ansible and for security reasons I use invalid ip for main compute ip . my compute have 2 network adapter and first adapter that is for management is not accessible from outside . the problem is I want to add new region in other datacenter and on openstack with multiregion keystone is deploy only on one region not all regions so my computes with invalid ip can not access keystone anymore . is there any solution for this case ?

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Nov 04: Reading: 5 min
by Ghanshyam Mann 04 Nov '22

04 Nov '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's video meeting on Nov 03. Most of the meeting discussions are summarized in this email. Meeting recording is available @ https://www.youtube.com/watch?v=cjpxiT2Egok and summary logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-03-15.05.log.html * Next TC weekly meeting will be on Nov 9 Wed at 16:00 UTC, please make note of new day/time for TC meetings. Feel free to add the topic to the agenda[1] by Nov 8. 2. What we completed this week: ========================= * Deprecated openstack-ansible rsyslog roles[2] * Completed the user survey TC question updates for 2023 user survey[3] 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Renovate translation SIG i18 ---------------------------------- * SIG i18 user Survey questions are finalized for 2023 user survey * rosmaita is coordinating with Weblate and as per them there shouldn't be any issue in hosting OpenStack translations. He will connect them with SIG i18n to work out details. TC Weekly meeting new day and time -------------------------------------------- We agreed to shift TC weekly meeting on evry wed on 16:00 UTC. This will be effective from next week (next meeting is on Nov 9, 16:00 UTC)[6]. TC Video meeting discussion ---------------------------------- Even though we discussed it many times in past and TC explained about having a monthly Video call and rest three week as IRC meeting, this came up again in yesterday meeting. We discussed both pros and cons of monthly video call but did not conclude anything. JayF is proposed the resolution to discuss it further if we want to continue on this monthly Video call or not[7]. TC chair nomination & election process ----------------------------------------------- We are formalizing the process of TC chair nomination process. Two options are up for the review[8][9]. Fixing Zuul config error ---------------------------- We are tracking this in one of the item in TC tracker, please refer there for the progress[10]. Project updates ------------------- * Add zookeeper role under OpenStack-Ansible governance[11] * Add Skyline repository for OpenStack-Ansible[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. See you all next week in PTG! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/863076 [3] https://etherpad.opendev.org/p/tc-2023-user-survey-questions [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-03-15.05.log.html#… [7] https://review.opendev.org/c/openstack/governance/+/863685 [8] https://review.opendev.org/c/openstack/governance/+/862772 [9] https://review.opendev.org/c/openstack/governance/+/862774 [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] https://review.opendev.org/c/openstack/governance/+/863161 [12] https://review.opendev.org/c/openstack/governance/+/863166 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 04 Nov '22

04 Nov '22

Hello Neutrinos: Today's meeting is cancelled due to the lack of agenda. See you next week. Have a nice weekend.

1 0

(openstack-horizon)
by Adivya Singh 04 Nov '22

04 Nov '22

hi Team, I'm facing one issue after the actual outage happened in my openstack env using horizon, The horizon overview page does not happen. i can get in to Stack page directly, But not the overview it just get timed out i restarted the mem cache services to no avail Is there anything else i can try Regards Adivya Singh

1 0

Infrastructure monitoring
by KK CHN 03 Nov '22

03 Nov '22

List,, Looking for an Infrastructure monitoring tool which is in the open source domain without any proprietary license involved for production use. Need to monitor Switches, UTMs/Firewalls, Physical servers, Virtual Machines/Virtual resources, Storage /Storage servers, Applications/daemons running status etc. Complete Infrastructure monitoring and alerts in advance for rectifying possible issues/outages. Regards, Krish

1 0

(no subject)
by Swogat Pradhan 03 Nov '22

03 Nov '22

I have configured a 3 node pcs cluster for openstack. To test the HA, i issue the following commands: iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT && iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT && iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 5016 -j ACCEPT && iptables -A INPUT -p udp -m state --state NEW -m udp --dport 5016 -j ACCEPT && iptables -A INPUT ! -i lo -j REJECT --reject-with icmp-host-prohibited && iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT && iptables -A OUTPUT -p tcp --sport 5016 -j ACCEPT && iptables -A OUTPUT -p udp --sport 5016 -j ACCEPT && iptables -A OUTPUT ! -o lo -j REJECT --reject-with icmp-host-prohibited When i issue iptables command on 1 node then it is fenced and forced to reboot and cluster works fine. But when i issue this on 2 of the controller nodes the resource bundles fail and doesn't come back up. [root@overcloud-controller-1 ~]# pcs status Cluster name: tripleo_cluster Cluster Summary: * Stack: corosync * Current DC: overcloud-controller-1 (version 2.1.2-4.el8-ada5c3b36e2) - partition WITHOUT quorum * Last updated: Sat Oct 29 03:15:29 2022 * Last change: Sat Oct 29 03:12:26 2022 by root via crm_resource on overcloud-controller-1 * 19 nodes configured * 68 resource instances configured Node List: * Node overcloud-controller-0: UNCLEAN (offline) * Node overcloud-controller-2: UNCLEAN (offline) * Online: [ overcloud-controller-1 ] Full List of Resources: * ip-172.25.201.91 (ocf::heartbeat:IPaddr2): Started overcloud-controller-0 (UNCLEAN) * ip-172.25.201.150 (ocf::heartbeat:IPaddr2): Started overcloud-controller-2 (UNCLEAN) * ip-172.25.201.206 (ocf::heartbeat:IPaddr2): Stopped * ip-172.25.201.250 (ocf::heartbeat:IPaddr2): Started overcloud-controller-0 (UNCLEAN) * ip-172.25.202.50 (ocf::heartbeat:IPaddr2): Stopped * ip-172.25.202.90 (ocf::heartbeat:IPaddr2): Started overcloud-controller-2 (UNCLEAN) * Container bundle set: haproxy-bundle [ 172.25.201.68:8787/tripleomaster/openstack-haproxy:pcmklatest]: * haproxy-bundle-podman-0 (ocf::heartbeat:podman): Started overcloud-controller-0 (UNCLEAN) * haproxy-bundle-podman-1 (ocf::heartbeat:podman): Stopped * haproxy-bundle-podman-2 (ocf::heartbeat:podman): Started overcloud-controller-2 (UNCLEAN) * haproxy-bundle-podman-3 (ocf::heartbeat:podman): Stopped * Container bundle set: galera-bundle [ 172.25.201.68:8787/tripleomaster/openstack-mariadb:pcmklatest]: * galera-bundle-0 (ocf::heartbeat:galera): Stopped overcloud-controller-0 (UNCLEAN) * galera-bundle-1 (ocf::heartbeat:galera): Stopped * galera-bundle-2 (ocf::heartbeat:galera): Stopped overcloud-controller-2 (UNCLEAN) * galera-bundle-3 (ocf::heartbeat:galera): Stopped * Container bundle set: redis-bundle [ 172.25.201.68:8787/tripleomaster/openstack-redis:pcmklatest]: * redis-bundle-0 (ocf::heartbeat:redis): Stopped * redis-bundle-1 (ocf::heartbeat:redis): Stopped overcloud-controller-2 (UNCLEAN) * redis-bundle-2 (ocf::heartbeat:redis): Stopped overcloud-controller-0 (UNCLEAN) * redis-bundle-3 (ocf::heartbeat:redis): Stopped * Container bundle set: ovn-dbs-bundle [ 172.25.201.68:8787/tripleomaster/openstack-ovn-northd:pcmklatest]: * ovn-dbs-bundle-0 (ocf::ovn:ovndb-servers): Stopped overcloud-controller-2 (UNCLEAN) * ovn-dbs-bundle-1 (ocf::ovn:ovndb-servers): Stopped overcloud-controller-0 (UNCLEAN) * ovn-dbs-bundle-2 (ocf::ovn:ovndb-servers): Stopped * ovn-dbs-bundle-3 (ocf::ovn:ovndb-servers): Stopped * ip-172.25.201.208 (ocf::heartbeat:IPaddr2): Started overcloud-controller-2 (UNCLEAN) * Container bundle: openstack-cinder-backup [ 172.25.201.68:8787/tripleomaster/openstack-cinder-backup:pcmklatest]: * openstack-cinder-backup-podman-0 (ocf::heartbeat:podman): Started overcloud-controller-0 (UNCLEAN) * Container bundle: openstack-cinder-volume [ 172.25.201.68:8787/tripleomaster/openstack-cinder-volume:pcmklatest]: * openstack-cinder-volume-podman-0 (ocf::heartbeat:podman): Stopped * Container bundle set: rabbitmq-bundle [ 172.25.201.68:8787/tripleomaster/openstack-rabbitmq:pcmklatest]: * rabbitmq-bundle-0 (ocf::heartbeat:rabbitmq-cluster): Stopped overcloud-controller-2 (UNCLEAN) * rabbitmq-bundle-1 (ocf::heartbeat:rabbitmq-cluster): Stopped overcloud-controller-0 (UNCLEAN) * rabbitmq-bundle-2 (ocf::heartbeat:rabbitmq-cluster): Stopped * rabbitmq-bundle-3 (ocf::heartbeat:rabbitmq-cluster): Stopped * ip-172.25.204.250 (ocf::heartbeat:IPaddr2): Started overcloud-controller-0 (UNCLEAN) * ceph-nfs (systemd:ceph-nfs@pacemaker): Started overcloud-controller-0 (UNCLEAN) * Container bundle: openstack-manila-share [ 172.25.201.68:8787/tripleomaster/openstack-manila-share:pcmklatest]: * openstack-manila-share-podman-0 (ocf::heartbeat:podman): Started overcloud-controller-0 (UNCLEAN) * stonith-fence_ipmilan-48d539a11820 (stonith:fence_ipmilan): Stopped * stonith-fence_ipmilan-48d539a1188c (stonith:fence_ipmilan): Started overcloud-controller-2 (UNCLEAN) * stonith-fence_ipmilan-246e96349068 (stonith:fence_ipmilan): Started overcloud-controller-2 (UNCLEAN) * stonith-fence_ipmilan-246e96348d30 (stonith:fence_ipmilan): Stopped Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled PCS requires more than half the nodes to be alive for the cluster to work. To fix this step I issued a command:*pcs no-quorum-policy=ignore.* And now the PCS cluster keeps on running even when there is no quorum. Now the issue i have is the mariadb-bundle becomes slave and dosen't get promoted to master. Can you please suggest a proper workaround when more than half nodes go down and my cloud will be still running. With regards, Swogat Pradhan

2 2

[Kolla-ansible][Yoga][Trove] Creation of instance fails
by wodel youchi 03 Nov '22

03 Nov '22

Hi, The creation of the Trove instance fails, from my debugging I found this : - The db instance is not responding on its trove interface. - The controller (trove-management) can't reach it. I have a vlan network dedicated to the Trove instances, I have created a simple VM on that network and used the same security group used by the db instance. The simple VM responds to ping and ssh connections, the Trove instance does not. I added another interface to the db instance in another network, and the instance pings and responds to ssh connections on it!!! still I don't know how to access the db instance via ssh. I don't understand. Regards.

2 4

Re: [all][tc] Technical Committee next weekly meeting on 2022 Nov 3 at 1500 UTC
by Ghanshyam Mann 02 Nov '22

02 Nov '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting scheduled at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check * 2023.1 TC tracker ** https://etherpad.opendev.org/p/tc-2023.1-tracker * TC questions for the 2023 user survey ** https://etherpad.opendev.org/p/tc-2023-user-survey-questions ** Deadline: Oct 30 ** TC chair election process * TC weekly meeting time ** https://framadate.org/xR6HoeDpdXXfiueb * Recurring tasks check ** Bare 'recheck' state ** https://etherpad.opendev.org/p/recheck-weekly-summary * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[tc][ptls] OpenStack User Survey Update
by josh＠openinfra.dev 02 Nov '22

02 Nov '22

Hello everyone, Thank you all for submitting updates to the OpenStack User Survey. We have made adjustments to the survey, and published them as the OpenStack User Survey 2023, which you can find here: [ https://www.openstack.org/user-survey/survey-2023/ ]( https://www.openstack.org/user-survey/survey-2023/ ) If you have any additional adjustments or additions, please don't hesitate to let me know. Thank you! Josh Lohse josh(a)openinfra.dev

1 0

[security-sig] Cancelling this month's meeting
by Jeremy Stanley 02 Nov '22

02 Nov '22

I'm on vacation this week and don't expect to be around a computer tomorrow in order to chair the meeting, so am cancelling it for November. If anyone had topics they wanted to bring up, please just raise them here on the ML or in the #openstack-security channel on OFTC and I'll try to follow up there as appropriate. Additionally, we discussed at the PTG that the standing meeting time is inconvenient for multiple participants, so I'll be following up with a poll to work out a more consensual schedule. Thanks! -- Jeremy Stanley

1 0

(Open Stack Designate) Query regarding bind containers in Openstack
by Adivya Singh 02 Nov '22

02 Nov '22

Hi Team, I have a query, where I have installed the Designate Container and configured the name server accordingly. My question is related to Designate Container, Do i need to install the bind services independently in each designate container of all the 3 controllers Regards Adivya Singh

2 1

No bug meeting today
by Sofia Enriquez 02 Nov '22

02 Nov '22

-- Sofía 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

[Kolla-ansible][Yoga] which version of fedora-core to use with Magnum?
by wodel youchi 01 Nov '22

01 Nov '22

Hi, Could you point out which version of fedora-core to use with magnum? Is it the same as Xena : fedora-core 33? Regards.

1 0

[Kolla-ansible][Xena] How to update an Openstack deployment with new containers?
by wodel youchi 01 Nov '22

01 Nov '22

Hi, The documentation of kolla-ansible Xena does not talk about updating an existing Xena deployment with new containers. Could you please help with this? I found some lines about that in Yoga version, saying that, to update an existing deployment you have to : 1 - Update kolla-ansible it self : $ source xenavenv (xenavenv) $ pip install --upgrade git+ https://opendev.org/openstack/kolla-ansible@stable/xena 2 - Update the container Images with Docker pull 3 - Update my local registry if I am using one, and in my case I am, so I deleted the registry images then I recreated them. 4 - Then finally deploy again (xenavenv) $ kolla-ansible -i multinode deploy Is this the right procedure? because I followed the same procedure and I think it didn't change anything. For example I am taking nova-libvirt container as and example, in my local registry I have this : [root@rcdndeployer2 ~]# docker images | grep nova-libvirt 192.168.2.34:4000/openstack.kolla/centos-source-nova-libvirt xena 5be83d680102 31 hours ago 2. 34GB quay.io/openstack.kolla/centos-source-nova-libvirt xena *5be83d680102* *31 hours ago * 2. 34GB [root@rcdndeployer2 ~]# docker inspect -f '{{ .Created }}' *5be83d680102 * *2022-10-25*T02:33:13.172550584Z But in my compute nodes I have this : root@computehci24 ~]# docker ps | grep nova-lib b56a12bfd482 192.168.2.34:4000/openstack.kolla/centos-source-nova-libvirt:xena "dumb-init --single-…" *5 months ag**o Up Up 5 months (healthy) nova_libvirt* Regards.

1 1

[cinder][PTG] 2023.1 Antelope PTG Summary
by Rajat Dhasmana 01 Nov '22

01 Nov '22

Hello everyone, Here[1] is the summary of 2023.1 Antelope Cinder PTG conducted from 18th October to 21st October 2022, 1300-1700 UTC. The link to the etherpad and recordings are included. The action items are added in *conclusion* section of each topic. Let me know if any information needs to be updated. [1] https://wiki.openstack.org/wiki/CinderAntelopePTGSummary - Rajat Dhasmana

1 0

[all] [tripleo] opendev Gerrit is down
by Cédric Jeanneret 01 Nov '22

01 Nov '22

Hello there, For those who didn't get the IRC notification earlier today: gerrit is dead. The Infra team is working on that issue, but it will apparently take some time. Thank you for your patience! Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 1

Discontinuing Winstackers
by Lucian Petrut 01 Nov '22

01 Nov '22

Running Openstack on Windows has been driven by Cloudbase Solutions ever since Folsom (2012). Here are the most noteworthy contributions: * nova hyper-v driver - in-tree plus out-of-tree compute-hyperv driver * os-win - common Windows library for Openstack * neutron hyperv ml2 plugin and agent * ovs on Windows and neutron ovs agent support * cinder drivers - SMB and Windows iSCSI * os-brick Windows connectors - iSCSI, FC, SMB, RBD * ceilometer Windows poller * manila Windows driver * glance Windows support * freerdp gateway * last but not least, CI test systems for (most of) the above Due to a shift in business focus and the increased operational costs of maintaining the CI systems, we are no longer in a position to proactively support Openstack on Windows. However, we will continue to support Cloudbase-init (cloud-init equivalent for Windows) as well as the Openstack Windows imaging tools. If there are any interested parties that would like to step up as Winstacker maintainers, please let us know and we will provide any required assistance. Regards, Lucian Petrut Cloudbase Solutions Winstackers PTL

1 0