July 2020 - openstack-discuss - lists.openstack.org

October/November PTG Date Selection
by Kendall Waters 27 Jul '20

27 Jul '20

Hello Everyone! We wanted to get your input on the best dates for holding the PTG now that its been annouced that the Summit itself will be virtual[1]. Please fill out the CIVS poll by August 3 at 15:00 UTC. We really appreicate your feedback! Poll: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_a69944444a9b7c93&akey=3ecc… <https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_a69944444a9b7c93&akey=3ecc…> There are obviously many pros and cons to each option, below are the conflicts/reasons why we might not want to select that option. Option 0 - Two weeks before Summit (October 5-9) Conflicts with RC work External Event Conflicts: None? Option 1 - One week after Summit (October 26-30) Halloween on Oct 31 Perfect for release timing but event fatigue is a real concern External Event Conflicts: Open Source Summit EU, ODSC Open Data Science Conference East Cloud Foundry Summit EU, KVM Forum Option 2 - Two weeks after the Summit (November 2-6) USA Election day on Nov 3; could be a distraction, contributors needing to go vote (whatever that looks like with the virus), news, etc. Event Conflicts: None? Option 3 - Three weeks after the Summit (November 9-13) Pushes far into the cycle (4 weeks after previous release, a bit late, Veterns day/holiday - may affect France and Germany and US) External Events Conflicts: VMWorld EU -The Kendalls (diablo_rojo & wendallkaters) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016068.html <http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016068.html>

1 0

[Image-Encryption] No meeting today
by Josephine Seifert 27 Jul '20

27 Jul '20

Hi, there won't be a popup team meeting today. We will resume next week. greetings Josephine (Luzi)

1 0

[kolla] Kolla klub meeting next week
by Mark Goddard 24 Jul '20

24 Jul '20

Hi, The next Kolla klub meeting is scheduled for Thursday at 15:00 UTC. I propose the following topic: Downstream fork amnesty: are you running with locally applied bug fix or feature patches? Would they be useful to the rest of the community? Let's have an open discussion about the useful code that we all might be sitting on, and discuss how we can share it for the benefit of the wider community. There is room for other topics if anyone would like to propose them. We previously postponed these topics: * Gaël: Offline usage of Kolla & Kolla Ansible * Justinas: host OS lifecycle management Can we cover them this week? https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 0

Magnum: invalid format of client version
by Alexander Dibbo - UKRI STFC 24 Jul '20

24 Jul '20

Hi, I have just deployed magnum into my train enviroment and am seeing the following error when creating any kind of cluster: This is a Train environment deployed from RDO packages (9.4.0-1). Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server [req-aa9ce18b-64eb-40ad-b1c0-b7c312402780 - - - - -] Exception during message handling: InvalidParameterValue: ERROR: UnsupportedVersion: : resources.worker_nodes_server_group: : Invalid format of client version ''. Expected format 'X.Y', where X is a major part and Y is a minor part of version. Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server Traceback (most recent call last): Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 160, in wrapper Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/magnum/conductor/handlers/cluster_conductor.py", line 95, in cluster_create Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server raise e Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server InvalidParameterValue: ERROR: UnsupportedVersion: : resources.worker_nodes_server_group: : Invalid format of client version ''. Expected format 'X.Y', where X is a major part and Y is a minor part of version. Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server #033[00m When logging in debug, I see a dump of a huge heat template and a 400 bad request from heatclient (as below) immediately before the above log excerpt: {"explanation": "The server could not comply with the request since it is either malformed or otherwise incorrect.", "code": 400, "error": {"message": "UnsupportedVersion: : resources.master_nodes_server_group: : Invalid format of client version ''. Expected format 'X.Y', where X is a major part and Y is a minor part of version.", "traceback": null, "type": "StackValidationFailed"}, "title": "Bad Request"} log_http_response /usr/lib/python2.7/site-packages/heatclient/common/http.py:157 More details are available in my question here: https://ask.openstack.org/en/question/128520/magnum-invalid-format-of-clien… Any suggestions on where to look to set the client version it is complaining about would be much appreciated? Thanks Alex Regards Alexander Dibbo - Cloud Architect / Cloud Operations Group Leader For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io<https://stfc-cloud-docs.readthedocs.io/> To raise a support ticket with the cloud team please email cloud-support(a)gridpp.rl.ac.uk<mailto:cloud-support@gridpp.rl.ac.uk> To receive notifications about the service please subscribe to our mailing list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD To receive fast notifications or to discuss usage of the cloud please join our Slack: https://stfc-cloud.slack.com/ This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.

3 10

[ops][cinder] festival of EOL - ocata and pike
by Brian Rosmaita 24 Jul '20

24 Jul '20

Lee Yarwood recently announced the change to 'unmaintained' status of nova stable/ocata [0] and stable/pike [1] branches, with the clever idea of back-dating the 6 month period of un-maintenance to the most recent commit to each branch. I took a look at cinder stable/ocata and stable/pike, and the most recent commit to each is 8 months ago and 7 months ago, respectively. The Cinder team discussed this at today's Cinder meeting and agreed that this email will serve as notice to the OpenStack Community that the following openstack/cinder branches have been in 'unmaintained' status for the past 6 months: - stable/ocata - stable/pike The Cinder team hereby serves notice that it is our intent to ask the openstack infra team to tag each as EOL at its current HEAD and delete the branches two weeks from today, that is, on Wednesday, 22 July 2020. (This applies also to the other stable-branched cinder repositories, that is, os-brick, python-cinderclient, and python-cinderclient-extension.) Please see [2] for information about the maintenance phases and what action would need to occur before 22 July for a branch to be adopted back to the 'extended maintenance' phase. On behalf of the Cinder team, thank you for your attention to this matter. cheers, brian [0] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015747.html [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015798.html [2] https://docs.openstack.org/project-team-guide/stable-branches.html

2 6

[tripleo][centos8][ussuri][horizon] horizon container fails to start
by Ruslanas Gžibovskis 24 Jul '20

24 Jul '20

Hi all, I have noticed, that horizon container fails to start and some interestin zen_wozniak has apeared [0]. Healthcheck log is empty, but horizon log [1] sais "/usr/bin/python: No such file or directory" and there is no such file or directory :) after sume update it failed. I believe you guys will push update fast enough, as I am still bad at this git and container part.... HOW to fix it now :) on my side? As tripleo will redeploy horizon from images... and will update image. could you please give me a hint where to duck tape it whille it will be pushed to prod? [0] http://paste.openstack.org/show/3jjnsgXfWRxs3o0G6aKH/ [1] http://paste.openstack.org/show/1S66A55cz0UaFUWGxID8/ -- Ruslanas Gžibovskis +370 6030 7030

1 2

Re: [Release-job-failures] Release of openstack/oslo.messaging for ref refs/tags/12.2.2 failed
by Thierry Carrez 23 Jul '20

23 Jul '20

zuul(a)openstack.org wrote: > Build failed. > > - openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/2a9767af93c640ddb1bd1f864b2e71e3 : SUCCESS in 1m 03s > - release-openstack-python https://zuul.opendev.org/t/openstack/build/dfce7b106189491b9d9026a079c06bdd : POST_FAILURE in 4m 19s > - announce-release https://zuul.opendev.org/t/openstack/build/None : SKIPPED > - propose-update-constraints https://zuul.opendev.org/t/openstack/build/None : SKIPPED Two recent issues with AFS publication: oslo.messaging 12.2.2 - tag OK, build OK, pyPI OK, tarball not published https://zuul.opendev.org/t/openstack/build/dfce7b106189491b9d9026a079c06bdd designate 8.0.1 - tag OK, build OK, pyPI OK, tarball not published https://zuul.opendev.org/t/openstack/build/0f6c659223df46278c26460b2f3281fe Error: There was an issue creating /afs/.openstack.org as requested: [Errno 13] Permission denied: b'/afs/.openstack.org' Impact: - Tarballs are missing from tarballs.o.o - Missing release announces - Missing constraint updates We also had one AFS issue with docs publication to releases.o.o: https://zuul.opendev.org/t/openstack/build/3ca65d8665514c429629d18485ed186b But that should get synced at next refresh. -- Thierry Carrez (ttx)

2 1

[glance] Meeting about copy-image race condition
by Abhishek Kekane 23 Jul '20

23 Jul '20

Hi All, We (glance team) are organizing one meeting on Monday 27 July at 1400 UTC [1] . During ussuri glance has added the new import method 'copy-image' [2] to copy existing images in multiple stores. Recently while adding a CI job at nova side we have found out that there will be race conditions [3] if two or more simultaneous copy operations were initiated. There iS also WIP fix [4] submitted for the same but there have been lots of objections about the same. Objective of the meeting is to decide the approach to fix this issue. Interested people can join us to share their inputs for the same. [1] https://bluejeans.com/905878787 [2] https://review.opendev.org/696457 [3] https://bugs.launchpad.net/glance/+bug/1884596 [4] https://review.opendev.org/#/c/737596/ Thank you Abhishek

1 0

[PTL][Stable] Releases proposed for stable/stein
by Sean McGinnis 23 Jul '20

23 Jul '20

/me takes off release team hat and puts on stable team hat Hey everyone, To help out with stable releases, I've run a script to propose releases for any deliverables in stable/stein that had commits merged but not released yet. This is just to try to help make sure those fixes get out downstream, and to help ease the crunch that we inevitably have near the time that stable/stein goes into Extended Maintenance mode (this coming November). These are not driven by the release team, and they are not required. They are merely a convenience to help out the teams. If there is a patch for any deliverables owned by your team and you are good with the release, please leave a +1 and we will process it. Any patches with a -1, or anything not acknowledged by the end of next week, will just be abandoned. Of course, stable releases can be proposed by the team whenever they are ready. Again, this is not a release team activity. This may or may not be done regularly. I just had some time and an itch to do it. Patches can be found here: https://review.opendev.org/#/q/topic:stein-stable+(status:open+OR+status:me… Thanks! Sean

1 1

The Open Infrastructure Summit is Going Virtual!
by OpenStack Foundation 23 Jul '20

23 Jul '20

Call For Presentations is open! To view this email online, paste this link into your browser: https://t.e2ma.net/message/2ndfhc/ysadgbb GET EXCITED The Open Infrastructure Summit is coming directly to your browser! (https://t.e2ma.net/click/2ndfhc/ysadgbb/ulmein) GET READY Register for the Virtual Summit YOU READ IT RIGHT The annual Open Infrastructure Summit is going to be virtual (and free!), increasing accessibility for community members around the world! Now what? STEP ONE Register for free (https://t.e2ma.net/click/2ndfhc/ysadgbb/aenein) Register for the virtual Summit and make sure to mark your calendars - the Open Infrastructure Summit will be held October 19-23. STEP TWO Submit your talks (https://t.e2ma.net/click/2ndfhc/ysadgbb/q6nein) The Call For (https://t.e2ma.net/click/2ndfhc/ysadgbb/6yoein) Presentations (https://t.e2ma.net/click/2ndfhc/ysadgbb/mrpein) (CFP) deadline is August 4 at 11:59pm PT, so start drafting your presentations and panels around Open Infrastructure use cases like AI/Machine Learning, CI/CD, Container Infrastructure, Edge Computing and of course, Public, Private and Hybrid Clouds. STEP THREE Join the conversation (https://t.e2ma.net/click/2ndfhc/ysadgbb/2jqein) Invite your friends to login on October 19 for a packed agenda from the global community and join the conversation using #OpenInfraSummit (https://t.e2ma.net/click/2ndfhc/ysadgbb/icrein) ONE EXTRA STEP (IT'S WORTH IT) Sponsor the Summit! (https://t.e2ma.net/click/2ndfhc/ysadgbb/y4rein) Getting your organization some visibility is only one extra step - check out the prospectus and sign up to sponsor the virtual Summit! Learn more about the Summit (https://t.e2ma.net/click/2ndfhc/ysadgbb/exsein) PO Box 1903 | Austin , TX 78767 United States This email was sent to openstack-infra(a)lists.openstack.org. To ensure that you continue receiving our emails, please add us to your address book or safe list. manage your preferences (https://app.e2ma.net/app2/audience/signup/1812998/1771360/132927328/2247466…) opt out (https://t.e2ma.net/optout/2ndfhc/ysadgbb?s=dyit5ndwSJyARvqMDTMrpiGM27LZJv3w…) using TrueRemove(r). Got this as a forward? Sign up (https://app.e2ma.net/app2/audience/signup/1812998/1771360.132927328/) to receive our future emails.

1 0