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

OpenStack user survey data available?
by Bernd Bausch 23 Oct '20

23 Oct '20

Is there a way to get access to raw user survey data? Some of the graphical data on the analytics page <https://www.openstack.org/analytics> is unreadable, in particular information about Neutron's drivers: The analytics FAQ tells me to contact heidijoy(a)openstack.org <mailto:heidijoy@openstack.org> for questions, but email to this address bounces back. 550 5.1.1 <heidijoy(a)openstack.org>: Email address could not be found, or was misspelled (G8) Thanks much, Bernd

5 9

[tripleo] TripleO CI Summary: Unified Sprint 34
by Rafael Folco 23 Oct '20

23 Oct '20

Greetings, The TripleO CI team has just completed **Unified Sprint 34** (Oct 02 thru Oct 22). The following is a summary of completed work during this sprint cycle: In the last sprint we had two major goals: #1 OpenStack Victoria release preparation and #2 Docker.io removal from upstream CI #1 OpenStack Victoria release preparation Integration and component pipelines have been created and prepared for the stable/victoria branching. Periodic jobs, promotion, configuration and monitoring changes have been merged in order to run victoria pipelines and promote builds. Upstream jobs will be branched in the next sprint. https://hackmd.io/sasvoKjTSkabGlFOTkK_kw #2 Docker.io removal from upstream CI Standalone, multinode, undercloud and upgrade jobs have been converted in consumers of the new content provider job. With this new dependency relation, artifacts are not pulled from external sources like docker.io. Instead, container images and rpm packages are built in the provider job using local registries, pulled to the consumer, and then discarded. https://hackmd.io/vRMVeZXZRgK5Vxqi6ENUDg Jobs across all TripleO repositories have been switched to the new content provider job. There are still changes in flight to make this happen for stable branches and CentOS7 jobs. This work should be completed in the next week. Content provider changes (80+): https://review.opendev.org/#/q/topic:new-ci-job Upstream promotions [1] Ruck/Rover recorded notes [2]. The planned work for the next sprint is to complete the work started in the previous sprint, and focuses on: - Finish switching to content provider on stable branches and CentOS7 jobs. - Branch upstream stable/victoria jobs. The Ruck and Rover for this sprint are Sagi Shnaidman (sshnaidm) and Sandeep Yadav (ysandeep). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [3]. Thanks, --rfolco [1] http://dashboard-ci.tripleo.org/d/HkOLImOMk/upstream-and-rdo-promotions?org… [2] https://hackmd.io/1qxCqYzATfudl1cKvaQ8-w [3] https://hackmd.io/a_PhAlijTr-KTWHzGuf3qQ

1 0

[CloudKitty][ptg] PTG next week
by Rafael Weingärtner 23 Oct '20

23 Oct '20

Hi, Thanks to all of you who proposed some topics for our meeting at the PTG. I hope you are all enjoying the virtual summit this week. Next week is the virtual PTG, an event where we will reflect on the past release cycle and look forward to the next release, Wallaby, and beyond. The CloudKitty discussions at the PTG are organized in Etherpad [1]. The PTG meeting is free to attend, but please register [2] and add your name to the Etherpad. If you can't make all of the sessions, but are interested in specific topics, add your name to the topic to request an IRC ping. I am looking forward to seeing you all next week. Cheers, Rafael [1] https://etherpad.opendev.org/p/cloudkitty-ptg-wallaby [2] https://october2020ptg.eventbrite.com -- Rafael Weingärtner

1 0

[Diversity][PTG] Diversity and Inclusion WG at the PTG - Divisive Language
by Amy Marrich 23 Oct '20

23 Oct '20

The Diversity and Inclusion WG will be holding a PTG session Monday from 15:00-17:00 UTC. We will be using Meetpad[0] atleast to start but will change to Zoom if needed. Based on feedback [2] during the Forum session we will be working on providing a more comprehensive list of words and possible alternatives vs the original plan to leave this aspect within the technical groups. Thanks, Amy Marrich (spotz) 0 - https://meetpad.opendev.org/wallaby-ptg-diversity 1 - https://etherpad.opendev.org/p/wallaby-ptg-diversity 2 - https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage

1 0

Re: VM stuck in hard_reboot state
by Fabian Zimmermann 23 Oct '20

23 Oct '20

Hi, just forwarding your answer to the list - sorry for not using reply-all :( Is your nova-compute-agent on the hypervisor working as expected? (check the logs, restart) Are you able to reset the state? You should ensure the instance is not running somewhere else! https://docs.openstack.org/ocata/admin-guide/support-compute.html#reset-the… Fabian Am 23.10.20 um 14:16 schrieb Gregory SACRE: > Here they are: > > compute $ virsh list > Id Name State > -------------------- > > compute $ virsh list --all > Id Name State > ------------------------------------ > - instance-00000008 shut off > - instance-00000009 shut off > - instance-00000015 shut off > - instance-00000016 shut off > - instance-00000017 shut off > - instance-0000001c shut off > - instance-0000001d shut off > - instance-0000001e shut off > - instance-0000001f shut off > > controller $ openstack server show mediawiki > +-----------------------------+----------------------------------------------------------+ > | Field | Value > | > +-----------------------------+----------------------------------------------------------+ > | OS-DCF:diskConfig | AUTO > | > | OS-EXT-AZ:availability_zone | nova > | > | OS-EXT-STS:power_state | Running > | > | OS-EXT-STS:task_state | rebooting_hard > | > | OS-EXT-STS:vm_state | active > | > | OS-SRV-USG:launched_at | 2019-08-09T13:43:06.000000 > | > | OS-SRV-USG:terminated_at | None > | > | accessIPv4 | > | > | accessIPv6 | > | > | addresses | wiki-selfservice=172.16.1.54, > 192.168.150.154 | > | config_drive | > | > | created | 2019-08-09T13:32:49Z > | > | flavor | m2.large (7) > | > | hostId | > b8cbd9da0d28d67fff65b88405428269c97d8d27289e2f8ee35f5485 | > | id | 0e3eafb6-1b36-4e03-8548-8a3294d82c65 > | > | image | > | > | key_name | gsa-key > | > | name | mediawiki > | > | project_id | a5f2b77a4a8e499791ee981b991f2df3 > | > | properties | > | > | security_groups | name='teleport' > | > | | name='default' > | > | | name='global_http' > | > | status | HARD_REBOOT > | > | updated | 2020-10-23T08:50:09Z > | > | user_id | 16ea223cee1345dda504c8408c55fb2a > | > | volumes_attached | > id='bdfe4fc6-1e85-4b5d-b9b6-16147fbfc005' | > +-----------------------------+----------------------------------------------------------+ > > Thanks for the help! > > > Sorry for this question, but shouldn't I reply to the mailing list? > I'm new to this mailing list so I'm not 100% sure on the habits (I > have read the mailing list netiquette, but I prefer to ask first :-)) > > > On Fri, Oct 23, 2020 at 12:26 PM Fabian Zimmermann <dev.faz(a)gmail.com> wrote: >> >> Hi, >> >> could you dump the outputs of >> >> virsh list >> virsh list --all >> openstack server show >> >> Fabian >> >> Gregory SACRE <gregory.sacre(a)gmail.com> schrieb am Fr., 23. Okt. 2020, 12:16: >>> >>> Dear all, >>> >>> >>> I've been using Openstack (Ubuntu 18.04 install following Openstack documentation) for about a year in a lab at work. >>> I have one VM running 24/7 with Mediawiki on it (rest is for testing). >>> >>> It has been working fine until I updated packages yesterday. Here is the list of relevant packages that were updated: >>> >>> 2020-10-22 09:44:04 status installed neutron-common:all 2:14.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:06 status installed nova-common:all 2:19.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:12 status installed python3-nova:all 2:19.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:16 status installed python3-neutron:all 2:14.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:25 status installed neutron-linuxbridge-agent:all 2:14.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:29 status installed nova-compute-libvirt:all 2:19.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:44:35 status installed nova-compute-kvm:all 2:19.3.1-0ubuntu1~cloud0 >>> 2020-10-22 09:45:04 status installed nova-compute:all 2:19.3.1-0ubuntu1~cloud0 >>> >>> Since then, the VM does not respond (ping, ssh...). >>> I could list it (via Web interface or controller command line) and it showed as ACTIVE. >>> I rebooted the server thinking maybe something was stuck. The server came back online, the VM still ACTIVE but cannot connect to it. >>> My next step was to hard reboot the VM. Since then, the VM is in HARD_REBOOT state and would not move from there. I tried to shut it down, restart again the server, but no, nothing changes. When I try to shut it down it says it cannot as it is in hard reboot state. >>> >>> I would at least like to be able to save some stuff that's on it (I know, I should have backed it up before the update...). >>> My Google searches on "openstack vm stuck hard reboot" did not help... >>> >>> Do not hesitate if you need more info. >>> Any help would really be appreciated! >>> >>> >>> Kr, >>> >>> Gregory

1 0

[puppet] Gerrit breach and commit audit
by Takashi Kajinami 23 Oct '20

23 Oct '20

Hello, As suggested by the recent announcement[1], I started walking through the commits for puppet-openstack repos. [1] https://etherpad.opendev.org/p/puppet-gerrit-breach-audit You can find the progress in the etherpad below[2]. [2] https://etherpad.opendev.org/p/puppet-gerrit-breach-audit I'll update this thread once I complete checking all, but I would appreciate your help about some of the repos because we have so many repos here. Thank you, Takashi

2 2

VM stuck in hard_reboot state
by Gregory SACRE 23 Oct '20

23 Oct '20

Dear all, I've been using Openstack (Ubuntu 18.04 install following Openstack documentation) for about a year in a lab at work. I have one VM running 24/7 with Mediawiki on it (rest is for testing). It has been working fine until I updated packages yesterday. Here is the list of relevant packages that were updated: 2020-10-22 09:44:04 status installed neutron-common:all 2:14.3.1-0ubuntu1~cloud0 2020-10-22 09:44:06 status installed nova-common:all 2:19.3.1-0ubuntu1~cloud0 2020-10-22 09:44:12 status installed python3-nova:all 2:19.3.1-0ubuntu1~cloud0 2020-10-22 09:44:16 status installed python3-neutron:all 2:14.3.1-0ubuntu1~cloud0 2020-10-22 09:44:25 status installed neutron-linuxbridge-agent:all 2:14.3.1-0ubuntu1~cloud0 2020-10-22 09:44:29 status installed nova-compute-libvirt:all 2:19.3.1-0ubuntu1~cloud0 2020-10-22 09:44:35 status installed nova-compute-kvm:all 2:19.3.1-0ubuntu1~cloud0 2020-10-22 09:45:04 status installed nova-compute:all 2:19.3.1-0ubuntu1~cloud0 Since then, the VM does not respond (ping, ssh...). I could list it (via Web interface or controller command line) and it showed as ACTIVE. I rebooted the server thinking maybe something was stuck. The server came back online, the VM still ACTIVE but cannot connect to it. My next step was to hard reboot the VM. Since then, the VM is in HARD_REBOOT state and would not move from there. I tried to shut it down, restart again the server, but no, nothing changes. When I try to shut it down it says it cannot as it is in hard reboot state. I would at least like to be able to save some stuff that's on it (I know, I should have backed it up before the update...). My Google searches on "openstack vm stuck hard reboot" did not help... Do not hesitate if you need more info. Any help would really be appreciated! Kr, Gregory

1 0

Keystone with AzureAD as openid provider - JWT token could not be validated
by Robert Duncan 23 Oct '20

23 Oct '20

Found this when trying OS_AUTH_TYPE="v3oidcpassword" For anybody using AzureAD as idp in Keystone, it is not OIDC compliant - surprised? keystone will not validate tokens as they are signed for MS graph API essentially it results in "Apache WWW-Authenticate: Bearer error="invalid_token", error_description="JWT token could not be validated" keystone attempts to validate the tokens from the metadata using whatever if finds in https://login.microsoftonline.com/<tenant-guid>/v2.0/.well-known/openid-configuration<https://login.microsoftonline.com/6edb49c1-bf72-4eea-8b3f-a7fd0a25b68c/v2.0…> or using an Apache variable in wsgi-keystone.conf called OIDCOAuthVerifyJwksUri for example - it will reach here https://login.microsoftonline.com/<tenant-guid>/discovery/v2.0/keys<https://login.microsoftonline.com/6edb49c1-bf72-4eea-8b3f-a7fd0a25b68c/disc…> and find keys - however it won't be able to validate the token as MS inserts a nonce before signing them - i.e. the tokens can only be validated by ms graph additionally, if you try to validate the tokens locally on keystone using Apache variable OIDCOAuthVerifyCertFiles the keys can rotate without warning. The solution is using the app registration portal in Azure and modify the app registration by selecting 'expose an API' and add a scope - then request this scope on the client using apache variable 'OIDCScope' https://medium.com/@abhinavsonkar/making-azure-ad-oidc-compliant-5734b70c43… Rob Duncan. ________________________________ The information contained and transmitted in this e-mail is confidential information, and is intended only for the named recipient to which it is addressed. The content of this e-mail may not have been sent with the authority of National College of Ireland. Any views or opinions presented are solely those of the author and do not necessarily represent those of National College of Ireland. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. If you have received this communication in error, please delete the e-mail and destroy all record of this communication. Thank you for your assistance. ________________________________

1 0

[kuryr][ptg] virtual PTG
by Maysa De Macedo Souza 23 Oct '20

23 Oct '20

Hello, With the PTG approaching, I would like to encourage you to look at the PTG etherpad [1] and add any topics you want to discuss (please mention your name and IRC nickname). Even if you won't be able to attend the PTG, feel free to add the topic so it gets discussed. The Kuryr meeting[2] will happen at 7 UTC-8 UCT on October 27 at the Grizzly room. Cheers, Maysa Macedo [1] https://etherpad.openstack.org/p/wallaby-ptg-kuryr [2] http://ptg.openstack.org/ptg.html

1 0

[manila] PTG Schedule has been updated
by Goutham Pacha Ravi 23 Oct '20

23 Oct '20

Hello Zorillas and all interested stackers, Thanks for making your topic proposals on the planning etherpad [1]. You will notice that [1] has the re-arranged list of topics by their intended time slots. Please take a look and call out any issues you may have against your topics, or topics that may interest you. As is tradition, we won't have time to accommodate the whole schedule, but we'll try to pick up any new topics and languishing issues that haven't made it to the schedule with best effort. If we cannot address them at the PTG, i'll make sure to bring them to our weekly IRC meetings. Please save the bookmark to the live PTG schedule: http://ptg.openstack.org/ptg.html and subscribe to PTG bot updates so you don't miss the action! Looking forward to seeing you all there! Thanks, Goutham [1] https://etherpad.opendev.org/p/wallaby-ptg-manila-planning

1 1

[puppet] Gerrit breach and commit audit
by Tobias Urdin 23 Oct '20

23 Oct '20

Hello, As per the announcement in [1] I have audited all changes to Puppet OpenStack repositories. [1] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html

1 0

[placement] Train upgrade warning
by CHANU ROMAIN 23 Oct '20

23 Oct '20

Hello, I just did an openstack upgrade, from Stein to Train, OS is Ubuntu 18.04. I followed the procedure but I got a warning as return code (1). Everything works now but i'm affraid one day it will make an upgrade to fail: # placement-status upgrade check +------------------------------------------------------------------+ | Upgrade Check Results | +------------------------------------------------------------------+ | Check: Missing Root Provider IDs | | Result: Success | | Details: None | +------------------------------------------------------------------+ | Check: Incomplete Consumers | | Result: Warning | | Details: There are -15753 incomplete consumers table records for | | existing allocations. Run the "placement-manage db | | online_data_migrations" command. | +------------------------------------------------------------------+ #echo $? => 1 =a t least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK. Then i tried "placement-manage db online_data_migrations" the command does nothing because negative records Then "placement-manage db sync; echo $?" => 0 So what should I do about these -15753 incomplete consumeurs? Is it normal than nova_api sql backup keep growing? Best regards, Romain

1 0

[OpenStack] OpenStack Victoria for Ubuntu 20.10 and Ubuntu 20.04 LTS
by Corey Bryant 23 Oct '20

23 Oct '20

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack Victoria on Ubuntu 20.10 (Groovy Gorilla) and Ubuntu 20.04 LTS (Focal Fossa) via the Ubuntu Cloud Archive. Details of the Victoria release can be found at: https://www.openstack.org/software/victoria. To get access to the Ubuntu Victoria packages: == Ubuntu 20.10 == OpenStack Victoria is available by default for installation on Ubuntu 20.10. == Ubuntu 20.04 LTS == The Ubuntu Cloud Archive for OpenStack Victoria can be enabled on Ubuntu 20.04 by running the following command: sudo add-apt-repository cloud-archive:victoria The Ubuntu Cloud Archive for Victoria includes updates for: aodh, barbican, ceilometer, cinder, designate, designate-dashboard, glance, gnocchi, heat, heat-dashboard, horizon, ironic, keystone, magnum, manila, manila-ui, masakari, mistral, murano, murano-dashboard, networking-arista, networking-bagpipe, networking-baremetal, networking-bgpvpn, networking-hyperv, networking-l2gw, networking-mlnx, networking-odl, networking-sfc, neutron, neutron-dynamic-routing, neutron-vpnaas, nova, octavia, octavia-dashboard, openstack-trove, trove-dashboard, ovn-octavia-provider, panko, placement, sahara, sahara-dashboard, sahara-plugin-spark, sahara-plugin-vanilla, senlin, swift, vmware-nsx, watcher, watcher-dashboard, and zaqar. For a full list of packages and versions, please refer to: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/victoria_v… == Reporting bugs == If you have any issues please report bugs using the ‘ubuntu-bug’ tool to ensure that bugs get logged in the right place in Launchpad: sudo ubuntu-bug nova-conductor Thank you to everyone who contributed to OpenStack Victoria. Enjoy and see you in Wallaby! Corey (on behalf of the Ubuntu OpenStack Engineering team)

2 1

[ussuri][ansible][cinder] cinder-api timeout in setup-openstack
by Kiluria 22 Oct '20

22 Oct '20

Hello everyone, first of all, im very new with openstack. Currently i am trying to install my first openstack in a testing System consisting of 6 PCs. But i have some Problems to get it to work. I would be very grateful if someone could help me, to find my Problem. I tried to install Openstack with the Openstack-Ansible Deployment Guide. My Configuration files are: openstack_user_config.yml: http://paste.openstack.org/show/799294/ user_variables.yml : yhttp://paste.openstack.org/show/799295/ But the last Playbook "setup-openstacks" runs on an error. At the Task "os_cinder : Ensure cinder api is available" i get a timeout. It says that HTTP Error 503 and it can not connect to 172.29.236.9:8776 (open-stack-03). There is no port 8776 open on the internal haproxy IP. But the cinder-api.service in the cinder-api container is enabled. And there is even an open Port 8776 in the container. ("ss -tunlp") Does anyone have an idea what I did wrong? Thanks for every answer!

1 0

[neutron] Drivers meeting
by Slawek Kaplonski 22 Oct '20

22 Oct '20

Hi, We have one new RFE [1] proposed by Liu, but as we have PTG next week, I added it to the PTG agenda for discussion (on Thursday). And with that I think we can cancel tomorrow's meeting. Have a great weekend and see You on Monday at PTG :) [1] https://bugs.launchpad.net/neutron/+bug/1900934 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Survey on OpenStack Distributors
by foundjem＠ieee.org 22 Oct '20

22 Oct '20

Hello everyone, we are currently conducting a research to analyze how OpenStack distributors contribute changes back upstream. Please consider participating in this survey [1]. Thank you, Armstrong Foundjem Release team, SAIL Laboratory Queen’s University 1. https://forms.gle/QdHybesAuxysWe1i7 <https://forms.gle/QdHybesAuxysWe1i7>

1 0

[charms] Charm CI outage the weekend of Oct 23 - Oct 25
by Frode Nordahl 22 Oct '20

22 Oct '20

Hello fellow hackers, The Charm third party CI will be out this weekend on the back of some maintenance work. We will endeavour to get it back online Monday October 26th. Enjoy your weekend once you get there wherever you are. Cheers! -- Frode Nordahl

1 0

[release] Release countdown for week R-25, Oct 19 - 23
by Herve Beraud 22 Oct '20

22 Oct '20

Welcome back to the release countdown emails! These will be sent at major points in the Wallaby development cycle, which should conclude with a final release on Wednesday, 14 April, 2021. Development Focus -------------------------- At this stage in the release cycle, focus should be on planning the Wallaby development cycle, assessing Wallaby community goals and approving Wallaby specs. General Information -------------------------- Wallaby is a 26 weeks development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/wallaby/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the Victoria release are continued in Wallaby with a similar release model. If you intend to drop a deliverable, or modify its release model, please do so before the Wallaby-1 milestone by proposing a change to the deliverable file at: https://opendev.org/openstack/releases/src/branch/master/deliverables/walla… Upcoming Deadlines & Dates ------------------------------------- Virtual Wallaby PTG: October 26-30 Wallaby-1 milestone: December 3 Hervé Beraud and the entire Release Management Team -- 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

[kolla][ptg] PTG next week
by Mark Goddard 22 Oct '20

22 Oct '20

Hi, I hope you are all enjoying the virtual summit this week. As I'm sure you're all aware, next week is the virtual PTG, an event where we will reflect on the past release cycle and look forward to the next release, Wallaby, and beyond. The Kolla discussions at the PTG are organised via an Etherpad [1], and as we near the event, it is starting to take shape. It's free to attend, but please register [2] and add your name to the Etherpad. If you can't make all of the sessions, but are interested in specific topics, add your name to the topic to request an IRC ping. Look forward to seeing you next week. Cheers, Mark [1] https://etherpad.opendev.org/p/kolla-wallaby-ptg [2] https://october2020ptg.eventbrite.com

1 0

[blazar] PTL away
by Pierre Riteau 22 Oct '20

22 Oct '20

Hello, I'll be away for the next couple of weeks for paternity leave. All Blazar meetings are cancelled in the meantime. Pierre Riteau (priteau)

1 0

Error installing Horizon
by Cristina Mayo 22 Oct '20

22 Oct '20

Hi, I installed Horizon on my Openstack Ussuri cloud and it has worked fine for some months. A few days ago, I had some trouble with python packages (I updated some dependencies by error). I'm trying to reinstall Horizon because it fails but it seems almost impposible to me: # apt install openstack-dashboard Configuring openstack-dashboard (3:18.3.2-0ubuntu0.20.04.2) ... Collecting and compressing static assets... WARNING:root:"dashboards" and "default_dashboard" in (local_)settings is DEPRECATED now and may be unsupported in some future release. The preferred way to specify the order of dashboards and the default dashboard is the pluggable dashboard mechanism (in /usr/share/openstack-dashboard/openstack_dashboard/enabled, /usr/share/openstack-dashboard/openstack_dashboard/local/enabled). Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 204, in fetch_command app_name = commands[subcommand] KeyError: 'collectstatic' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "manage.py", line 25, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 211, in fetch_command settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 66, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 157, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/share/openstack-dashboard/openstack_dashboard/settings.py", line 352, in <module> STATICFILES_DIRS += settings_utils.get_xstatic_dirs( File "/usr/share/openstack-dashboard/openstack_dashboard/utils/settings.py", line 288, in get_xstatic_dirs module = import_module(module_name) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked ModuleNotFoundError: No module named 'horizon.xstatic' dpkg: error to process package openstack-dashboard (--configure) E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks in advance, Best

3 2

[tc] Gerrit breach and commit audit
by Ghanshyam Mann 22 Oct '20

22 Oct '20

Hello Everyone, As per the announcement of the Gerrit breach [1], I have audited all repos under the Technical Committee for 1. Suspicious commit 2. Core group list and everything is fine except the one already reported. - https://opendev.org/openstack/governance/src/branch/master/reference/techni… - https://opendev.org/openstack/governance/src/branch/master/reference/user-c… [1] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html -gmann

2 1

[neutron][ptg] Sessions schedule
by Slawek Kaplonski 22 Oct '20

22 Oct '20

Hi Neutrinos, Thanks for all of You who proposed some topics for our meeting at the PTG. I prepared agenda for that in etherpad [1]. I didn't specify exact time slots for each topics but just moved things around for specific days. We will move through the list of topics and use as much time for each of them as needed. I hope that will work better than scheduled time slots for topic :) Please review that agenda and ping me if You would like to add/change anything there. There is not much time for that but still I can do some changes :) And as it was during last ptg, we are gonna use meetpad [2] for our meetings. Last time it worked fine so I hope it will be like that this time too. If not, we can fallback to zoom during the PTG week. That's all from me for now. Have a great (and safe) weekend and see You on Monday. [1] https://etherpad.opendev.org/p/neutron-wallaby-ptg [2] https://meetpad.opendev.org/neutron-wallaby-ptg -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[oslo][core] gerrit breach and auditing all oslo deliverables [1] since Oct 01
by Herve Beraud 22 Oct '20

22 Oct '20

Hello, As every team we are also concerned by the gerrit breach and we must take a look at our changes during this time frame on all our deliverables [1]. The list of deliverables owned by Oslo is very huge, we need a methodical approach and also external help to check all these repositories. Fortunately oslo was in feature freeze during the majority of this period so I think it will reduce the scope of our investigation to our master branches. Due to the criticality of the problem I propose the following action plan: - first, split our deliverables in group and assign volunteer on them - second, focus us on changes against our scripts, executable files and CI config; - third, inspect documentation; - fourth, inspect other kinds of changes that I missed in previous points. I wrote a script [2][3] to help the release team to extract relevant changes (*.py, *.sh), all the rest (*.yaml, *.rst) have been ignored for now, we could adapt this script to lead our investigation. Example of script usage against our openstack/oslo.messaging repos: ``` $ cd oslo.messaging $ curl https://gist.githubusercontent.com/4383/511359cc2080e06295944c5f40bd1033/ra… | sh ``` Are you interested to follow this action plan? Ben as you are the security liaison are you interested in coordinating these groups/actions? Else any volunteer? Feel free to propose another approach or to propose changes on this one. Please ensure to double check your account activity [4] and make sure nothing is off. Special congrats to Julia Kreger and for her excellent job [5]. Thank you in advance for your help, [1] https://governance.openstack.org/tc/reference/projects/oslo.html#deliverabl… <https://governance.openstack.org/tc/reference/projects/release-management.h…> [2] https://gist.github.com/4383/511359cc2080e06295944c5f40bd1033 [3] https://gist.githubusercontent.com/4383/511359cc2080e06295944c5f40bd1033/ra… [4] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html [5] http://lists.openstack.org/pipermail/openstack-discuss/2020-October/018148.… -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----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-----

4 6

[tacker] Gerrit breach and commit audit
by Yasufumi Ogawa 22 Oct '20

22 Oct '20

Hi, As announced for the gerrit breach [1], I have audited all repos under Tacker for 1. Suspicious commit 2. Core group list and everything is fine [2]. [1] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html [2] https://etherpad.opendev.org/p/tacker-gerrit-breach-audit Regards, Yasufumi

1 0