October 2020 - openstack-discuss - lists.openstack.org

[Automation SIG] BoF today! feel free to join
by Rico Lin 20 Oct '20

20 Oct '20

Hi all, Automation SIG is hosting a BoF on Tue 20, 1:00pm - 1:45pm (18:00 - 18:45 UTC) - Virtual - Virtual Floor - Forum Room 2 https://summit.openinfra.dev/a/event/24753 Please join if you're interested. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[Multi-arch SIG][OpenInfra Summit] BoF today! Feel free to join us
by Rico Lin 20 Oct '20

20 Oct '20

Hi all As a forming SIG, we hope to have more hands or resources to keep pushing things forward. In this summit, we will host a BoF on Tuesday this week and hope to have people to join. Multi-arch SIG Tue 20, 12:15pm - 1:00pm (17:15 - 18:00 UTC) - Virtual - Virtual Floor - Forum Room Multi-arch SIG BoF https://summit.openinfra.dev/a/event/24752 Also if you would like to see some related sessions here's some you can consider: Multi-Arch Support in OpenStack https://summit.openinfra.dev/a/event/24708 The Progress for Cloud Computing on Arm architecture https://summit.openinfra.dev/a/event/24719 Cloud-hypervisor: A new choice for virtual machine monitor https://summit.openinfra.dev/a/event/24684 -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[nova] NUMA scheduling
by Eric K. Miller 20 Oct '20

20 Oct '20

Hi, I'm at a loss for finding good information about how a VM's vCPUs and Memory are assigned to NUMA nodes within a scheduled physical host. I think Libvirt does this, and the Nova Scheduler simply finds the right physical host to run the VM, and thus Nova has no input on which NUMA node to choose. So this might be a Libvirt question. We are running Stein and have the issue where VMs launch on NUMA Node 0, and not on NUMA Node 1, in physical hosts with two processors, and are simply looking for a way to tell Libvirt to consider NUMA Node 1 when scheduling a VM, since there is nearly all of the memory available on NUMA Node 1. Our flavors are defined with hw:numa_nodes='1' since we want all vCPUs+Memory to land on a single NUMA Node, and so the guest OS has visibility that a single NUMA Node is being used. We are "not" looking for a way to pin a VM to a specific NUMA node (such as for SR-IOV purposes). Any suggestions where to look for the solution? Thanks! Eric

5 17

[qa] Weekly meeting cancelled because of Summit and PTG
by Masayuki Igawa 20 Oct '20

20 Oct '20

Hi, We'll skip the meetings both this and next week because of the summit and PTG. See you there :) -- Masayuki Igawa

1 0

[openstack-helm] No meeting this week and next week
by Gage Hugo 20 Oct '20

20 Oct '20

Hello everyone, due to the summit and PTG there will be no meeting this week or next week. We will meet again on November 3rd at the usual time, thanks!

1 0

[Security SIG] No meeting this week or next week
by Gage Hugo 20 Oct '20

20 Oct '20

Hello everyone, due to the summit and PTG there will be no meeting this week or next week. We will meet again on November 5th at the usual time, thanks!

1 0

Forum Etherpads
by Kendall Nelson 20 Oct '20

20 Oct '20

Hello All! I wanted to encourage you to add your etherpads to the wiki for the Forum[1] like we normally do. Sorry I didn't sooner! -Kendall Nelson [1] https://wiki.openstack.org/wiki/Forum/Virtual2020

1 0

[announce][debian][victoria] general availability of OpenStack Victoria in Debian
by Thomas Goirand 20 Oct '20

20 Oct '20

Hi! It's my pleasure to announce the general availability of OpenStack Victoria in Debian. I've just finished uploading everything to Debian Unstable today, and the Buster backports are available the usual way, for example using extrepo (which is in the official Debian backports): apt-get install extrepo extrepo enable openstack_victoria apt-get update ... or directly setting-up the buster-victoria.debian.net repository the usual way. New in this release =================== As all projects are deprecating the policy.json files, all of the services are now using a /etc/<PROJECT>/policy.d/00_default_policy.yaml. The normal /etc/<PROJECT>/policy.json will be automatically deleted, as it can be a problem if it remains. Looking backward, a sensible rename to get the file away would have been nicer to Debian users, so this will be implemented soonish. Implementation in openstack-cluster-installer ============================================= Victoria can already be installed by OCI. The only issue that remains to be fixed, is puppet-openstack setting-up a /etc/keystone/puppet.conf wrongly in the controllers. Once the file contains the correct things, deployment can go on. Also, it looks like LVM volume nodes still need some fixes. Apart from these early glitches, everything seems working smoothly so far, and of course, these will be addressed soon. I'll be testing upgrades using the usual oci-cluster-upgrade-openstack-release script. Testing Victoria over Bullseye and Python 3.9 ============================================= The day OpenStack was released, Python 3.9 was uploaded to Debian Unstable. I've already sent a few patches to address some problems, but I haven't yet fully deployed OpenStack on top of Bullseye. Since Victoria will be the release for Bullseye, I will spend time polishing all of this before the forthcoming freeze in February. Hopefully, I'll also be able to finish scripting for upgrading a cluster from Buster to Bullseye before the freeze, just like one was shipped in OCI for Stretch to Buster upgrades. Cheers, Thomas Goirand (zigo)

1 0

Re: CentOS 8 Ussuri can't launch instance /usr/libexec/qemu-kvm: Permission denied
by Oliver Weinmann 20 Oct '20

20 Oct '20

Ok, I will try to disable selinux and deploy one more compute node. I just stumbled across another issue, not sure if it is related. The instance seems to be deployed just fine but now I looked on the console and neither cirros nor centos 7 seem to be booting up correctly. on cirros i see an error: [ 0.846019] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- and on centos7: error: not a correct XFS inode. I tried to create with ephemeral and volume. Cheers, Oliver Am 19. Oktober 2020 um 16:09 schrieb Alex Schultz <aschultz(a)redhat.com>: On Mon, Oct 19, 2020 at 7:59 AM Oliver Weinmann <oliver.weinmann(a)me.com> wrote: First of all thanks a lot for the quick reply. I just checked and it seems that the package is really not available for centos8 from the upstream repo: https://centos.pkgs.org/8/centos-appstream-x86_64/podman-1.6.4-15.module_el… When you say it should be available via rdo, does this mean I have to add or use a different repo when deploying undercloud / overcloud? I have followed the tripleo guide to deploy it: I thought we shipped it, maybe we don't because we run with selinux disabled so it doesn't show up in CI. https://docs.openstack.org/tripleo-docs/latest/ And is there a way to disable selinux on all overcloud nodes by default? I guess it is the default to disable it? Set the following in an environment file as part of the deployment: parameter_defaults: SELinuxMode: permissive Cheers, Oliver Am 19. Oktober 2020 um 15:29 schrieb Alex Schultz <aschultz(a)redhat.com>: On Mon, Oct 19, 2020 at 7:09 AM Oliver Weinmann <oliver.weinmann(a)me.com> wrote: Hi all, I have successfully deployed the overcloud many many times, but this time I have a strange behaviour. Whenever I try to launch an instance it fails. I checked the logs on the compute node and saw this error: Failed to build and run instance: libvirt.libvirtError: internal error: process exited while connecting to monitor: libvirt: error : cannot execute binary /usr/libexec/qemu-kvm: Permission denied googling led me to the solution to disable selinux: setenforce 0 I have not made this change persistent yet, as I would like to know why I'm facing this issue right now. What is actually the default for the overcloud nodes SeLinux? Enforcing, permissive or disabled? I build the ipa and overcloud image myself as I had to include drivers. Is this maybe the reason why SeLinux is now enabled, but is actually disabled when using the default ipa images? From a TripleO perspective, we do not officially support selinux enabled when running with CentOS. In theory it should work, however it is very dependent on versions. I think you're likely running into an issue with the correct version of podman which is likely causing this. We've had some issues as of late which require a very specific version of podman in order to work correctly with nova compute when running with selinux enabled. You need 1.6.4-15 or higher which I don't think is available with centos8. It should be available via RDO. Related: https://review.opendev.org/#/c/736173/ Thanks and Best Regards, Oliver

1 0

Introducing the Open Infrastructure Foundation
by Kendall Nelson 20 Oct '20

20 Oct '20

Hello Everyone, If you’re not watching the Open Infrastructure Summit keynotes right now, you just missed some big news (and it’s not too late to tune in <https://www.youtube.com/watch?v=wNNOFfDBB0o&ab_channel=OpenStackFoundation>!). Jonathan Bryce just announced the Open Infrastructure Foundation (OIF) <http://openinfra.dev> as the successor to the OpenStack Foundation (OSF). The name change reflects all of our community’s work building open infrastructure with dozens of open source components, and we could not have done it without your help. We look forward to continuing to collaborate with you over the next decade to build open source communities that write software for production. The Summit keynotes <https://www.youtube.com/watch?v=wNNOFfDBB0o&ab_channel=OpenStackFoundation> are still going on the YouTube live stream, so login now to hear more about this announcement and how OpenStack and other open source projects fit into the next decade of open infrastructure. You can also watch Imtiaz present an update today on what the community is doing and support them in the chat as they encourage Summit attendees to participate. Tomorrow Dawson Coleman and myself will also be presenting on the community and the last two releases. And if you haven’t already, join as an individual member <http://openinfra.dev/join> so you can get involved! Let’s get started! -Kendall Nelson (diablo_rojo) Upstream Developer Advocate The Open Infrastructure Foundation

1 0

Summit issues
by Kanevsky, Arkady 20 Oct '20

20 Oct '20

I was able to join summit. But I am perpetually stuck in "checking credentials..." Any recommendations? Thanks, Arkady

7 6

Re: CentOS 8 Ussuri can't launch instance /usr/libexec/qemu-kvm: Permission denied
by Oliver Weinmann 19 Oct '20

19 Oct '20

First of all thanks a lot for the quick reply. I just checked and it seems that the package is really not available for centos8 from the upstream repo: https://centos.pkgs.org/8/centos-appstream-x86_64/podman-1.6.4-15.module_el… When you say it should be available via rdo, does this mean I have to add or use a different repo when deploying undercloud / overcloud? I have followed the tripleo guide to deploy it: https://docs.openstack.org/tripleo-docs/latest/ And is there a way to disable selinux on all overcloud nodes by default? I guess it is the default to disable it? Cheers, Oliver Am 19. Oktober 2020 um 15:29 schrieb Alex Schultz <aschultz(a)redhat.com>: On Mon, Oct 19, 2020 at 7:09 AM Oliver Weinmann <oliver.weinmann(a)me.com> wrote: Hi all, I have successfully deployed the overcloud many many times, but this time I have a strange behaviour. Whenever I try to launch an instance it fails. I checked the logs on the compute node and saw this error: Failed to build and run instance: libvirt.libvirtError: internal error: process exited while connecting to monitor: libvirt: error : cannot execute binary /usr/libexec/qemu-kvm: Permission denied googling led me to the solution to disable selinux: setenforce 0 I have not made this change persistent yet, as I would like to know why I'm facing this issue right now. What is actually the default for the overcloud nodes SeLinux? Enforcing, permissive or disabled? I build the ipa and overcloud image myself as I had to include drivers. Is this maybe the reason why SeLinux is now enabled, but is actually disabled when using the default ipa images? From a TripleO perspective, we do not officially support selinux enabled when running with CentOS. In theory it should work, however it is very dependent on versions. I think you're likely running into an issue with the correct version of podman which is likely causing this. We've had some issues as of late which require a very specific version of podman in order to work correctly with nova compute when running with selinux enabled. You need 1.6.4-15 or higher which I don't think is available with centos8. It should be available via RDO. Related: https://review.opendev.org/#/c/736173/ Thanks and Best Regards, Oliver

2 1

Divisive Language stance final(?) draft and Forum session
by Amy Marrich 19 Oct '20

19 Oct '20

Hi everyone, Below is what we hope is the final draft of the OSF's stance on Divisive Language. If you have any comments please place them on the etherpad[0] and/or join us this Tuesday during the forum[1]. Please note that decisions related to what words should be replaced with are being left with the project's technical leadership with the knowledge that context is important to determine the best alternative. That said, the Diversity and Inclusion WG will be available to assist these groups. Thanks, Amy Marrich (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage 1- https://www.openstack.org/summit/2020/summit-schedule/events/24778/divisive… 1a - https://zoom.us/j/94295083896?pwd=VmZCTFN3eERDK1ltRHRyWDl0eG1hZz09 1b - https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage ------------------ The OpenStack Foundation (OSF) Board of Directors supports removal of wording identified as oppressive, racist and sexist by members of our communities from the software and documentation they produce. While we know there will be challenges, both technical and non-technical, this is an action we feel is important. These efforts are the responsibility of the various technical leadership groups within our communities, and we trust them to make appropriate decisions about applicability, timelines, minimizing impact to users and operators, and choosing the changes that make the most sense for their projects. Contributors will take care to make changes to software in the least disruptive way possible. While standardized wording is a laudable goal, we recognize that different implementation contexts might require different solutions. In many cases the work is also complicated by external dependencies for these projects, and their capacity to make necessary changes before we can implement ours. Terminology to which special attention should be paid includes: 1. The use of "slave," or "master" in reference to slavery-oriented relationships, as is currently found in databases, the domain name system, etc. 1. The terms "blacklist" and "whitelist" in various contexts (which might require a variety of different replacements to make sense for those contexts) 1. The use of "master" in non-slavery-related contexts such as revision control branches and documentation builds (pending feedback from our community members) We shall continue to be vigilant for other language areas that cause challenges and work with the community to evolve this policy.

2 1

CentOS 8 Ussuri can't launch instance /usr/libexec/qemu-kvm: Permission denied
by Oliver Weinmann 19 Oct '20

19 Oct '20

Hi all, I have successfully deployed the overcloud many many times, but this time I have a strange behaviour. Whenever I try to launch an instance it fails. I checked the logs on the compute node and saw this error: Failed to build and run instance: libvirt.libvirtError: internal error: process exited while connecting to monitor: libvirt: error : cannot execute binary /usr/libexec/qemu-kvm: Permission denied googling led me to the solution to disable selinux: setenforce 0 I have not made this change persistent yet, as I would like to know why I'm facing this issue right now. What is actually the default for the overcloud nodes SeLinux? Enforcing, permissive or disabled? I build the ipa and overcloud image myself as I had to include drivers. Is this maybe the reason why SeLinux is now enabled, but is actually disabled when using the default ipa images? Thanks and Best Regards, Oliver

2 1

[tripleo][ironic] fails to introspect: my fsm encountered an exception
by Ruslanas Gžibovskis 19 Oct '20

19 Oct '20

Hi all, I have a clean undercloud deployment. but when I add a node, it fails to introspect. in ironic logs I see interesting lines about FSM (what is it?) [1] and in the same paste, I have provided/pasted, how openstack overcloud node import instack.json looks like. [1] http://paste.openstack.org/show/uPwWVYlO3UQbrF0WzDFH/ -- Ruslanas Gžibovskis +370 6030 7030

3 14

[cyborg] Weekly meeting cancelled due to overlapping with Summit and PTG
by yumeng bao 19 Oct '20

19 Oct '20

Hi cyborg members! This is to announce that we will cancel our weekly meetings for the next two weeks(Oct 22 and Oct 29) and resume Nov 05 due to schedule overlapping with the OpenInfra China Hackathon, OpenInfra Summit, and PTG. If you have any questions, please let us know! Regards， Yumeng

1 0

[magnum] error when trying to overwrite master_lb_enabled in cluster create
by Ionut Biru 19 Oct '20

19 Oct '20

Hi guys, In template i have master_lb_disabled and i want to overwrite this option using: » openstack coe cluster create cluster002 --cluster-template b7e0be01-bf3b-4c32-af60-98b9edefa0be --keypair ioni --master-count 2 --node-count 2 --master-lb-enabled master_count must be 1 when master_lb_enabled is False (HTTP 400) (Request-ID: req-608b8634-d98e-4efd-b0e4-543ebc9eb315 Looking at the code https://opendev.org/openstack/magnum/src/branch/master/magnum/api/controlle… https://opendev.org/openstack/magnum/src/branch/master/magnum/api/attr_vali… It seems that the validator doesn't take in consideration the new cluster dictionary. I've modified the validator with: cluster.get('master_lb_enabled', cluster_template['master_lb_enabled']): and it seems to work fine Not sure if it is the right fix. -- Ionut Biru - https://fleio.com

1 0

approach to deploying rhosp 16.1 with octavia on standalone
by Chen Sagi 19 Oct '20

19 Oct '20

Hi, I am trying to figure out if I am able to deploy Red Hat Openstack platform with one physical server available, included with the Octavia solution. For now I have been trying to use the "openstack triplo deploy -standalone" command (with various environment files) and it Is unable to install Octavia without an undercloud available. Is it even possible? If so, I would love to hear some suggestions. Thanks, Chen Sagi.

2 3

Fwd: [ops] [cinder] __DEFAULT__ volume type
by Rajat Dhasmana 19 Oct '20

19 Oct '20

Sorry i forgot to include openstack discuss mailing list with my reply. ---------- Forwarded message --------- From: Rajat Dhasmana <rdhasman(a)redhat.com> Date: Sun, Oct 18, 2020 at 1:06 PM Subject: Re: [ops] [cinder] __DEFAULT__ volume type To: Eugen Block <eblock(a)nde.ag> Hi Eugen, On Sun, Oct 18, 2020 at 12:54 PM Eugen Block <eblock(a)nde.ag> wrote: > Hi, > > I also was confused about that during our upgrade to Train. I noticed > that many volumes in our cloud didn't have any volume type defined at > all, so I had to update the respective table before I could continue > the upgrade process. What do you mean by "updating the respective table"? The optimal way to update a volume with a volume type is: 1) create a volume type pointing to the backend in which the volume currently is 2) retype the volume to that volume type > I have also defined a different volume type in > cinder.conf but I don't think you can just delete the __DEFAULT__ > type, The functionality to delete the __DEFAULT__ type is only available since cinder train >= 15.4.0 (See the releasenotes for more info regarding the __DEFAULT__ type[1]) Also you need to have a valid value defined with ``default_volume_type`` in cinder.conf Let me know if you have respective settings and still not able to delete the __DEFAULT__ type. > I'm not sure anymore but I think I also tried that. But it > doesn't really hurt if you have one of your own types as default. > > Regards, > Eugen > > [1] https://docs.openstack.org/releasenotes/cinder/train.html#relnotes-15-4-0-s… Regards Rajat Dhasmana

2 1

[Image Encryption] No meeting this week and next week
by Josephine Seifert 19 Oct '20

19 Oct '20

Hi, due to the Summit and the PTG, there will be no meeting today and no meeting next week. Next meeting will be at November 2nd. greeting Josephine (Luzi)

1 0

Sorry for the stupid question... it’s been a while
by Florian Rommel 18 Oct '20

18 Oct '20

Hey everyone. So, I have developed openstack, wrote installers and fixed parts in the raw phytonutrients.. but... so I am , for fun and refreshing my memory, building an openstack deployment by hand, the hood old fashioned way. I have a few servers and I get everything working perfectly EXCEPT neutron ovs with dvr integration. I am using Ubuntu focal with ussuri release. When I deploy neutron i get the agents to show up and register with UP. The neutron-openvswitch-agent crashes with physical network floating to br-public not found. I am wondering how in need to configure the bridge in order to make this work. I have a empty interface (internet facing) which I added to br-public but where do I define the floating network name? Yes it’s stupid but I been banging my head against the wall:) Thanks already for help and sorry to anyone else for the dumb question:) //Florian

3 2

[ops] [cinder] __DEFAULT__ volume type
by Massimo Sgaravatto 18 Oct '20

18 Oct '20

I have recently updated my Cloud from Rocky to Train (I am running Cinder v. 15.4.0) I have a question concerning the __DEFAULT__ volume type, that I don't remember to have seen before. Since: - I have no volumes using this volume type - I defined in in the [DEFAULT] section of cinder.conf the attribute "default_volume_type" to a value different than "__DEFAULT___" I assume that I can safely delete the __DEFAULT__ volume type Is this correct? Thanks, Massimo

2 1

[glance][devstack] Problem with stack.sh in devsatck install
by James 18 Oct '20

18 Oct '20

hi guys：       I met some problems in installing devstack . the details please refers to "Errors" listed as below.     The environment: 1) Win 10 ; 2) VMware workstation ;3) ubuntu-18.04.5-desktop-amd64;4)devstack          The installation processes refer to the devstack quick start (https://docs.openstack.org/devstack/latest/) Could you give me the solution to solve the problem. Error : Installing collected packages: oslo.rootwrap, retrying, os-win, oslo.privsep, os-brick, simplejson, python-cinderclient, glance-store Attempting uninstall: simplejson Found existing installation: simplejson 3.13.2 ERROR: Cannot uninstall 'simplejson'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. +inc/python:pip_install:1 exit_trap +./stack.sh:exit_trap:489 local r=1 ++./stack.sh:exit_trap:490 jobs -p +./stack.sh:exit_trap:490 jobs= +./stack.sh:exit_trap:493 [[ -n '' ]] +./stack.sh:exit_trap:499 '[' -f '' ']' +./stack.sh:exit_trap:504 kill_spinner +./stack.sh:kill_spinner:399 '[' '!' -z '' ']' +./stack.sh:exit_trap:506 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:507 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:509 type -p generate-subunit +./stack.sh:exit_trap:510 generate-subunit 1589476087 780 fail +./stack.sh:exit_trap:512 [[ -z /opt/stack/logs ]] +./stack.sh:exit_trap ...

2 1

Your Virtual PTG Checklist
by Kendall Waters 17 Oct '20

17 Oct '20

REGISTRATION If you haven't done so, please register for the PTG! This is how we will be able to provide you with the tooling information and passwords. Register here: https://october2020ptg.eventbrite.com <https://october2020ptg.eventbrite.com/> FINAL SCHEDULE The final schedule [1] for the event is set here and in the PTGBot [2]. IRC The main form of synchronous communication between attendees during the PTG is on IRC. If you are not on IRC, learn how to get started here [3]. The main PTG IRC channel is #openstack-ptg on Freenode. It's used to interact with the PTGbot, and Foundation staff will be present to help answer questions. PTGBOT The PTGbot [3] is an open source tool that PTG track moderators use to surface what's currently happening at the event. Track moderators will send messages to the bot via IRC, and from that information, the bot publishes a webpage with several sections of information: - The discussion topics currently discussed in the room ("now") - An indicative set of discussion topics coming up next ("next") - The schedule for the day with available extra slots you can book Learn more about the ptgbot via the documentation here [4]. HELP DESK We are here to help! If you have any questions during the event week, we encourage you to join the #openstack-ptg IRC channel and ask them there. You can ping Kendall Waters (wendallkaters) and Kendall Nelson(diablo_rojo) directly on IRC. We will also have a dedicated Zoom room, but ONLY FOR MONDAY, October 26 where an OSF staff member will be available to answer your event related questions. You can also always reach someone at ptg(a)openstack.org if you are unable to connect to IRC. FEEDBACK We have preemptively created an etherpad[5] to collect all of your feedback throughout the event. Please add your thoughts as the week goes on. GAME TIME! Since we all know that coming together as a community to hang out and play games is part of what makes the PTG great, we are going to try something new this time around. This PTG, we are going to have two 'game nights'- obviously time zones are hard and it might not be night for everyone, but the times are as follows. - Thursday, October 29 at 19:00 UTC - Friday, October 30 at 10:00 UTC - Friday, October 30 at 23:00 UTC If you are interested in participating, write your name in the etherpad [6]. We will use it to coordinate games for each of the timeslots. [1] PTG schedule: https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c0… <https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c0…> [2] PTGbot: http://ptg.openstack.org/ptg.html <http://ptg.openstack.org/ptg.html> [3] How to get started on IRC: https://docs.openstack.org/contributors/common/irc.html <https://docs.openstack.org/contributors/common/irc.html> [4] PTGbot documentation: https://github.com/openstack/ptgbot/blob/master/README.rst <https://github.com/openstack/ptgbot/blob/master/README.rst> [5] Feedback Etherpad: https://etherpad.opendev.org/p/October2020-PTG-Feedback <https://etherpad.opendev.org/p/October2020-PTG-Feedback> [6] Game Time Etherpad: https://etherpad.opendev.org/p/October2020-PTG-Games <https://etherpad.opendev.org/p/October2020-PTG-Games>

1 0

[OSSA-2020-007] Blazar: Remote code execution in blazar-dashboard (CVE-2020-26943)
by Pierre Riteau 17 Oct '20

17 Oct '20

======================================================== OSSA-2020-007: Remote code execution in blazar-dashboard ======================================================== :Date: October 12, 2020 :CVE: CVE-2020-26943 Affects ~~~~~~~ - Blazar-dashboard: <1.3.1, ==2.0.0, ==3.0.0 Description ~~~~~~~~~~~ Lukas Euler (Positive Security) reported a vulnerability in blazar-dashboard. A user allowed to access the Blazar dashboard in Horizon may trigger code execution on the Horizon host as the user the Horizon service runs under. This may result in Horizon host unauthorized access and further compromise of the Horizon service. All setups using the Horizon dashboard with the blazar-dashboard plugin are affected. Patches ~~~~~~~ - https://review.opendev.org/755814 (Stein) - https://review.opendev.org/755813 (Train) - https://review.opendev.org/755812 (Ussuri) - https://review.opendev.org/756064 (Victoria) - https://review.opendev.org/755810 (Wallaby) Credits ~~~~~~~ - Lukas Euler from Positive Security (CVE-2020-26943) References ~~~~~~~~~~ - https://launchpad.net/bugs/1895688 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26943

1 0