July 2021 - openstack-discuss - lists.openstack.org

[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