- openstack-discuss - lists.openstack.org

openstack-nova-consoleauth/scheduler failed to start up
by Pete Zhang 19 Jul '21

19 Jul '21

We are installing openstack in a new DC and seeing openstack-nova-consoleauth/scheduler failed to start up. Checking log and found this. Host 10.160.4.5 is not allowed to connect to this MariaDB server. Three controller nodes are installed with MariaDB/Galera Cluster, none of them with this ip. -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

3 6

[kolla][wallaby] config drive vm fails live migration
by Ignazio Cassano 19 Jul '21

19 Jul '21

Hello All, I installed kolla wallaby with ubuntu source images. I have cinder installed, so live migration works but does not work with instances configured with config drive. Any help,please? Ignazio

1 1

[wallaby][neutron][ovn][vpnaas] Openstack VPNaaS with OVN Networking
by Malik Obaid 18 Jul '21

18 Jul '21

Hi, I am using Openstack Wallaby release on Ubuntu 20.04. I just want to know when openstack VPNaaS will be available with OVN networking. I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

1 0

[baremetal-sig][ironic] Tue July 13, 2021, 2pm UTC: Introduction to Bifrost
by Arne Wiebalck 18 Jul '21

18 Jul '21

Dear all, The Bare Metal SIG will meet tomorrow Tue July 13, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Julia Kreger (TheJulia): "Getting started with Ironic: Bifrost" Bifrost allows to install Ironic in standalone mode (without other OpenStack components) and is also often chosen as a starting point to get familiar Ironic. As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome, hope to see you there! Cheers, Arne

2 1

Fwd: [Kolla] [ Kolla-Ansible] Existing Workloads getting Impacted on Upgrade
by Anirudh Gupta 17 Jul '21

17 Jul '21

Hi Team, We have deployed the Openstack Victoria release using Multinode Kolla Ansible deployment. There are 2 nodes - one for compute and other for Controller+Network Following the below link, we also upgraded the setup from Victoria to wallaby https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html During the Upgrade process, we figured out that the VM which was spawned before Upgrade went to shut off during the middle of Upgrade process and post completion of the upgrade process, we had to manually start the VM again. Ideally we were expecting that the existing Workloads would remain unimpacted in this process. Can someone please suggest if our observation is correct or any steps that needs to be taken in order to avoid this? Regards Anirudh Gupta

4 4

[Kolla][wallaby] vpnaas
by Ignazio Cassano 17 Jul '21

17 Jul '21

Hello, I tried to enable vpnaas in my global.yml file with ubuntu source images but pull action does not download any vpnaas image. Must I switch to binary or centos image type? Regards Ignazio

2 2

[all][tc] What's happening in Technical Committee: summary 16th July, 21: Reading: 5 min
by Ghanshyam Mann 16 Jul '21

16 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Added Hashicorp Vault deployment repo under OpenStack-ansible project[1] * Proposed 'consistent and secure RBAC' as a community-wide goal[2] 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-15-15.00.log.html * We will have next week's meeting on July 22th, Thursday 15:00 UTC[3]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[4] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Six open reviews for ongoing activities[5]. ELK services next plan and help status --------------------------------------------- * We continue the discussion in the this week TC meeting, below is the summary: ** Help status: as of now, there are no volunteers to help. ** Clark announced the deadline (Yoga cycle end) on ML[6]. ** Clark checked the result by reducing the load on log worker as well as the ELK instance. ** Based on results, his current propose is to shrink log workers to 60% of their total size and reduce the elasticsearch cluster size by one instance. ** Before taking final decision, we will monitor the result during Xena release (when we have more load). Migration from Freenode to OFTC ----------------------------------------- * I started updating the remaining project side wiki/doc page, please review those. ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * I request to merge the current open patches ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * I am leaving the retired repo because 1. there are lot of retired repo[7] 2. it need to add gate setup in project-config to sync the change in github repo. * All the required work for this migration is tracked in this etherpad[8] Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[9], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Project updates: ------------------- * Retiring js-openstack-lib [10] * Properly retire neutron-lbaas[11] * Deprecate os-panko role [12] * Retire tripleo-common-tempest-plugin[13] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [14]. * Current status: One goal "Secure RBAC" is proposed. Other Changes ------------------ * Defining Yoga release testing runtime15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [18] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/799826 [2] https://review.opendev.org/c/openstack/governance/+/799705 [3] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [4] https://etherpad.opendev.org/p/tc-xena-tracker [5] https://review.opendev.org/q/project:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023578.html [7] https://opendev.org/openstack/governance/src/branch/master/reference/legacy… [8] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [10] https://review.opendev.org/c/openstack/governance/+/798540 [11] https://review.opendev.org/c/openstack/governance/+/800148 [12] https://review.opendev.org/c/openstack/governance/+/799817 [13] https://review.opendev.org/c/openstack/governance/+/800432 [14] https://etherpad.opendev.org/p/y-series-goals [15] https://review.opendev.org/c/openstack/governance/+/799927 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [18] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[manila][ptg] Yoga cycle Project Teams Gathering information
by Goutham Pacha Ravi 16 Jul '21

16 Jul '21

Hello Zorillas and other interested stackers, We've reserved some time-slots for the upcoming Virtual Project Teams Gathering [1]. Based on experience these timings have generally worked for us, albeit they're bound to be too early or too late in some time zones. We'll try to be accommodative and schedule additional meetings if you're interested but cannot make it at the designated time. Please use the PTG Planning Etherpad at [2] to add your IRC nicknames and topics you wish to bring up. As usual, we will record all our discussions and post minutes to this mailing list, as well as upload them [3]. Will post more information closer to the event! Thanks, Goutham [1] https://ethercalc.openstack.org/8tum5yl1bx43 [2] https://etherpad.opendev.org/p/yoga-ptg-manila-planning [3] https://www.youtube.com/channel/UCCnLeIR8V1Fl7ym1c7H3e0A

1 0

[manila][stable][release] Transitioning stable/queens and stable/rocky to eol and the fate of stable/stein
by Goutham Pacha Ravi 16 Jul '21

16 Jul '21

Hello zorillas, stable branch maintainers and operators, We've kept stable/queens and stable/rocky branches of manila, python-manilaclient and manila-ui around under extended maintenance for a while now. The coordinated Queens release was 2018-02-28 and the Rocky release was 2018-08-30. The last time a change was backported to these branches has been a while: - manila stable/queens: Jan 20, 2021 stable/rocky: Jan 18, 2021 - python-manilaclient stable/queens: Jul 6, 2021 (Oct 14, 2020 before that) stable/rocky: Oct 13, 2020 - manila-ui stable/queens: Jul 16, 2020 (already EOL'ed, see [4]) stable/rocky: Oct 16, 2019 CI jobs on the manila repo have been failing on these branches, and the team has no bandwidth to address them; we polled the community members and contributors during several IRC meetings as well as the Xena Project Teams Gathering, and there has been steadily reduced interest in needing these branches to be maintained. So, I'd like to request that these branches be moved to end-of-life. Any open changes on these branches for these repositories have been abandoned, and patches are posted [1][2][3][4] to create the EOL tags. Once the Xena cycle concludes, we would also like to transition stable/stein branches on these repositories and bid adieu to the last remnants of python2 testing in manila. Happy to answer any queries and appreciate your help in concluding this activity. Thanks! Goutham [1] https://review.opendev.org/c/openstack/releases/+/801141 (manila) [2] https://review.opendev.org/c/openstack/releases/+/801142 (python-manilaclient) [3] https://review.opendev.org/c/openstack/releases/+/801143 (manila-ui) - stable/rocky [4] https://review.opendev.org/c/openstack/releases/+/800963 (manila-ui) - stable/queens, merged

1 0

[cinder] new driver freeze exception for PowerStore NFS
by Brian Rosmaita 16 Jul '21

16 Jul '21

I'm granting a driver freeze exception to the Dell EMC PowerStore NFS driver: https://review.opendev.org/c/openstack/cinder/+/79760 The driver is mostly ready and the third-party CI is functioning. It could use one more round of reviews. To be included in the Xena release, the driver should be merged by 20:00 UTC on Friday, 23 July 2021. cheers, brian

1 0

[horizon][stable] [release] Proposal to make stable/queen as EOL
by vishal manchanda 16 Jul '21

16 Jul '21

Hi all, As discussed in the last horizon weekly meeting[1] on 2021-06-23, I would like to announce that the horizon team decided to make stable/queen branch as EOL. Consider this mail as an official announcement for that. I would like to know if anyone still would like to keep this branch to be open otherwise, I will purpose an EOL patch for this branch. Thanks & Regards, Vishal Manchanda [1] https://meetings.opendev.org/meetings/horizon/2021/horizon.2021-06-23-15.00…

3 4

Re: PXE setup in a VM created in Oracle VM virtual Box
by Adivya Singh 16 Jul '21

16 Jul '21

Hi Team, I am trying to install a Ubuntu PXE setup by creating a VM in Oracle Virtual Box Manager, and also using VM created by virsh With VM created by virsh , will it work, because i am unable to copy the Yaml File content inside Ubuntu Virtual Manager server even after following the article of enabling copy/paste I am also trying to find out a solution for getting a root password in encrypted format for yaml file I am trying to create a PXE setup in VM created in Oracle Vm Virtual Box, and i am following this link, is anything wrong or you want to add because it is not working https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 and this one i found latest https://askubuntu.com/questions/1235723/automated-20-04-server-installation… Regards Adivya Sing On Mon, Jul 12, 2021 at 10:07 PM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > Hi brian, > > I am trying to create a PXE setup in VM created in Oracle Vm Virtual Box, > and i am following this link, is anything wrong or you want to add because > it is not working > > https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 > > and this one i found latest > > https://askubuntu.com/questions/1235723/automated-20-04-server-installation… > > Regards > > Adivya Singh > > >

2 2

PowerDNS admin Configuration for making a bind server
by Adivya Singh 16 Jul '21

16 Jul '21

Hi Team, I am unable to create a install and Configure a PowerDNS admin on a Server, it installed Fine, but when i am trying to open the Link , it say "Page not Found error" it never shows any error while installation and Configuration, I am using a Setup in Canonical Open Stack where I am using Internal IP for Configuration, There is no Floating IP attached Regards Adivya Singh 9590986094

2 2

[release] Release countdown for week R-11, Jul 19 - Jul 23
by Herve Beraud 16 Jul '21

16 Jul '21

Development Focus ----------------- We are now past the Xena-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 19). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 2, 2021) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 2, 2021. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 16) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 27, 2021) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 19 (R-7 week) Client library freeze: September 2 (R-5 week) Xena-3 milestone: September 2 (R-5 week) Xena release: October 6 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[CloudKitty] Virtual PTG October 2021
by Rafael Weingärtner 16 Jul '21

16 Jul '21

Hello everyone, As you probably heard our next PTG will be held virtually in October. I've marked October 18, at 14:00-17:00 UTC [1]. We already have a CloudKitty meeting organized for this day. Therefore, it seems the most practical choice. However, if you guys would like some other dates and/or time, just let me know. The room I selected is called "Bexar". I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://ethercalc.openstack.org/8tum5yl1bx43 [2] https://etherpad.opendev.org/p/cloudkitty-ptg-xena -- Rafael Weingärtner

3 4

[nova] Milestone 2 - spec freeze
by Balazs Gibizer 16 Jul '21

16 Jul '21

Hi, Yesterday we hit Xena Milestone 2. This also means nova is now in a state of spec freeze. The Yoga spec directory already exists so specs that are not merged to Xena can be propose to Yoga already. I've updated the bp states in launchpad[1]. Please check your bps and let me know if I missed something or misunderstood the status of the implementation work. We have 20 open bps at the moment which is a lot. Please note that Milestone 3 and therefore feature freeze is 3rd of September, which is 7 weeks from now. I encourage all of you to prioritize reviewing implementation of the bps that are already in NeedsCodeReview state. Cheers, gibi [1] https://launchpad.net/nova/+milestone/xena-3

1 0

Setting bandwidth limit
by Felipe Mogollon 16 Jul '21

16 Jul '21

Hi, I am running openstack victoria installed using packstack. Everything things to be fine except bandwidth limit. I have tried to limit internal traffic between two instances and between instances and "Internet" but I always get maximum data transfer speed. I have set up following rules openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --ingress bw-choke openstack network qos rule create --type bandwidth-limit --max-kbps 3 --max-burst-kbits 2 --egress bw-choke and applied bw-choke policy to the internal network where my instances are deployed: openstack network set --qos-policy bw-choke newdeploylab_private_network and to ports where machines connect to subnet: openstack port set --qos-policy bw-choke 503a07b8-2da0-4abe-8251-ede648ba42b4 openstack port set --qos-policy bw-choke 776d5fb3-639c-47cc-9b0f-6ec855397df7 but nothing happens. Each time I try to download something from internet or copy data from an instance to another I always get maximum data transfer speed. I have followed instructions from https://docs.openstack.org/neutron/victoria/admin/config-qos.html Any ideas? -- <https://www.vicomtech.org> Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media <https://www.linkedin.com/company/vicomtech> <https://www.youtube.com/user/VICOMTech> <https://twitter.com/@Vicomtech> member of: <https://graphicsvision.ai/> La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

1 0

[all] Proposed Yoga cycle schedule
by Herve Beraud 16 Jul '21

16 Jul '21

Hey everyone, The Xena cycle is going by fast, and it's already time to start planning some of the early things for the Yoga release. One of the first steps for that is actually deciding on the release schedule. Typically we have done this based on when the next Summit event was planned to take place. Due to several reasons, we don't have a date yet for the first 2022 event. The current thinking is it will likely take place in May (nothing is set, just an educated guess, so please don't use that for any other planning). So for the sake of figuring out the release schedule, we are proposing one schedule targeting a release date at the end of March. Hopefully this will then align well with event plans. Here is the proposed schedule: https://review.opendev.org/c/openstack/releases/+/800663 Please feel free to comment on the patch if you see any major issues that we may have not considered. Thanks for your reading -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[neutron][vpnaas] Ok with V. not working with W.
by Franck VEDEL 16 Jul '21

16 Jul '21

Hello, i have been trying to fix a problem for over 2 weeks with no success so am looking for some help as my openstack is due to work in september (for my students). I need the vpnaas service. I'm doing a lab with centos / kolla-ansible / victoria ... vpnaas works, exactly what I need. I replace V with Wallaby. Exactly the same server, the same Centos, I just change V to W in the configuation file. Everything works except Vpnaas. I have a new server, and for some reason I can't have Victoria (issue with horizon that I don't understand). I'm trying Wallaby. Everything works perfectly except Vpnaas. Why ? It's incomprehensible. A bug ? The error message (neutron-l3-agent.log): Command: ['mount', '--bind', '/var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run', '/var/run'] Exit code: 0 Stdout: Stderr: 2021-07-16 12:03:57.089 281941 INFO neutron_vpnaas.services.vpn.common.netns_wrapper [-] /var/lib/neutron/ipsec/8b987595-47be-45cc-95f5-3b70d24f4976/var/run has been bind-mounted in /var/run Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl ») Can this be a bug? I do exactly the same things, the same configurations? How to find the problem? Does anyone have a working Oopenstack Wallaby with Centos and Vpnaas? Meci in advance for your help. Franck http://www.rtgrenoble.fr <http://www.rtgrenoble.fr/>

1 0

[kolla] Ceph client version in Kolla 12.0.0 Wallaby and ubuntu containers
by J-P Methot 16 Jul '21

16 Jul '21

Hi, We've been using Kolla to provision a production cluster and we've noticed that the ceph-client version provided in the Kolla images is severely outdated as it doesn't support the fix to CVE-2021-20288 that was added in Pacific 16.2.1 (installed version in image is 16.2.0). As a result, the installed ceph-client can't connect to ceph clusters where the patch is active. Is there any Kolla image where more recent versions of ceph-client is installed? How would I be able to get them? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4

[nova] [magnum] Flavor names vs IDs
by Krzysztof Klimonda 15 Jul '21

15 Jul '21

Hi, Flavors have both names ands IDs and both can be set during creation - what is the background for having both being separate from each other? I'm asking this because magnum uses flavor id for it's "instance-type" node annotation (which is understandable) and by default flavor ID is an autogenerated UUID. Would there be any downside to always matching flavor id and name when creating flavors? Best Regards, Krzysztof -- Krzysztof Klimonda kklimonda(a)syntaxhighlighted.com

1 0

[kolla] multiple ceph backends
by J-P Methot 15 Jul '21

15 Jul '21

Hi, I'm progressing in figuring out Kolla and I've hit another issue. On our regular setups, we happen to be using multiple Ceph backends in cinder. Each of those backend uses a differently named ceph config file (like ceph.conf and ceph-rep.conf). While adding a custom configuration to cinder.conf is pretty easy, what's the best way to ensure that my second ceph config file ends up in my containers at the correct path? I've considered using ansible to add the file after kolla has deployed but I doubt this would be permanent. -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

2 1

[TripleO] next irc meeting Tuesday 20 July @ 1400 UTC in OFTC #tripleo
by Marios Andreou 15 Jul '21

15 Jul '21

Reminder the next TripleO irc meeting is this coming Tuesday 20 July 1400 UTC in OFTC irc channel #tripleo. agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (feel free to add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Jul 6 - you can find logs @ http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-07-06-14.… Hope you can make it on Tuesday, regards, marios

1 0

[horizon] [plugins] [heat-dashboard] [murano-dashboard] Drop nodejs10 Support
by vishal manchanda 15 Jul '21

15 Jul '21

Hello Everyone, As you may have noticed I have pushed a series of patches[1] in the last few months to drop nodejs10 support from our gate job because nodejs10 is already EOL. All horizon plugins and horizon moved to nodejs14 which is the current LTS version also runtime for the Xena release[2]. Next Step is to drop nodejs10 support, only two horizon plugins left that still run nodejs10 job i.e openstack/heat-dashboard and opensatck/murano-dashboard. So I would request to heat and murano core team to approve open patches for the same [3], [4] and then we can finally drop it from the horizon. Thanks to all for taking this as the priority and quick approvals on the patches. In case of any issue, please feel free to reach out to Horizon channel #openstack-horizon. Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/q/topic:%22drop-nodejs10%22+(status:open%20OR%20… [2] https://governance.openstack.org/tc/reference/runtimes/xena.html#node-js-ru… [3] https://review.opendev.org/c/openstack/heat-dashboard/+/792201 [4] https://review.opendev.org/c/openstack/murano-dashboard/+/792207

1 0

Re: Cinder error while creating Volumes in Openstack
by Adivya Singh 15 Jul '21

15 Jul '21

Hello Team, I am getting the above error, while attaching volumes, My volume service list are up and running. also my rabbitmq services are fine, any other suggestion we can check, we use qnap as storage Regards Adivya Singh On Wed, Jul 14, 2021 at 7:30 PM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > Hi Eugen, > > Please find the error logs which i am getting, particular during attaching > a instance to a Instance > > Jul 14 13:54:17 c1w-cinder-volumes-container-aa023a91 > cinder-volume[38100]: 2021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server [req-7ec417bc-0692-4766-8513-86a979c23e07 > 4441034aeea2551710631bc8fe381b1094c260e64501c736bfa51987aaefd7cc > 4e1398294816433bab5f3cebb2210788 - f7834cb0083b4f8f81184b6595b46b34 > f7834cb0083b4f8f81184b6595b46b34] Exception during message handling: > ParseError: no element found: line 20, column 0#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server Traceback (most recent call > last):#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", > line 166, in _process_incoming#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server res = > self.dispatcher.dispatch(message)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 265, in dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, > ctxt, args)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 194, in _do_dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server result = func(ctxt, **new_args)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4420, in attachment_update#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server connector)#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4348, in _connection_create#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server volume, connector)#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", > line 274, in inner#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return f(*args, **kwargs)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 853, in create_export#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server self._get_portal_info(volume, connector, > lun_slot_id, lun_owner))#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 706, in _get_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server ret = > self.api_executor.get_iscsi_portal_info()#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1109, in inner_connection_checker#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server return func(self, *args, > **kwargs)#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1520, in get_iscsi_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server root = > ET.fromstring(res_details['data'])#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/defusedxml/common.py", > line 118, in fromstring#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return parser.close()#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1671, in > close#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > self._raiseerror(v)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in > _raiseerror#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server raise err#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server ParseError: no element found: line 20, > column 0#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > > Regards > Adivya Singh > 9590986094 > > On Wed, Jul 14, 2021 at 1:29 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> those are only INFO logs, they don't show anything related to errors >> you're experiencing. >> >> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> >> > Hi Team, >> > >> > any input on this, Logs are attached >> > >> > Regards >> > Adivya Singh >> > >> > >> > ---------- Forwarded message --------- >> > From: Adivya Singh <adivya1.singh(a)gmail.com> >> > Date: Mon, Jul 12, 2021 at 9:58 PM >> > Subject: Re: Cinder error while creating Volumes in Openstack >> > To: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> >> > >> > >> > hi Brian, >> > >> > Thanks for your response, I am attaching the logs hereby. >> > >> > Earlier we were able to create the cinder volumes and delete , but >> unable >> > to attach, but now even create and delete not working >> > >> > Regards >> > Adivya Singh >> > >> > On Mon, Jul 12, 2021 at 9:31 PM Brian Rosmaita < >> rosmaita.fossdev(a)gmail.com> >> > wrote: >> > >> >> On 7/12/21 11:20 AM, Adivya Singh wrote: >> >> > Hello Team, >> >> > >> >> > i am seeing the below error, while creating volumes in cinder log, >> Any >> >> > solution or fix for these error, as of now i am not able to create >> >> > volumes, neither i am unable to delete, it just sits in hung state >> >> > >> >> > DISTRIB_RELEASE="18.1.9" >> >> > DISTRIB_CODENAME="Rocky" >> >> > DISTRIB_DESCRIPTION="OpenStack-Ansible" >> >> >> >> Hello Adivya, >> >> >> >> I think you forgot to include the error? If your log extracts are >> long, >> >> you can post them in http://paste.openstack.org/ and send the links to >> >> this mailing list. (Don't forget to scrub any sensitive info first.) >> >> >> >> > >> >> > Regards >> >> > Adivya Singh >> >> > >> >> >> >> >> >> >> >> >> >> >>

4 3

[all] Request to fix the warning to reduce the log size
by Ghanshyam Mann 14 Jul '21

14 Jul '21

Hello Everyone, As you might have noticed the discussion in infra channel, log size are increasing a lot and one of the main reasons is warnings (especially repeatedly warnings). Few of them are from oslo policy on new policy and DeprecdatedRule. However, those are not the only warnings, there are lot from other lib also. Before we start facing more issues in logging system and indexing, we would request all the project team to start looking at the logs and fix the warnings as much as possible. I started fixing few of the oslo policy warning on DeprecatedRule in applicable projects and once all patches are merged, we can convert them to error from oslo side to avoid any future warnings- https://review.opendev.org/q/topic:%22fix-oslo-policy-warnings%22+(status:o… [1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html#… -gmann

4 4

[all][tc] Technical Committee next weekly meeting on July 15th at 1500 UTC
by Ghanshyam Mann 14 Jul '21

14 Jul '21

Hello Everyone, Below is the agenda for Tomorrow's TC meeting schedule at 1500 UTC in #openstack-tc IRC OFTC channel. -https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting == Agenda for tomorrow's TC meeting == * Roll call * Follow up on past action items * Gate health check (dansmith/yoctozepto) ** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/ * Migration from 'Freenode' to 'OFTC' (gmann) ** https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc * PTG Planning ** Doodle poll for slot selection. *** https://doodle.com/poll/6dfdmdfi4s8wc7cd * PTG Etherpad ** https://etherpad.opendev.org/p/tc-yoga-ptg * ELK services plan and help status * Help status * Reducing the size of the existing system ** One concern is this service represents an outsized slice of our resources. ** We are investigating if it is possible to slim this down a bit given the current inputs/demands on the system. * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[ci] zuul nodes
by Adrian D. Popescu 14 Jul '21

14 Jul '21

Hi, Is there a comprehensive listing of the nodes available for use in Zuul CI? I looked through the listing here: https://zuul.opendev.org/t/openstack/nodes not sure if that list is complete? More specifically I'm trying to find out if any s390x nodes exist. Signs point to no, but I'm just trying to be sure. Also, assuming there aren't any, how would someone go about adding more nodes if possible? Thank you, -Adrian

2 1

[horizon] Yoga PTG Planning
by vishal manchanda 14 Jul '21

14 Jul '21

Hello Everyone, As you may already know that Yoga Cycle PTG will be held between 18th-22nd October[1]. I have created a doodle poll [2] to select the time which works best for our team. Please try to fill it asap as the deadline to book the slot is 21st July. I have also created an etherpad [3] to collect the topics for discussion. Feel free to add your topics which you would like to discuss in the PTG. Thanks & Regards, Vishal Manchanda [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html [2] https://doodle.com/poll/7vxwprypskrhidhq [3] https://etherpad.opendev.org/p/horizon-yoga-ptg

1 0

Manage network quotas from Horizon
by Derek O keeffe 14 Jul '21

14 Jul '21

Hi all, Is there a way to enable the admin to edit network quotas from horizon? I can edit volume and compute but not network. Thanks in advance for any info. Regards,Derek

1 0

Take care when deleting email addresses in Gerrit
by Clark Boylan 14 Jul '21

14 Jul '21

Hello everyone, We have discovered a bug in Gerrit [0] that allows you to delete your account's Ubuntu One OpenID association if you delete the email from your account associated with that OpenID. When you do this the next time you log in Gerrit will create a new account for you. Fixing this after the fact is currently difficult. We are working to correct this but the required corrections take time. We would like to avoid these issues in the first place. Please avoid deleting email addresses from your accounts unless you are sure they are not associated with your OpenID. If you would like help double checking that for you please let us know and one of our Gerrit admins can double check. We are working to make this fixable after the fact, and will try to work with the Gerrit upstream to prevent you from deleting Ubuntu One OpenID associations from your account in the first place. Until then we apologize for the inconvenience. Finally, this message and others like it are sent to service-announce(a)lists.opendev.org. I am sending this email to a much broader set of mailing lists because the service-announce list membership is quite small. All of our users should be subscribed to that list to get important notices like this one. We keep the traffic low and only send mail there when we feel it is important for you to see it. [0] https://bugs.chromium.org/p/gerrit/issues/detail?id=14776 Clark

1 0

[cinder] Bug deputy report for week of 2021-14-07
by Sofia Enriquez 14 Jul '21

14 Jul '21

Hello, This is a bug report from 2021-07-07 to 2021-14-07. You're welcome to join the Cinder Bug Meeting today. Weekly on Wednesday at 1500 UTC on #openstack-cinder Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1935981 "Available volume status with attachments". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1935649 "Retyping an attached MA volume while attached to more than one instance should either be fixed, blocked or documented as a limitation". Assigned to Rajat Dhasmana. - https://bugs.launchpad.net/cinder/+bug/1934905 "[cinder-backup] Backup is not possible from backends different from ceph". Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1935057 "Delete attachment doesn't fail on remove_export errors". Assigned to Gorka Eguileor. - https://bugs.launchpad.net/cinder/+bug/1935011 "Deleting a reserved snapshot is missing detach.start notificacion".i Assigned to Gorka Eguileor. Low - https://bugs.launchpad.net/cinder/+bug/1935989 "Prophetstor driver not compatible with python 3.9". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1935670 "SVC _update_replication_properties for empty values". Unassigned. Cheers, Sofia -- L. 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

Re: Cinder error while creating Volumes in Openstack
by Eugen Block 14 Jul '21

14 Jul '21

Hi, it seems as if there's something wrong with rabbitmq, check its health status. What does 'openstack volume service list' return? Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: > Hi Eugen, > > Please find the error logs which i am getting, particular during attaching > a instance to a Instance > > Jul 14 13:54:17 c1w-cinder-volumes-container-aa023a91 cinder-volume[38100]: > 2021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > [req-7ec417bc-0692-4766-8513-86a979c23e07 > 4441034aeea2551710631bc8fe381b1094c260e64501c736bfa51987aaefd7cc > 4e1398294816433bab5f3cebb2210788 - f7834cb0083b4f8f81184b6595b46b34 > f7834cb0083b4f8f81184b6595b46b34] Exception during message handling: > ParseError: no element found: line 20, column 0#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server Traceback (most recent call > last):#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", > line 166, in _process_incoming#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server res = > self.dispatcher.dispatch(message)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 265, in dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, > ctxt, args)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", > line 194, in _do_dispatch#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server result = func(ctxt, **new_args)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4420, in attachment_update#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server connector)#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/manager.py", > line 4348, in _connection_create#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server volume, connector)#0122021-07-14 13:54:17.246 > 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", > line 274, in inner#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return f(*args, **kwargs)#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 853, in create_export#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server self._get_portal_info(volume, connector, > lun_slot_id, lun_owner))#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 706, in _get_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server ret = > self.api_executor.get_iscsi_portal_info()#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1109, in inner_connection_checker#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server return func(self, *args, > **kwargs)#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/cinder/volume/drivers/qnap.py", > line 1520, in get_iscsi_portal_info#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server root = > ET.fromstring(res_details['data'])#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/openstack/venvs/cinder-18.1.9/lib/python2.7/site-packages/defusedxml/common.py", > line 118, in fromstring#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server return parser.close()#0122021-07-14 > 13:54:17.246 38100 ERROR oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1671, in > close#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > self._raiseerror(v)#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server File > "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in > _raiseerror#0122021-07-14 13:54:17.246 38100 ERROR > oslo_messaging.rpc.server raise err#0122021-07-14 13:54:17.246 38100 > ERROR oslo_messaging.rpc.server ParseError: no element found: line 20, > column 0#0122021-07-14 13:54:17.246 38100 ERROR oslo_messaging.rpc.server > > Regards > Adivya Singh > 9590986094 > > On Wed, Jul 14, 2021 at 1:29 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> those are only INFO logs, they don't show anything related to errors >> you're experiencing. >> >> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> >> > Hi Team, >> > >> > any input on this, Logs are attached >> > >> > Regards >> > Adivya Singh >> > >> > >> > ---------- Forwarded message --------- >> > From: Adivya Singh <adivya1.singh(a)gmail.com> >> > Date: Mon, Jul 12, 2021 at 9:58 PM >> > Subject: Re: Cinder error while creating Volumes in Openstack >> > To: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> >> > >> > >> > hi Brian, >> > >> > Thanks for your response, I am attaching the logs hereby. >> > >> > Earlier we were able to create the cinder volumes and delete , but unable >> > to attach, but now even create and delete not working >> > >> > Regards >> > Adivya Singh >> > >> > On Mon, Jul 12, 2021 at 9:31 PM Brian Rosmaita < >> rosmaita.fossdev(a)gmail.com> >> > wrote: >> > >> >> On 7/12/21 11:20 AM, Adivya Singh wrote: >> >> > Hello Team, >> >> > >> >> > i am seeing the below error, while creating volumes in cinder log, Any >> >> > solution or fix for these error, as of now i am not able to create >> >> > volumes, neither i am unable to delete, it just sits in hung state >> >> > >> >> > DISTRIB_RELEASE="18.1.9" >> >> > DISTRIB_CODENAME="Rocky" >> >> > DISTRIB_DESCRIPTION="OpenStack-Ansible" >> >> >> >> Hello Adivya, >> >> >> >> I think you forgot to include the error? If your log extracts are long, >> >> you can post them in http://paste.openstack.org/ and send the links to >> >> this mailing list. (Don't forget to scrub any sensitive info first.) >> >> >> >> > >> >> > Regards >> >> > Adivya Singh >> >> > >> >> >> >> >> >> >> >> >> >> >>

1 0

[openstack-victoria] [horizon] issue when installing openstack dashboard Module not found
by Swogat Pradhan 14 Jul '21

14 Jul '21

Hi, I am trying to install openstack dashboard but am getting an error stating ModuleNotFoundError: No module named 'horizon.xstatic'. Can someone suggest a way forward for this? *lsb_release -rd:* Description: Ubuntu 20.04.2 LTS Release: 20.04 *apt-cache policy openstack-dashboard:* openstack-dashboard: Installed: 4:18.6.2-0ubuntu1~cloud0 Candidate: 4:18.6.2-0ubuntu1~cloud0 Version table: *** 4:18.6.2-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu focal-updates/victoria/main amd64 Packages 100 /var/lib/dpkg/status 3:18.3.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3:18.3.2-0ubuntu0.20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3:18.2.1~git2020041013.754804667-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages With regards, Swogat Pradhan

1 1

Fwd: Cinder error while creating Volumes in Openstack
by Adivya Singh 14 Jul '21

14 Jul '21

Hi Team, any input on this, Logs are attached Regards Adivya Singh ---------- Forwarded message --------- From: Adivya Singh <adivya1.singh(a)gmail.com> Date: Mon, Jul 12, 2021 at 9:58 PM Subject: Re: Cinder error while creating Volumes in Openstack To: Brian Rosmaita <rosmaita.fossdev(a)gmail.com> hi Brian, Thanks for your response, I am attaching the logs hereby. Earlier we were able to create the cinder volumes and delete , but unable to attach, but now even create and delete not working Regards Adivya Singh On Mon, Jul 12, 2021 at 9:31 PM Brian Rosmaita <rosmaita.fossdev(a)gmail.com> wrote: > On 7/12/21 11:20 AM, Adivya Singh wrote: > > Hello Team, > > > > i am seeing the below error, while creating volumes in cinder log, Any > > solution or fix for these error, as of now i am not able to create > > volumes, neither i am unable to delete, it just sits in hung state > > > > DISTRIB_RELEASE="18.1.9" > > DISTRIB_CODENAME="Rocky" > > DISTRIB_DESCRIPTION="OpenStack-Ansible" > > Hello Adivya, > > I think you forgot to include the error? If your log extracts are long, > you can post them in http://paste.openstack.org/ and send the links to > this mailing list. (Don't forget to scrub any sensitive info first.) > > > > > Regards > > Adivya Singh > > > > >

2 1

[tripleo][ci] ussuri promoted, mirrors not synced yet..
by Wesley Hayutin 13 Jul '21

13 Jul '21

FYI.. Jobs running against ussuri or victoria-upgrade jobs may fail atm. The branch promoted and the mirrors are not yet synced up. Some details: http://paste.openstack.org/show/807451/

1 0

Re: [devstack][neutron][manila] Instances having trouble getting to external network with OVN
by Simon Dodsley 13 Jul '21

13 Jul '21

To follow on from this. This is a link to an example CI failure: http://openstack-logs.purestorage.com/84/789384/25/thirdparty-check/pure-de… Thanks Simon | *Simon Dodsley MBCS CITP* | Technical Director, New Stack | Global Cloud Architecture Organization | Pure Storage, Inc. | +1 (510) 516-2682 | simon(a)purestorage.com | www.purestorage.com *BOOK TIME WITH ME*: 30 minutes <https://purestorage.chilipiper.com/book/me/simon-dodsley?type=my-meeting> [image: http://www.purestorage.com/_media/header_logo.png?130529]

1 0

review.opendev.org server upgrade 18/19th July 2021
by Ian Wienand 13 Jul '21

13 Jul '21

Hello, Around 2021-07-18 23:00 UTC we plan to provision an upgrade to the review.opendev.org server which hosts our Gerrit instance. We are aware that some users may require firewall updates or similar to access the new server. The new addresses will be: 199.204.45.33 2604:e100:1:0:f816:3eff:fe52:22de We hope the downtime will be limited to a few hours as we migrate and index the data. User-visible changes be should minimal. Due to incompatible schemas between the old hosted database and new database instance we will not be transitioning the table that holds the information about what files you have reviewed (gerrit shows a light-grey "Reviewed" when you have viewed a file). Note this is *not* review comments or code, but just the per-user flag in the UI if you have viewed a file. You can reach admins via email at service-discuss(a)lists.opendev.org or in OFTC #opendev for any further questions or queries. Thank you, -i

1 1

[glance] Yoga PTG Planning
by Abhishek Kekane 13 Jul '21

13 Jul '21

Hello Everyone!!! As you are already aware that Yoga virtual PTG will be held between October 18th to 22nd [1]. Please use below etherpad to add the topics you would like to discuss during PTG. https://etherpad.opendev.org/p/yoga-ptg-glance-planning [1] https://www.eventbrite.com/e/project-teams-gathering-october-2021-tickets-1… Thanks & Best Regards, Abhishek Kekane

1 0

[cinder] yoga virtual PTG timeslots
by Brian Rosmaita 13 Jul '21

13 Jul '21

Hello Cinder team and anyone interested in Cinder development, It's time to determine when we will be meeting for the Yoga PTG, which takes place 18-22 October. We are asked to schedule within the following 3 blocks of 4 hours each: - 14:00-08:00 UTC - 13:00-17:00 UTC - 21:00-01:00 UTC with the following constraints: - no project should schedule more than 4 hours in a single day - no project should schedule more than 16 hours over the entire PTG Given the current cinder-core team's distribution across time zones, it looks to me like the best bet is to use (as we have for the past few Virtual PTGs) the 13:00-17:00 UTC time slot. So I propose that the cinder team meet 13:00-17:00 UTC on the four days Tuesday 19 October through Friday 22 October 2021. We'll schedule topics from 13:00-16:00 UTC, with 16:00-17:00 available for slack space for discussion overruns or happy hour. Take a look at this etherpad to see how the time slots fall across cinder contributor time zones: https://etherpad.opendev.org/p/yoga-ptg-cinder-timeslots If you have a topic you want to discuss at the PTG and the proposed timeslots do not work for you, please contact me immediately and let me know both (a) what you want to discuss, and (b) what timeslot you propose, and I'll try to work something out (which could include a post-PTG video meeting when we're not constrained by the PTG time blocks). By "immediately" I mean "before Monday 19 July at 12:00 UTC". cheers, brian

1 0

[nova][stable] Adding nova-core to nova stable branches
by Stephen Finucane 13 Jul '21

13 Jul '21

Happy Friday (again), Following on from my earlier email regarding os-vif stable branch permissions, I'd like to once again propose that we add nova-core to the list of teams with +2 rights on nova stable branches. Unlike the os-vif change, this has been discussed extensively in the past, most recently during the Victoria PTG [1] (search for "Can we add nova-core to nova-stable-maint") and therefore carries a little more baggage with it. Last time we discussed this, there were concerns from some existing stable cores that not all of nova-core were sufficiently well acquainted with stable branch policy and it was suggested that review velocity was sufficient. However, the stable team has remained pretty stable (heh) over the last couple of cycles and is staffed with developers with ample experience of both nova itself and the backport policies of nova and OpenStack as a whole. In addition, we continue to have a long tail of open stable reviews [2] from various people. The stable branches are increasingly important for users and organizations alike, and a faster, smoother backport policy encourages people to have an upstream-first mentality when it comes to maintaining a product built on these branches. The alternative is to handle these backports in a downstream-first or downstream- only manner, which results in duplication of effort and, over the long-term, potential difficulties keeping downstream and upstream in-sync. I think the time has long since passed where we should remove the artificial barrier that exists here. I expect all nova cores will have the maturity and sensibility to ask questions where uncertainty exists and only approve backports that they are confident and knowledgeable about. I do not expect existing stable cores will be sidelined either. Far from it, in fact. Existing stable cores will continue to be valuable both for their reviews and knowledge of the intricacies of stable policy. I proposed a waiting period of one week before making changes to os-vif permissions, but given the history around changes to nova stable core, I think we would benefit from some additional time to assuage any concerns that may still exist. I propose that we come to a decision by 09-Aug, or two weeks from now. If necessary, we can discuss this in real-time during the nova team meeting next Tuesday. Cheers, Stephen [1] https://etherpad.opendev.org/p/nova-victoria-ptg [2] https://review.opendev.org/q/project:openstack/nova+NOT+branch:master+is:op…

2 2

[cinder] festival of XS reviews 16 July 2021
by Brian Rosmaita 13 Jul '21

13 Jul '21

Hello Cinder community members, This is a reminder that the most recent edition of the Cinder Festival of XS Reviews will be held at the end of this week on Friday 16 July. who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 16 July 2021 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews This recurring meeting can be placed on your calendar by using this handy ICS file: http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics See you there! brian

1 0

How to use masked_set_action?
by taoyunupt 13 Jul '21

13 Jul '21

Hi, I found some info from vswitch.xml，it says "Masked data can improve performance by allowing megaflows to match on fewer fields." I do not know What kinds of flow atcion will use 'masked_set_action'. Can you give some demo flows and situation？ Thanks, YUN

1 0

[oslo] next meeting (July 19) canceled - PTO
by Herve Beraud 13 Jul '21

13 Jul '21

Hello Osloers, I'll be on PTO during the next 2 weeks, from July 19 to August 2, so I won't be around to run our meetings. If someone else is a volunteer to lead the meeting then feel free to run it. Thanks for your understanding. See you soon. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[neutron] WSREP: referenced FK check fail: Lock wait index
by Michal Arbet 13 Jul '21

13 Jul '21

Hi, I have wallaby deployed via kolla-ansible and from time to time see this in mariadb log while i'm running tempest tests against wallaby: /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:09:17 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:10:02 841 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:10:13 836 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:10:37 841 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:13:29 813 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:13:37 854 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:16:45 845 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:25:41 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`portsecuritybindings` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:26:30 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:27:14 827 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:27:38 866 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:28:28 846 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:29:27 840 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` /var/log/kolla/mariadb/mariadb.log:2021-07-13 9:43:39 842 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` I found some info in openstack-discuss below : http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014928.html So, it seems it is mariadb issue, but it should be fixed in version which I am using root@controller0:/home/ubuntu# docker exec -itu root mariadb bash (mariadb)[root@controller0 /]# dpkg -l | grep mariadb ii libmariadb3:amd64 1:10.5.10-2 amd64 MariaDB database client library ii mariadb-backup 1:10.5.10-2 amd64 Backup tool for MariaDB server ii mariadb-client 1:10.5.10-2 all MariaDB database client (metapackage depending on the latest version) ii mariadb-client-10.5 1:10.5.10-2 amd64 MariaDB database client binaries ii mariadb-client-core-10.5 1:10.5.10-2 amd64 MariaDB database core client binaries ii mariadb-common 1:10.5.10-2 all MariaDB common configuration files ii mariadb-server 1:10.5.10-2 all MariaDB database server (metapackage depending on the latest version) ii mariadb-server-10.5 1:10.5.10-2 amd64 MariaDB database server binaries ii mariadb-server-core-10.5 1:10.5.10-2 amd64 MariaDB database core server files So, is it really mariadb issue or neutron ? No similar log from other services in mariadb log. Thanks, Michal Arbet (kevko) Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

[Kolla] [Kayobe] Is Kayobe release dependent on Kolla-Ansible Release
by Anirudh Gupta 13 Jul '21

13 Jul '21

Hi Team, Whenever a new version of openstack is released in the market, Kayobe also updates its release accordingly. I was going through the installation guide and found Kayobe is dependent on Kolla-Ansible as well. The link https://docs.openstack.org/kayobe/latest/contributor/releases.html suggests that kayobe needs to Synchronise with Kolla Ansible feature flags Synchronise with Kolla Ansible inventory¶ <https://docs.openstack.org/kayobe/latest/contributor/releases.html#synchron…> So in case openstack releases it's newer version, does kayobe wait for kolla-ansible to update to the new release and then starts upgrading its release? Regards Anirudh Gupta

2 3

[Openstack][kolla] updates check
by Ignazio Cassano 13 Jul '21

13 Jul '21

Hello, I am new user for openstack kolla because I installed openstack writing my ansible Playbooks. I wonder if it is a method to check if new images has been released . For example: I installed kolla wallaby 2 weeks ago, and now I want to check if new images could be updated. I want to check if new images solve some bugs. Is it possibile without trying to pull all images.? Thanks Ignazio

3 6

[docs][openstackdocstheme][oslo] - can deprecated-badge-container be added to the pre-pike docs
by Walsh, Helen 12 Jul '21

12 Jul '21

Hi all, Pike seems to be the first project to have a notification of its current support status https://docs.openstack.org/cinder/pike/drivers.html This is in extended maintenance and not the current release. The current supported release is Wallaby.<https://docs.openstack.org/wallaby/> Is there any way to get a similar status for Ocata and Newton e.g. This project is End of Life and not the current release. The current supported release is Wallaby.<https://docs.openstack.org/wallaby/> https://docs.openstack.org/ocata/config-reference/dashboard.html https://docs.openstack.org/newton/config-reference/dashboard.html Kind regards, Helen

2 1

[cinder][stable] proposing Rajat Dhasmana for cinder-stable-maint team
by Brian Rosmaita 12 Jul '21

12 Jul '21

Rajat Dhasmana (whoami-rajat on IRC) has been organizing the cinder project's stable releases for a while now, and has also been active reviewing backports. He has a good understanding of the OpenStack stable maintenance policy and has been a reliable cinder core reviewer since January 2019. I hereby propose that he be included as a member of the cinder-stable-maint team. cheers, brian

7 8

[all][tc] Technical Committee next weekly meeting on July 15th at 1500 UTC
by Ghanshyam Mann 12 Jul '21

12 Jul '21

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

1 0