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

[all][goals] Switch legacy Zuul jobs to native - update #1
by Luigi Toscano 22 Jul '20

22 Jul '20

Hi, Victoria is not far away and one of the goal is the removal of all legacy Zuul v3 jobs. tl;dr - the goal page is https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-j… - that page is being updated (https://review.opendev.org/#741987/) please check the migration guide on: https://docs.openstack.org/project-team-guide/zuulv3.html - I summarized the status on this etherpad, which will be used as reference: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration - I'm around as tosky on IRC, feel free to ping me or ask here on the list, especially if I haven't contacted you already - if you haven't started yet, please prioritize this goal, which will also provide most of the work for the other community goal (migrate from bionic to focal) almost for free. --- And now, the longer version. It's time for some updates about the "Switch legacy Zuul jobs to native" community goal. I apologize for the lack of official communication so far about the goal, despite the Victoria cycle has been open for a (long) while. On the other hand, the porting of the legacy is ongoing. Thanks to everyone who helped with the rewriting even before this was a goal, and thanks to the people who started working on this (writing and reviewing patches). I've got in touch with a few teams during the PTG and during the team meetings in the past weeks, but unfortunately attended the PTG or is active on IRC, and with few exceptions, a significant amount of legacy jobs belongs to less active teams. The projects which right now use legacy job, regardless of the status (many of them have patches floating around), are listed below. Projects with (*) have been contacted by me during or after the PTG and the work is ongoing: - barbican (*) - blazar (*) - cinder (*) - designate - ec2-api - freezer - glance (*) - heat (*) - infra (*) - ironic (*) - karbor - keystone (*) - kuryr (*) - magnum - manila (*) - monasca (*) - murano - neutron (*) - nova (*) - oslo (*) - senlin - trove - tripleo (*) - vitrage - watcher - zaqar Back to the etherpad (https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration) the most important section is the first one, "Jobs to be ported", which includes all the legacy jobs which affects Victoria. While the goal focuses on Victoria, when the jobs are ported, in order to easy the maintenance, I believe it would make everyone's life easier if you just backport to the new jobs to the older branches, as far as it's possible. As a general remark, that native tempest and devstack jobs should work to all branches starting from pike, while the new grenade jobs only work starting from train right now (they may be enabled in stein in the future, but it's not sure yet). Please remember to always use the native-zuulv3-migration gerrit topic. The "Stretch goal only (they don't affect master)" section lists the jobs defined in openstack/openstack-zuul-jobs.git which are still used by stable branches. If you feel like that and if it's possible, please backport the native jobs to the not-yet covered branches, so that we can clean up openstack-zuul-jobs. Ciao -- Luigi

1 0

[release] Release countdown for week R-12 July 20 - July 24
by Sean McGinnis 22 Jul '20

22 Jul '20

Better late than never? Could have sworn I sent this last week. Development Focus ----------------- The Victoria-2 milestone is next week, on July 30! Victoria-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/victoria/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Victoria' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Upcoming Deadlines & Dates -------------------------- Victoria-2 milestone: July 30 Ussuri Cycle-trailing deadline: August 13

1 0

[openstack-ansible] os_congress role retirement
by Dmitriy Rabotyagov 22 Jul '20

22 Jul '20

Hi everyone. Since congress service has been retired with [1], there's no reason for us to carry on and maintain os_congress role [2] for the inactive project. In case congress service will be revived, we can revert role retirement and continue its support in the future. [1] https://review.opendev.org/#/c/721733/ [2] https://opendev.org/openstack/openstack-ansible-os_congress -- Kind regards, Dmitriy Rabotyagov

1 1

[largescale-sig] Next meeting: July 22, 8utc
by Thierry Carrez 22 Jul '20

22 Jul '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, July 22 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200722T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - ttx to identify from the chat interested candidates from Opendev event and invite them to next meeting - amorin to add some meat to the wiki page before we push the Nova doc patch further - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation - amorin to start a thread on osarchiver proposing to land it somewhere in openstack - amorin to start a [largescale-sig] thread about his middleware ping approach, SIG members can comment if that makes sense for them Talk to you all on Wednesday, -- Thierry Carrez

1 1

[TripleO] [Train] CentOS 8: Undercloud installation fails
by Reza Bakhshayeshi 22 Jul '20

22 Jul '20

Hi, I'm going to install OpenStack Train with the help of TripleO on CentOS 8, but undercloud installation fails with the following error: "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat[10-zaqar_wsgi.conf]/Concat_file[10-zaqar_wsgi.conf]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat[10-zaqar_wsgi.conf]/File[/etc/httpd/conf.d/10-zaqar_wsgi.conf]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-apache-header]/Concat_fragment[zaqar_wsgi-apache-header]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-docroot]/Concat_fragment[zaqar_wsgi-docroot]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-directories]/Concat_fragment[zaqar_wsgi-directories]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-logging]/Concat_fragment[zaqar_wsgi-logging]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-serversignature]/Concat_fragment[zaqar_wsgi-serversignature]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-access_log]/Concat_fragment[zaqar_wsgi-access_log]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-setenv]/Concat_fragment[zaqar_wsgi-setenv]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-wsgi]/Concat_fragment[zaqar_wsgi-wsgi]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-custom_fragment]/Concat_fragment[zaqar_wsgi-custom_fragment]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Concat::Fragment[zaqar_wsgi-file_footer]/Concat_fragment[zaqar_wsgi-file_footer]: Skipping because of failed dependencies", "puppet-user: Warning: /Stage[main]/Zaqar::Wsgi::Apache/Openstacklib::Wsgi::Apache[zaqar_wsgi]/Apache::Vhost[zaqar_wsgi]/Apache::Listen[192.168.24.1:8888]/Concat::Fragment[Listen 192.168.24.1:8888]/Concat_fragment[Listen 192.168.24.1:8888]: Skipping because of failed dependencies", "puppet-user: Notice: Applied catalog in 1.72 seconds", "puppet-user: Changes:", "puppet-user: Total: 97", "puppet-user: Events:", "puppet-user: Failure: 1", "puppet-user: Success: 97", "puppet-user: Total: 98", "puppet-user: Resources:", "puppet-user: Failed: 1", "puppet-user: Skipped: 41", "puppet-user: Changed: 97", "puppet-user: Out of sync: 98", "puppet-user: Total: 235", "puppet-user: Time:", "puppet-user: Resources: 0.00", "puppet-user: Concat file: 0.00", "puppet-user: Anchor: 0.00", "puppet-user: Concat fragment: 0.00", "puppet-user: Augeas: 0.03", "puppet-user: File: 0.39", "puppet-user: Zaqar config: 0.61", "puppet-user: Transaction evaluation: 1.69", "puppet-user: Catalog application: 1.72", "puppet-user: Last run: 1594207735", "puppet-user: Config retrieval: 4.14", "puppet-user: Total: 1.72", "puppet-user: Version:", "puppet-user: Config: 1594207730", "puppet-user: Puppet: 5.5.10", "+ rc=6", "+ '[' False = false ']'", "+ set -e", "+ '[' 6 -ne 2 -a 6 -ne 0 ']'", "+ exit 6", " attempt(s): 3", "2020-07-08 15:59:00,478 WARNING: 95123 -- Retrying running container: zaqar", "2020-07-08 15:59:00,478 ERROR: 95123 -- Failed running container for zaqar", "2020-07-08 15:59:00,478 INFO: 95123 -- Finished processing puppet configs for zaqar", "2020-07-08 15:59:00,482 ERROR: 95117 -- ERROR configuring ironic", "2020-07-08 15:59:00,484 ERROR: 95117 -- ERROR configuring zaqar"]} Any suggestion would be grateful. Regards, Reza

5 9

[all] PyCharm Community licences
by ʂʍɒρƞįł Ҟưȴķɒʁʉɨ 21 Jul '20

21 Jul '20

I have renewed the Pycharm licenses for community contributors until July 20, 2021. For everyone who is using it will be updated automatically. Please do not request again for renewal. If you are an active contributor and need one, please submit the details on [1] [1] https://docs.google.com/forms/d/e/1FAIpQLSe5JMbtZEKB95AMVnyOBh4-7Y55hDgQChj… Best Regards, Swapnil Best Regards, Swapnil Kulkarni irc : coolsvap coolsvap at gmail dot com +91-87960 10622(c) http://in.linkedin.com/in/coolsvap

1 0

[security] Security SIG Meeting July 23rd Cancelled
by Gage Hugo 21 Jul '20

21 Jul '20

Hello, The security SIG meeting for this week is cancelled, we plan on meeting at the usual time next week.

1 0

[tc] weekly update
by Mohammed Naser 21 Jul '20

21 Jul '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - V goals, Zuul v3 migration: update links and grenade https://review.opendev.org/#/c/741987/ - [manila] assert:supports-accessible-upgrade https://review.opendev.org/740509 - migrate testing to ubuntu focal https://review.opendev.org/740851 - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - Add legacy repository validation https://review.opendev.org/737559 [Updated 12 days ago] - Cleanup the remaining osf repos and their data https://review.opendev.org/739291 [Updated 13 days ago] - [draft] Add assert:supports-standalone https://review.opendev.org/722399 [Updated 27 days ago] # Email Threads - New Office Hours: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015761.html - Summit CFP Open: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015730.html # Other Reminders - If you're an operator, make sure you fill out our user survey: https://www.openstack.org/user-survey/survey-2020/ - Milestone 2 coming at the end of the month Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[all][TC] New Office Hours Times
by Kendall Nelson 21 Jul '20

21 Jul '20

Hello! It's been a while since the office hours had been refreshed and we have a lot of new people on the TC that were not around when the times were set. In an effort to stir things up a bit, and get more community engagement, we are picking new times! I want to invite everyone in the community interested in interacting more with the TC to respond to the poll so we have your input as the office hours are really for your benefit anyway. (Nevermind the name of the poll :) Too much work to remake the whole thing just to rename it..) That said, we do need responses from ALL TC members so that we can also document who will (typically) be present for each office hour as well. (Also, thanks Mohammed for putting the poll together! It's no joke. ) -Kendall (diablo_rojo) [1] https://doodle.com/poll/q27t8pucq7b8xbme

2 3

CentOS unrecoverable after Ceph issues
by Grant Morley 21 Jul '20

21 Jul '20

Hi all, We recently had an issue with our ceph cluster which ended up going into "Error" status after some drive failures. The system stopped allowing writes for a while whilst it recovered. The ceph cluster is healthy again but we seem to have a few instances that have corrupt filesystems on them. They are all CentOS 7 instances. We have got them into rescue mode to try and repair the FS with "xfs_repair -L" However when we do that we get this: 973.026283] XFS (vdb1): Mounting V5 Filesystem [ 973.203261] blk_update_request: I/O error, dev vdb, sector 8389693 [ 973.204746] blk_update_request: I/O error, dev vdb, sector 8390717 [ 973.206136] blk_update_request: I/O error, dev vdb, sector 8391741 [ 973.207608] blk_update_request: I/O error, dev vdb, sector 8392765 [ 973.209544] XFS (vdb1): xfs_do_force_shutdown(0x1) called from line 1236 of file fs/xfs/xfs_buf.c. Return address = 0xffffffffc017a50c [ 973.212137] XFS (vdb1): I/O Error Detected. Shutting down filesystem [ 973.213429] XFS (vdb1): Please umount the filesystem and rectify the problem(s) [ 973.215036] XFS (vdb1): metadata I/O error: block 0x7ffc3d ("xlog_bwrite") error 5 numblks 8192 [ 973.217201] XFS (vdb1): failed to locate log tail [ 973.218239] XFS (vdb1): log mount/recovery failed: error -5 [ 973.219865] XFS (vdb1): log mount failed [ 973.233792] blk_update_request: I/O error, dev vdb, sector 0 Interestingly any debian based instances we could recover. It just seems to be CentOS and having XFS on CentOS and ceph the instances don't seem happy. This seems more low level to me in ceph rather than a corrupt FS on a guest. Does anyone know of any "ceph tricks" that we can use to try and at least get an "xfs_repair" running? Many thanks, -- Grant Morley Cloud Lead, Civo Ltd www.civo.com <https://www.civo.com/>

2 2

[nova] spec review day on Tuesday 07-21
by Balázs Gibizer 21 Jul '20

21 Jul '20

Hi, As the spec freeze will happen next week at Milestone 2 we agreed[1] to have a dedicated spec review day on Tuesday (07-21). If you are a spec author then please prepare to react on the incoming feedback on your open spec. If you are reviewer then please focus on reviewing open specs during the day. Cheers, gibi [1] http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-07-16-16.00.log…

2 1

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

21 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 Here is my config file: [DEFAULT] auth_strategy = keystone debug = true memcached_servers = dev-service1.nubes.rl.ac.uk:11211 my_ip = 172.16.103.43 rpc_backend = rabbit stack_domain_admin = magnum stack_domain_admin_password = MAGNUM_PASS stack_user_domain_name = magnum transport_url = rabbit://openstack:rabbit-pass@dev-rabbit4.nubes.rl.ac.uk:5672,openstack:rabbit-pass@dev-rabbit5.nubes.rl.ac.uk:5672,openstack:rabbit-pass@dev-rabbit6.nubes.rl.ac.uk:5672/ verbose = true [api] host = 172.16.103.43 [barbican_client] endpoint_type = public region_name = RegionOne [cache] backend = oslo_cache.memcache_pool enabled = true memcache_servers = dev-service1.nubes.rl.ac.uk:11211 [certificates] cert_manager_type = x509keypair [cinder_client] endpoint_type = public region_name = RegionOne [database] connection = mysql+pymysql://magnum:MAGNUM_DBPASS@dev-openstack.stfc.ac.uk:3306/magnum connection_recycle_time = 3600 [glance_client] endpoint_type = public region_name = RegionOne [heat_client] endpoint_type = public region_name = RegionOne [keystone_authtoken] admin_password = MAGNUM_PASS admin_tenant_name = service admin_user = magnum auth_plugin = password auth_type = password auth_uri = https://dev-openstack.stfc.ac.uk:5000 auth_url = https://dev-openstack.stfc.ac.uk:5000 insecure = false password = MAGNUM_PASS project_domain_name = default project_name = service user_domain_name = default username = magnum www_authenticate_uri = https://dev-openstack.stfc.ac.uk:5000 [magnum_client] endpoint_type = public region_name = RegionOne [neutron_client] endpoint_type = public region_name = RegionOne [nova_client] endpoint_type = public region_name = RegionOne [octavia_client] endpoint_type = public region_name = RegionOne [oslo_concurrency] lock_path = /var/lib/magnum/tmp [oslo_middleware] enable_proxy_headers_parsing = true [oslo_messaging_notifications] driver = messaging [trust] trustee_domain_admin_name = magnum_domain_admin trustee_domain_admin_password = MAGNUM_DOMAIN_ADMIN_PASS trustee_domain_name = magnum trustee_keystone_interface = public 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.

1 0

[tripleo] Proposing Rabi Mishra part of tripleo-core
by Emilien Macchi 20 Jul '20

20 Jul '20

Hi folks, Rabi has proved deep technical understanding on the TripleO components over the last years. Initially as a major maintainer of the Heat project and then a regular contributor to TripleO, he got involved at different levels: - Optimization of the Heat templates, to reduce the number of resources or improve them to make it faster and more efficient at scale. - Migration of the Mistral workflows into native Ansible modules and Python code into tripleo-common, with end-to-end expertise. - Regular contributions to the container tooling integration. Being involved on the mailing-list and IRC channels, Rabi is always helpful to the community and here to help. He has provided thorough reviews in principal components on TripleO as well as a lot of bug fixes or new features; which contributed to make TripleO more stable and scalable. I would like to propose him be part of the TripleO core team. Thanks Rabi for your hard work! -- Emilien Macchi

13 14

[nova] Nova Gate is broken due to novnc issue in nova-next job
by Balázs Gibizer 20 Jul '20

20 Jul '20

Hi, Since Jul 18 the nova-next gate job is broken due to a novnc issue[1]. Hold your re-checks. Cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1888237

2 2

[glance] issues with glance functional tests at gate
by Abhishek Kekane 20 Jul '20

20 Jul '20

Hello All, It seems that something merged/released during the past weekend (late Friday) causing failure of glance functional tests. We are working on fixing the same, till then please refrain from adding recheck on the patches. Thank you, Abhishek Kekane

1 1

[neutron] Cancelling Monday July 20th weekly team IRC meeting
by Miguel Lavalle 20 Jul '20

20 Jul '20

Dear Neutrinos, I have an agenda conflict so I won't be able to run the weekly team IRC meeting. Let's skip for this week Best regards Miguel

1 0

[qa][dev][all] Gate issues with devstack glance standalone w/o tls-proxy
by Radosław Piliszek 20 Jul '20

20 Jul '20

Morning, Folks! It seems the devstack glance standalone mode (the new default) is broken at the moment if not using tls-proxy. If your jobs break on g-api not coming up, then this is the likely case. So far it seems to have hit Neutron and Nodepool jobs (and hence also SDK and DIB for example). Please refrain from rechecking until solved. -yoctozepto

3 3

[ironic] Cancelling meeting for this week
by Julia Kreger 20 Jul '20

20 Jul '20

Greetings everyone, Sorry for the late notice, but we have OpenDev[0] today which overlaps with our weekly meeting. Since the topic of OpenDev this week is on Hardware Automation, I anticipate most of us will be joining OpenDev this morning gathering new requirements and driving the discussion forward. Thanks everyone! Again, sorry for the late notice. -Julia -- [0] https://www.openstack.org/events/opendev-2020/opendev-schedule-2

1 0

RabbitMQ consumer connection is refused when trying to read notifications
by Anil Jangam 20 Jul '20

20 Jul '20

Hi, I followed the video and the steps provided in this video link and the consumer connection is being refused. https://www.openstack.org/videos/summits/denver-2019/nova-versioned-notific… /etc/nova/nova.conf file changes.. [notifications] notify_on_state_change=vm_state default_level=INFO notification_format=both [oslo_messaging_notifications] driver=messagingv2 transport_url=rabbit://guest:guest@10.30.8.57:5672/ topics=notification retry=-1 The python consume code is as follows (followed the example provided in the video: transport = oslo_messaging.get_notification_transport( cfg.CONF, url='rabbit://guest:guest@10.30.8.57:5672/') targets = [ oslo_messaging.Target(topic='versioned_notifications'), ] Am I missing any other configuration in any of the services in OpenStack? Let me know if you need any other info. /anil.

2 2

[stein][watcher] Running watcher with sample Audit templates
by Sanjay K 19 Jul '20

19 Jul '20

Hello Watcher-dev, Would you please give any pointers on how to run watcher successfully based on my query posted at - ask.openstack.org <https://ask.openstack.org/en/question/128530/running-watcher-audit-template…> If the metric cpu_util is deprecated in the past, how are these sample templates given in the Watcher Stein release going to work? Whether I have to do anything to replace these kinds of deprecated metrics in watcher? Thank you for your help and support. Best regards, Sanjay

1 0

[neutron] Bug deputy report for week of July 13th
by Lajos Katona 19 Jul '20

19 Jul '20

Hi, I was Neutron bug deputy last week. A short summary of the reported bugs: - High bugs - https://bugs.launchpad.net/neutron/+bug/1887815 Neutron API - problem parsing semi-colon in Accept header - In Progress / Assigned - https://bugs.launchpad.net/neutron/+bug/1887992 [neutron-tempest-plugin] glance service failing during the installation - Fixed in Devstack - Medium bugs - https://bugs.launchpad.net/neutron/+bug/1887523 Deadlock detection code can be stale - In Progress (use oslo.b deadlock handling) => https://review.opendev.org/740977 - https://bugs.launchpad.net/neutron/+bug/1887281 [linuxbridge] ebtables delete arp protect chain fails - In Progress / Assigned => https://review.opendev.org/740588 - https://bugs.launchpad.net/neutron/+bug/1887405 Race condition while processing security_groups_member_updated events (ipset) - Unassigned - Low bugs - https://bugs.launchpad.net/neutron/+bug/1887778 neutron-ovn-migration-mtu does not support specifying project/user domain name - Assigned / In Progress => https://review.opendev.org/741410 - https://bugs.launchpad.net/neutron/+bug/1887781 neutron-ovn-migration-mtu does not adjust mtu on gre-networks - Assigned / In Progress => https://review.opendev.org/741414 - https://bugs.launchpad.net/neutron/+bug/1887385 String to byte conversion should provide the encoding type - Assigned / In progress => https://review.opendev.org/740693 - RFE - https://bugs.launchpad.net/neutron/+bug/1887497 Cleanup stale flows by cookie and table_id instead of just by cookie Only 1 is that still unassigned and some more checks are needed: https://bugs.launchpad.net/neutron/+bug/1887405 Lajos (lajoskatona)

1 0

[Zaqar][Project-Update]Encrypted Messages in Queue is coming !
by hao wang 19 Jul '20

19 Jul '20

Hi, stackers, In Victoria, the queue in Zaqar will support to encrypt messages before storing them into storage backends, also could support to decrypt (or not) messages when those are claimed by consumer. This feature will enhance the security of the messaging service. As you may know, currently, Zaqar can't encrypt any messages and just store those messages into storage backends. That'll bring some security issues like information leakage or hacker attack. So depending on this feature, we have a basic mechanism to protect user's data from those security threats. Now we will support the encryption algorithm AES-256 at first, we consider bringing more capacities in the future like supporting RSA and letting users chose what they want to use. Finding more details in [1] and now the code patch is ready for reviewing [2]. Welcome to anyone who's interested in this new feature! [1]https://review.opendev.org/#/c/731102/4 [2]https://review.opendev.org/#/c/738736/

1 0

Re: Floating IP's for routed networks
by Thomas Goirand 18 Jul '20

18 Jul '20

Hi Ryan, If you don't mind, I'm adding the openstack-discuss list in the loop, as this topic may be of interest to others. For mailing list readers, I'm trying to implement this: https://review.opendev.org/#/c/669395/ but I'm having some difficulties. I did a bit of investigation with some added LOG.info() in the code. When doing: > openstack subnet create vm-fip \ > --subnet-range 10.66.20.0/24 \ > --service-type 'network:routed' \ > --service-type 'network:floatingip' \ > --network multisegment1 Here's where neutron-api crashes. in db/ipam_backend_mixin.py: def _validate_segment(self, context, network_id, segment_id, action=None, old_segment_id=None): # TODO(tidwellr) Create and use a constant for the service type segments = subnet_obj.Subnet.get_subnet_segment_ids( context, network_id, filtered_service_type='network:routed') associated_segments = set(segments) if None in associated_segments and len(associated_segments) > 1: raise segment_exc.SubnetsNotAllAssociatedWithSegments( network_id=network_id) SubnetsNotAllAssociatedWithSegments() is raised, as you must already guessed. Here's the values... associated_segments is an array containing 3 values: 2 being the IDs of the segments I added previously, the 3rd one being None. This test is then matched. Where is that None value coming from? Is this the new subnet I'm trying to add? Maybe the filtered_service_type='network:routed' in the call: subnet_obj.Subnet.get_subnet_segment_ids() isn't working as expected? Printing the SQL query that is checked shows: SELECT subnets.segment_id AS subnets_segment_id FROM subnets WHERE subnets.network_id = %(network_id_1)s AND subnets.id NOT IN (SELECT subnet_service_types.subnet_id AS subnet_service_types_subnet_id FROM subnet_service_types WHERE subnets.network_id = %(network_id_2)s AND subnet_service_types.subnet_id = subnets.id AND subnet_service_types.service_type = %(service_type_1)s) though when doing by hand: SELECT subnets.segment_id AS subnets_segment_id FROM subnets the db has only 2 subnets, so it looks like the floating-ip subnet got added before the check, and is then removed when the above test fails. So I just removed the raise, and could add the subnet I wanted, but that's obviously not a long term solution. Your thoughts? Another problem that I'm having, is that neutron-bgp-dragent is not receiving (or processing) the messages from neutron-rpc-server. I've enabled DEBUG mode for oslo_messaging, and found out that when dr-agent starts and prints "Agent has just been revived. Scheduling full sync", it does send a message to neutron-rpc-server, which is replied, but it doesn't look like dr-agent processes the return message in its reply queue, and then prints in the logs: "imeout in RPC method get_bgp_speakers. Waiting for 17 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID c1b401c9e10d481bb5e071f2c048e480". What is weird is that a few times (rarely), it worked, and the agent gets the reply. What should I do to investigate further? Cheers, Thomas Goirand (zigo)

3 4

SDK API to get the version of openstack distribution
by Anil Jangam 17 Jul '20

17 Jul '20

Hi, I am able to iterate through the list of hypervisors and servers as follows. for hypervisor in self.connection.list_hypervisors(): for server in self.connection.compute.servers(): However, I could not find an API that returns the version of the OpenStack i.e. whether it is Stein, Train, or Ussuri. Openstack CLI client has command: openstack versions show Thanks, /anil.

1 0

[octavia] Proposal to deprecate the amphora spares pool
by Michael Johnson 17 Jul '20

17 Jul '20

Back at the Victoria PTG the Octavia team discussed deprecating the spares pool capability of the amphora driver[1]. This would follow the standard OpenStack deprecation process[2]. There are a number of reasons this was proposed: 1. It adds a lot of complexity to the code. 2. It can't be used with Active/Standby load balancers due to server group (anti-affinity) limitations in Nova. 3. It provides only 15-30 seconds of speedup when provisioning a new load balancer on production clouds. 4. It makes supporting Octavia availability zones awkward as we have to boot spares instances in each AZ. 5. It can be confusing for people when it is enabled as there are always extra amphora running and being automatically recreated. Due to these reasons a patch has been proposed to deprecate spares pool support in the amphora driver: https://review.opendev.org/741686 Please comment on that patch and/or join the weekly Octavia IRC meeting if you have any concerns with this deprecation plan. Michael [1] https://etherpad.opendev.org/p/octavia-virtual-V-ptg [2] https://governance.openstack.org/tc/reference/tags/assert_follows-standard-…

1 0