- openstack-discuss - lists.openstack.org

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

[tripleo][ci] master is promoting
by Wesley Hayutin 12 Jul '21

12 Jul '21

FYI... Heads up, master is promoting. If you see master jobs failing in a few hours, it may be due to the proxies ttl and sync. You can double check them w/ this WIP patch https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/34441/2/ci-scripts/…

1 0

[cinder] Block Storage API v2 removal
by Brian Rosmaita 12 Jul '21

12 Jul '21

Cinder community members, especially cinder-core: First, thanks to Rajat, who has reviewed this patch carefully, as evidenced by his 32 comments on patch set 4 and his re-review of patch set 6. We need to get https://review.opendev.org/c/openstack/cinder/+/792299/ reviewed and merged. It's holding up some feature work, as people rightly don't want to touch v2 if it's going to be removed, but aren't sure how serious we are that there will be no v2 in the Xena release, so they're not sure what to submit. The v2 API has been deprecated since Pike [0], and at this point it looks like all consuming projects have switched to using v3. But we need to get this change merged and released now at M-2 so we can discover whether there's anything we missed while it's still relatively early in the cycle. So please look at https://review.opendev.org/c/openstack/cinder/+/792299/ . If you are pressed for time, be creative and make a deal with another reviewer or two so that each of you reivews half (or a third, or whatever). But it's important that this be reviewed now! cheers, brian [0] https://docs.openstack.org/releasenotes/cinder/pike.html#deprecation-notes

1 0

[OSSA-2021-001] Neutron: Anti-spoofing bypass for Open vSwitch networks (CVE-2021-20267)
by Jeremy Stanley 12 Jul '21

12 Jul '21

============================================================= OSSA-2021-001: Anti-spoofing bypass for Open vSwitch networks ============================================================= :Date: July 12, 2021 :CVE: CVE-2021-20267 Affects ~~~~~~~ - Neutron: <16.3.3, >=17.0.0 <17.1.3, =18.0.0 Description ~~~~~~~~~~~ David Sinquin with Gandi.net reported a vulnerability in Neutron's default Open vSwitch firewall rules. By sending carefully crafted packets, anyone in control of a server instance connected to the virtual switch can impersonate the IPv6 addresses of other systems on the network, resulting in denial of service or in some cases possibly interception of traffic intended for other destinations. Only deployments using the Open vSwitch driver are affected. Patches ~~~~~~~ - https://review.opendev.org/777873 (Queens) - https://review.opendev.org/791470 (Queens) - https://review.opendev.org/777786 (Rocky) - https://review.opendev.org/791469 (Rocky) - https://review.opendev.org/777872 (Stein) - https://review.opendev.org/791500 (Stein) - https://review.opendev.org/777785 (Train) - https://review.opendev.org/791468 (Train) - https://review.opendev.org/777784 (Ussuri) - https://review.opendev.org/791467 (Ussuri) - https://review.opendev.org/777783 (Victoria) - https://review.opendev.org/791465 (Victoria) - https://review.opendev.org/776599 (Wallaby) - https://review.opendev.org/791464 (Wallaby) - https://review.opendev.org/783743 (Xena) Credits ~~~~~~~ - David Sinquin from Gandi.net (CVE-2021-20267) References ~~~~~~~~~~ - https://launchpad.net/bugs/1902917 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20267 Notes ~~~~~ - The stable/train, stable/stein, stable/rocky, and stable/queens branches are under extended maintenance and will receive no new point releases, but patches for them are provided as a courtesy. -- Jeremy Stanley

1 0

placement service issue (placement-status upgrade check failure)
by Deepak Mohanty 12 Jul '21

12 Jul '21

I need your help with installation of placement service on Ubuntu 20.04. I have followed the steps in: https://docs.openstack.org/placement/wallaby/install/install-ubuntu.html I am facing the following issue when I try to verify the installation: $ placement-status upgrade check Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/oslo_upgradecheck/upgradecheck.py", line 196, in run return conf.command.action_fn() File "/usr/lib/python3/dist-packages/oslo_upgradecheck/upgradecheck.py", line 104, in check result = func_name(self, **kwargs) File "/usr/lib/python3/dist-packages/oslo_upgradecheck/common_checks.py", line 41, in check_policy_json policy_path = conf.find_file(conf.oslo_policy.policy_file) File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2543, in find_file raise NotInitializedError() oslo_config.cfg.NotInitializedError: call expression on parser has not been invoked I did a bit of debugging and found that the policy file is: policy.json. I could not find any policy.json on my machine. I created an empty policy.json at: /etc/placement/policy.json (user and group = placement). That too did not work. I have followed the steps in the install guide twice, deleting the placement database and other resources and recreating them. I continue to see the same issue. Thank you for your time.

5 6

[ patrole ] Understanding RBAC Permission Exceptions
by darumaseye 12 Jul '21

12 Jul '21

Hello, I am a researcher studying security of the Openstack's Policies. I'm very interested in the Patrole project and I would like to ask you some questions. In the documentation it is stated that Patrole compares two different types of results: - an expected one ( derived from oslo.policy ) - an actual one ( derived from an actual request to the API ). Given that, Patrole's tests can return 3 different values: 1) "Success" if actual result and expected result are both True or both False; 2) "RbacOverPermissionException" if actual result is True but expected result is False; 3) "RbacUnderPermissionException" in the other case. I can't understand in which cases the tests can return a value different from "Success". As far as I know, an API call should always be validated internally by oslo.policy's rules, before being allowed. So, in order for an API call to be accepted, oslo.policy's rules must allow that API call. It seems to me that the "expected" result ( derived from oslo.policy ) is always included in the actual result. Hoping that everything I said is correct, I would like to ask you: What issue is allowing such a strange behavior in Openstack APIs ? Why the expected results can be different from the actual ones? Are there publicly available examples showing "Failure" values? In general, are there any publicly available test cases that i can study to understand this? I Would like to thank you very much in advance; Best Regards, Jacopo

3 3

Cinder error while creating Volumes in Openstack
by Adivya Singh 12 Jul '21

12 Jul '21

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" Regards Adivya Singh

2 1

OpenInfra Live - July 15 at 9am CT
by Ashlee Ferguson 12 Jul '21

12 Jul '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the Open Infrastructure Foundation. One of the reasons workloads moved to virtualization and clouds was to avoid having underutilized resources. But as demand for resources goes up and down, the cloud itself can now have a lot of spare capacity. How do OpenStack-based large scale clouds manage their spare capacity? Join this live discussion between operators of private and public clouds with InMotion Hosting, CERN, NECTAR research cloud, Verizon Media, City Network and Open Telekom Cloud. Episode: How OpenStack Large Clouds Manage their Spare Capacity Date and time: July 15 at 9am CT (1400 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=G7oN2XdI__k <https://www.youtube.com/watch?v=G7oN2XdI__k> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6818945419729604608 <https://www.linkedin.com/feed/update/urn:li:ugcPost:6818945419729604608> Facebook: https://www.facebook.com/104139126308032/posts/4134653546589883/ <https://www.facebook.com/104139126308032/posts/4134653546589883/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Belmiro Moreira, CERN Brendan Conlan, Verizon Media Chris Bermudez, InMotion Hosting Erik Johansson, CityNetwork Sam Morrison, NECTAR Viktor Molnar, T-Systems Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Ashlee

1 0

[octavia] Meeting cancelled
by Gregory Thiemonge 12 Jul '21

12 Jul '21

Hi, I'm out of the office on July 14th, I won't be able to attend the weekly meeting. The meeting is cancelled. See you next week. Greg

1 0

[neutron] bug deputy report for week of 2021-07-05
by Bence Romsics 12 Jul '21

12 Jul '21

Hi Neutron Team, These are the new bugs of last week: High: * https://bugs.launchpad.net/neutron/+bug/1934930 [ovn] Multiple servers can try to create neutron_pg_drop at the same time fix proposed: https://review.opendev.org/c/openstack/neutron/+/799900 * https://bugs.launchpad.net/neutron/+bug/1934915 [OVN Octavia Provider] Investigate tempest failures tests disabled to unblock ovn-octavia-provider gate: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/799864 Medium: * https://bugs.launchpad.net/neutron/+bug/1934666 IPv6 not set on VMs when using DVR HA + SLAAC/SLAAC (or DHCPv6 stateless) * https://bugs.launchpad.net/neutron/+bug/1934912 Router update fails for ports with allowed_address_pairs containg IP range in CIDR notation fix proposed: https://review.opendev.org/c/openstack/neutron/+/800059 Low: * https://bugs.launchpad.net/neutron/+bug/1934957 [sriov] Unable to change the VF state for i350 interface unassigned RFE / Wishlist: * https://bugs.launchpad.net/neutron/+bug/1934948 [RFE] refactor of L3 resources update procedure * https://bugs.launchpad.net/neutron/+bug/1935764 RFE: Adding support for direct ports with qos in ovn * https://bugs.launchpad.net/neutron/+bug/1934670 neutron-tempest-plugin should migrate from paramiko Incomplete: * https://bugs.launchpad.net/neutron/+bug/1934135 nova cannot create instances, because it doesn't find the network Regards, Bence

1 0

[keystone][interop][refstack] Adding new capabilities to track in interop
by Martin Kopec 12 Jul '21

12 Jul '21

Hi everyone, we are adding new capabilities and tests for keystone service to interop, see: https://review.opendev.org/c/osf/interop/+/799163 If someone from keystone could review the patch, it would be great. Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

1 0

[Image Encryption] No meeting today
by Josephine Seifert 12 Jul '21

12 Jul '21

Hi, there will not be a meeting today, as I am ill. The next meeting will be next Monday the 19th of July. greetings Luzi

1 0

[qa] Virtual PTG October 2021
by Martin Kopec 12 Jul '21

12 Jul '21

Hi everyone, as you have probably heard our next PTG will be held virtually in October. I've created a Doodle [1] to collect the best time slots for our team. Please fill it in by Tuesday July 20th (the deadline for team signup is July 21st). 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://doodle.com/poll/a8gakx4ca6zvtuem?utm_source=poll&utm_medium=link [2] https://etherpad.opendev.org/p/qa-yoga-ptg Regards, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

1 0

[kolla][wallaby][neutron][vpnaas]
by Franck VEDEL 12 Jul '21

12 Jul '21

Hello, and first excuse my English please… thanks a lot. I hope you will understand my problem. I have a problem with the following configuration: kolla-ansible, centos, wallaby. I need the vpnaas service. I create internal networks, configure these networks, the routers, and I create a vpnaas between two internal networks (2 cirros instances for example). To the left; net1: 192.168.10.0/24 Right, net2: 192.168.20.0/24 VM On the left: ping VM on the right (ex 192.168.20.30). The ping goes to the internet, it is handled by the default route on the router leaving net1. I do the same with Victoria: it works. I am testing a VPN between net1 and an internal network behind a real network, behind a watchguard. With Victoria, it works. With Wallaby, it doesn't work. Neutron-l3-agent logs says: Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl ») Is there a bug in wallaby? What could be the problem, the configuration and the hardware is the same, it works with victoria, not with wallaby. Thanks for your help. Franck

1 1

[all][infra][qa] Retiring Logstash, Elasticsearch, subunit2sql, and Health
by Clark Boylan 09 Jul '21

09 Jul '21

Hello everyone, Xenial has recently reached the end of its life. Our logstash+kibana+elasticsearch and subunit2sql+health data crunching services all run on Xenial. Even without the distro platform EOL concerns these services are growing old and haven't received the care they need to keep running reliably. Additionally these services represent a large portion of our resource consumption: * 6 x 16 vcpu + 60GB RAM + 1TB disk Elasticsearch servers * 20 x 4 vcpu + 4GB RAM logstash-worker servers * 1 x 2 vcpu + 2GB RAM logstash/kibana central server * 2 x 8 vcpu + 8GB RAM subunit-worker servers * 64GB RAM + 500GB disk subunit2sql trove db server * 1 x 4 vcpu + 4GB RAM health server To put things in perspective, they account for more than a quarter of our control plane servers, occupying over a third of our block storage and in excess of half the total memory footprint. The OpenDev/OpenStack Infra team(s) don't seem to have the time available currently to do the major lifting required to bring these services up to date. I would like to propose that we simply turn them off. All of these services operate off of public data that will not be going away (specifically job log content). If others are interested in taking this on they can hook into this data and run their own processing pipelines. I am sure not everyone will be happy with this proposal. I get it. I came up with the idea for the elasticsearch job log processing way back at the San Diego summit. I spent many many many hours since working to get it up and running and to keep it running. But pragmatism means that my efforts and the team's efforts are better spent elsewhere. I am happy to hear feedback on this. Thank you for your time. Clark

10 13

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

09 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Y release naming process is completed and announced the name 'Yoga' on ML[1] * Added Ceph Dashboard charm to OpenStack charms [2] * Documentation updates to add DPL model also in 'Appointing leaders' process [3] * Charter change to handle the vacant seat situation during the election or in between of cycle [4]. 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-08-15.00.log.html * We will have next week's meeting on July 15th, Thursday 15:00 UTC[5]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[6] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Seven open reviews for ongoing activities[7]. ELK services next plan and help status --------------------------------------------- * We discussed this in the TC meeting, below is the summary: ** Help status: as of now, there are no volunteers to help. ** We defined the deadline of service shutdown if there is no help. Agreed Deadline is Yoga cycle end. Clark will update it on ML. ** We also discussed reducing the size of the existing system, and there were multiple ways. Clark will get more data on this and we will continue discussing the same in the next TC meeting on 15th July. 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 * During that I am also updating the retired/deprecated repo README.rst and many of deprecated repo need project-config update to remove the release job run from the master gate. * Retired repo does not need any action from the project team as TC has the ACL right and will take care of patch merge. * 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]. * Create repo for Hashicorp Vault deployment [11] * Deprecate os-panko role [12] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [13]. * Current status: One goal "Secure RBAC" is proposed [14]. 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] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023512.html [2] https://review.opendev.org/c/openstack/governance/+/797913 [3] https://review.opendev.org/c/openstack/governance/+/797985 [4] https://review.opendev.org/c/openstack/governance/+/797912 [5] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [6] https://etherpad.opendev.org/p/tc-xena-tracker [7] https://review.opendev.org/q/project:openstack/governance+status:open [8] https://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/+/799826 [12] https://review.opendev.org/c/openstack/governance/+/799817 [13] https://etherpad.opendev.org/p/y-series-goals [14] https://review.opendev.org/c/openstack/governance/+/799705 [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

[neutron] Drivers meeting - agenda for 9.07.2021
by Slawek Kaplonski 09 Jul '21

09 Jul '21

Hi, I will be on PTO tomorrow but Miguel will chair the meeting. Agenda for is at [1]. There are 3 RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1933517 - [RFE][OVN] Create an intermediate OVS bridge between VM and intergration bridge to improve the live-migration process * https://bugs.launchpad.net/neutron/+bug/1933222 - [RFE] Add distributed datapath for metadata * https://bugs.launchpad.net/neutron/+bug/1932154 - Off-path SmartNIC Port Binding [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

VM fail over mechanism to Remote DR site
by KK CHN 09 Jul '21

09 Jul '21

Members , I am using OpenStack Ussuri for our datacentre for virtualization requirements. we are using KVM hypervisor on Debian . We are in a requirement that our DR site is 200+ KMs apart from our office premises and connectivity over WAN. This DR site also going to deploy with Ussuri version. How we can setup the DR site so effectively so that, when VMs or Physical hosts in our DC clusters crashes or abruptly power to one physical machine got break due to electrical wire pulled out/unplugged , then how automatic failover to the DR site which is 300 miles away from our DC . what will be the solution for this setup so that automatically the VMs crashed in our DC will be served from our DR site with minimum latency or zero downtime (is zero down time possible ? kindly enlight on this or how to achieve near zero down time ) using OpenStack without any data loss ( is this possible no Data Loss ?). How ? Whats the best architecture for this using openstack, what all are the tools components need to be used ? and what type of solutions need to be deployed for the above requirement. VMs are nearly 100 nos and Linux and Windows majority of them with around 100 GB to 200 GB size for each VM. Kindly share your thoughts and expertise in this regard and enlighten me on what techniques / components of OpenStack need to be employed for achieving this. Any hints and tips and reference links highly appreciated. Thanks in advance, Kris

1 0

[tripleo] Retiring tripleo-common-tempest-plugin
by Takashi Kajinami 09 Jul '21

09 Jul '21

Hello, I have raised this in #tripleo channel yesterday but I noticed we have a tempest plugin[1] for tripleo but it has never been used actually. The repo has not been updated for a while and it's documentation still mentions very old items like python2, usage of mistral in undercloud, and so on. Because I'm not aware of any plan to use this repo for our testing, I proposed retiring repo[1]. If anybody has concern with this retirement, please give your feedback on the proposed change. [1] https://review.opendev.org/c/openstack/project-config/+/800154 Thank you, Takashi

2 1

[release] Release countdown for week R-12, Jul 12 - Jul 16
by Herve Beraud 09 Jul '21

09 Jul '21

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

qemu-kvm-rhev >= 2.10.0
by Pete Zhang 09 Jul '21

09 Jul '21

We have qemu-kvm-ev in yum.repos.d but it still complains of missing qemu-kvm-rhev. Any idea where we can find qemu-kvm-rhev (NOT qemu-kvm-ev), thx. Error: Execution of '/bin/yum -d 0 -e 0 -y install openstack-nova-compute' returned 1: Error: Package: 1:openstack-nova-compute-20.6.0-1.el7.noarch (local_openstack-tnrp) Requires: qemu-kvm-rhev >= 2.10.0 sh-4.2# yum list | grep qemu-kvm qemu-kvm-ev.x86_64 10:2.10.0-21.el7_5.1.1 local_openstack-tnrp qemu-kvm.x86_64 10:1.5.3-160.el7_6.1 @ORB-updates qemu-kvm-common.x86_64 10:1.5.3-160.el7_6.1 @ORB-updates qemu-kvm-tools.x86_64 10:1.5.3-160.el7_6.1 ORB-updates -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

2 1

[i40e][vf][sriov] Disabling i40evf driver at the compute level.
by Laurent Dumont 09 Jul '21

09 Jul '21

Hey everyone, We are troubleshooting some weirdness with X710 Intel cards and i40evf. Looking around, it seems that most vendors recommend disabling the i40evf driver from the compute side (and keeping the i40e driver). Is anyone aware of any funkiness if both the i40e driver and the i40evf driver is present on computes running VMs with SRIOV ports. Thanks!

3 3

[Cinder] Active/Active Support
by Swapnil Kulkarni 09 Jul '21

09 Jul '21

Hello Cinder Team, Can someone provide a reference documentation for active/active support for a Cinder Driver w.r.t. configuration and any driver changes expected? Best Regards, Swapnil

2 1

[Octavia dashboard] Impossible to fill the subnet field when creating a load balancer
by Taltavull Jean-Francois 09 Jul '21

09 Jul '21

Hi All, On my OSA Victoria deployment (on Ubuntu 20.04), the "Create Load Balancer" form does not allow me to fill the mandatory "subnet" field and therefore I can't create a load balancer with Horizon. On the other hand, Octavia works fine and I can create load balancers with the CLI, Terraform, etc. Has one of you already faced such a situation ? Best regards, Jean-François

3 6

[nova] Applying custom policies at VM creation time
by gustavo panizzo 08 Jul '21

08 Jul '21

Hello I'd like to reject VM creation or mutate the request depending on custom (business) logic for example - reject duplicate names within the same neutron network(s) - change the VM name to append a number or increase it (VM-1 requested, VM-1 already exists so it gets created as VM-2) - reject some values for particular keys on metadata (role=db rejected for project foo) How can I accomplish this? I really don't want to patch nova thanks PS: I found https://github.com/roaet/wafflehaus but it looks it hasn't been touched in years -- IRC: gfa GPG: 0x27263FA42553615F904A7EBE2A40A2ECB8DAD8D5 OLD GPG: 0x44BB1BA79F6C6333

2 2

VM failover mechanism to DR site at remote
by KK CHN 08 Jul '21

08 Jul '21

Hi list members , I am using OpenStack Ussuri for our datacentre for virtualization requirements. we are using KVM hypervisor on Debian . We are in a requirement that our DR site is 200+ KMs apart from our office premises and connectivity over WAN. This DR site also going to deploy with Ussuri version. How we can setup the DR site so effectively so that, when VMs or Physical hosts in our DC clusters crashes or abruptly power to one physical machine got break due to electrical wire pulled out/unplugged , then how automatic failover to the DR site which is 300 miles away from our DC . what will be the solution for this setup so that automatically the VMs crashed in our DC will be served from our DR site with minimum latency or zero downtime (is zero down time possible ? kindly enlight on this or how to achieve near zero down time ) using OpenStack without any data loss ( is this possible no Data Loss ?). How ? Whats the best architecture for this using openstack, what all are the tools components need to be used ? and what type of solutions need to be deployed for the above requirement. VMs are nearly 100 nos and Linux and Windows majority of them with around 100 GB to 200 GB size for each VM. Kindly share your thoughts and expertise in this regard and enlighten me on what techniques / components of OpenStack need to employed for achieving this. Any hints and tips and reference links hightly appreicated. Thanks in advance, Kris

1 0

cannot import name greenpool
by Pete Zhang 08 Jul '21

08 Jul '21

We are seeing this error in /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync] from eventlet import greenpool ImportError: cannot import name greenpool *glance/greenlet version* sh-4.2# yum list installed | grep -i "eventlet\|glance" openstack-glance.noarch 1:19.0.4-1.el7 @local_openstack-tnrp python2-eventlet.noarch 0.25.1-1.el7 @local_openstack-tnrp python2-glance.noarch 1:19.0.4-1.el7 @local_openstack-tnrp python2-glance-store.noarch 1.0.1-1.el7 @local_openstack-tnrp python2-glanceclient.noarch 1:2.17.1-1.el7 @local_openstack-tnrp *Log* Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: Traceback (most recent call last): Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/bin/glance-manage", line 6, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.cmd.manage import main Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/cmd/manage.py", line 54, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.db.sqlalchemy import alembic_migrations Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/alembic_migrations/__init__.py", line 28, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.db.sqlalchemy import api as db_api Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/api.py", line 46, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from glance.common import utils Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/glance/common/utils.py", line 29, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet.green import socket Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/eventlet/__init__.py", line 10, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet import convenience Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: File "/usr/lib/python2.7/site-packages/eventlet/convenience.py", line 4, in <module> Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: from eventlet import greenpool Notice: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]/returns: ImportError: cannot import name greenpool Error: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: Failed to call refresh: 'glance-manage db_sync' returned 1 instead of one of [0] Error: /Stage[main]/Glance::Db::Sync/Exec[glance-manage db_sync]: 'glance-manage db_sync' returned 1 instead of one of [0] -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[cinder] I have a question about openstack cinder zonemanager driver
by aaaa bbbb 08 Jul '21

08 Jul '21

I am using Brocade FC switch in my OpenStack environment. I have a question about OpenStack cinder zonemanger driver. I find that [fc-zone-manager] can only configure one zone driver. If I want to use two FC switches from different vendors at the same time. One is Brocade FC switch, the other one is Cisco FC switch. Is there a method or solution configure two FC switch zone driver in one cinder.conf ? I want them both to support Zone Manager.

2 1

[kolla] Clean shutdown for guest VMs when host shutdown
by J-P Methot 08 Jul '21

08 Jul '21

Hi, I'm about ready to go into production with kolla, but one small issue remains. On regular Openstack deployments, I would use the libvirt-guests service to ensure that VMs on hosts always shutdown cleanly when the host shuts down. This is to prevent database issues which may happen on guests during forced, unclean shutdowns. At first glance, Kolla doesn't seem to install this service or anything similar that would ensure clean shutdown of guests when the host shuts down. I have found in the github source, in the tools folder, a systemd script that is supposed to do that, but it tries to execute /usr/libexec/libvirt-guests.sh shutdown in the libvirt container, which doesn't exist there. Does Kolla already ensure clean shutdown automatically, or is there a script I'm missing that could make this work?

4 6

[kolla] [kolla-ansible] Multiple external ceph clusters
by Alexandros Soumplis 08 Jul '21

08 Jul '21

Hi all, I am trying to connect Cinder and Manila with a second CEPH cluster and cannot find an "elegant" way to copy a second pair of ceph.conf/ceph_keyring to the running images. I can do it manually or by changing the playbook code, but I was wondering if there is a clean solution that will allow me to do this without touching the base code of kolla-ansible. Thank you in advance for any suggestions! Best, Alexandros

1 0

bird rpm for Openstack Release Train
by Pete Zhang 08 Jul '21

08 Jul '21

Does anyone know which version of bird rpm used by Openstack Release Train and where I can download it? thx. -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[TripleO] Abandoning all open stable/stein and stable/queens patches for EOL
by Marios Andreou 08 Jul '21

08 Jul '21

Hello folks As brought to my attention this morning, we still have some open reviews against stein [1] and queens [2]. Since we have agreed to EOL those branches we should not be merging any new code there (if this is news to you (!) see [3] - EOL patches at [4][5]). I am going to go through and abandon all the patches in [1][2]. If this causes problems for you then please reach out to me ASAP so we can work something out if possible (may be harder for stein, e.g. we'd have to address some broken jobs first). For example, we can try and merge your patch and then resend the EOL patches at [4][5]. Once the patches at [4][5] merge (which is looking pretty close, they have at least one +2 from the release team) then all bets are off we can't merge anything else there. regards, marios [1] https://review.opendev.org/q/(project:%255Eopenstack/.*tripleo.*)AND(status… [2] https://review.opendev.org/q/(project:%255Eopenstack/.*tripleo.*)AND(status… [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023409.html [4] https://review.opendev.org/c/openstack/releases/+/798924 [5] https://review.opendev.org/c/openstack/releases/+/798925

2 3

Increase image upload limit
by open infra 08 Jul '21

08 Jul '21

Hi In a Kubernetes based OpenStack deployment, how to set the value for image_size_cap? Regards Danishka

1 0