- openstack-discuss - lists.openstack.org

[nova] nova stable pike|queens|rocky is still failing on Tempest u-c: Do not recheck
by Ghanshyam Mann 09 Feb '20

09 Feb '20

After fixing the stable/pike|queens|rocky integrated jobs[1], on using the stable u-c for pinned Tempest run, nova-live-migration fail on these stable branch on nova. I have proposed the fixes[2], wait for recheck till those are merged. [1] https://review.opendev.org/#/q/topic:fix-stable-gate+status:merged [2] https://review.opendev.org/#/q/topic:fix-stable-gate+status:open+projects:o… -gmann

1 0

[qa][stable][tempest-plugins]: Tempest & plugins py2 jobs failure for stable branches (1860033: the EOLing python2 drama)
by Ghanshyam Mann 09 Feb '20

09 Feb '20

Hello Everyone, This is regarding bug: https://bugs.launchpad.net/tempest/+bug/1860033. Using Radosław's fancy statement of 'EOLing python2 drama' in subject :). neutron tempest plugin job on stable/rocky started failing as neutron-lib dropped the py2. neutron-lib 2.0.0 is py3 only and so does u-c on the master has been updated to 2.0.0. All tempest and its plugin uses the master u-c for stable branch testing which is the valid way because of master Tempest & plugin is being used to test the stable branches which need u-c from master itself. These failed jobs also used master u-c[1] which is trying to install the latest neutron-lib and failing. This is not just neutron tempest plugin issue but for all Tempest plugins jobs. Any lib used by Tempest or plugins can drop the py2 now and leads to this failure. Its just neutron-lib raised the flag first before I plan to hack on Tempest & plugins jobs for py2 drop from master and kepe testing py2 on stable bracnhes. We have two way to fix this: 1. Separate out the testing of python2 jobs with python2 supported version of Tempest plugins and with respective u-c. For example, test all python2 job with tempest plugin train version (or any latest version if any which support py2) and use u-c from stable/train. This will cap the Tempest & plugins with respective u-c for stable branches testing. 2. Second option is to install the tempest and plugins in py3 env on py2 jobs also. This should be an easy and preferred way. I am trying this first[2] and testing[3]. [1] https://zuul.opendev.org/t/openstack/build/fb8a928ed3614e09a9a3cf4637f2f6c2… [2] https://review.opendev.org/#/c/703011/ [3] https://review.opendev.org/#/c/703012/ -gmanne

5 17

[all] Gate status: Stable/ocata|pike|queens|rocky is broken: Avoid recheck
by Ghanshyam Mann 09 Feb '20

09 Feb '20

Hello Everyone, Stable/ocata, pike, queens, rocky gate is broken now due to Temepst dependency require >=py3.6. I summarized the situation in ML[1]. Do not recheck on failed patches of those branches until the job is explicitly disabling Tempest. Fixes are in progress, I will update the status here once fixes are merged. [1]http://lists.openstack.org/pipermail/openstack-discuss/2020-February/0123… -gmann

1 1

Regarding OpenStack
by HARISH KUMAR Ivaturi 09 Feb '20

09 Feb '20

Hi I am Harish Kumar, Master Student at BTH, Karlskrona, Sweden. I have started my Master thesis at BTH and my thesis topic is Performance evaluation of OpenStack with HTTP/3. My solutions will take some time (few months) and i would like to request you that could you add me as a contributor to your github repository , so after completing my thesis i could push my codes in that repository. You can contact me for further details. Thanks and Regards Harish Kumar

2 1

[cinder][nova] volume-local-cache meeting day/time set
by Brian Rosmaita 09 Feb '20

09 Feb '20

I picked the day/time with the most votes (9/10, sorry Rajat), but as gibi pointed out in the other thread, it may not have been obvious what you actually voted for. The good news is that the selected day is late in the week, so if you look at this time and say WTF?, let me know and we can scramble to try to find another day/time (though hopefully not--we're trying to find a time that works stretching from Minneapolis to Shanghai). Meeting time: 13:30-14:00 UTC Thursday 13 February 2020 Location: https://bluejeans.com/3228528973 Topic: volume-local-cache specs: cinder: https://review.opendev.org/#/c/684556/ nova: https://review.opendev.org/#/c/689070/ Etherpad: https://etherpad.openstack.org/p/volume-local-cache The meeting will be recorded. Feel free to leave comments on the etherpad if you can't make it but want something addressed. cheers, brian

2 1

[cinder][nova] volume-local-cache proposal cross-project meeting
by Brian Rosmaita 08 Feb '20

08 Feb '20

Liang Fang's volume-local-cache spec has gotten stuck because the Cinder team doesn't want to approve something that won't get approved on the Nova side and vice-versa. We discussed the spec at this week's Cinder meeting and there's sufficient interest to continue with it. In order to keep things moving along, we'd like to have a cross-project video conference next week instead of waiting for the PTG. I think we can get everything covered in a half-hour. I've put together a doodle poll to find a reasonable day and time: https://doodle.com/poll/w8ttitucgyqwe5yc Please take the poll before 17:00 UTC on Saturday 8 February. I'll send out an announcement shortly after that letting you know what time's been selected. I'll send out connection info once the meeting's been set. The meeting will be recorded and interested parties who can't make it can always leave notes on the discussion etherpad. Info: - cinder spec: https://review.opendev.org/#/c/684556/ - nova spec: https://review.opendev.org/#/c/689070/ - etherpad: https://etherpad.openstack.org/p/volume-local-cache cheers, brian

2 2

[Queens][neutron] multiple networks with same vlan id
by Ignazio Cassano 08 Feb '20

08 Feb '20

Hello, I trying to create multiple networks with the same vlan id and different address but it is impossibile because neutron returns vlan id is already present. I tried with success on vcenter and it works. On openstack I can create more subnets with different adresses under the same vlan id, but instances receive static routes from dhcp for all subnets. Any workaround ? I am also trying with segments but they do not seem to fit my case. Regards Ignazio

4 5

[quuens] neutron vxlan to vxlan
by Ignazio Cassano 08 Feb '20

08 Feb '20

Hello, I have an openstack installation and a vcenter installation with nsxv. Vcenter is not under openstack Any solution for vxlan to vxlan communication between them? Regards Ignazio

2 2

Re: [Release-job-failures] Release of openstack/mox3 for ref refs/tags/1.0.0 failed
by Sean McGinnis 07 Feb '20

07 Feb '20

On Fri, Feb 07, 2020 at 01:16:38PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-python https://zuul.opendev.org/t/openstack/build/720dc1833f464e2db76b90d1c8437883 : SUCCESS in 3m 48s > - announce-release https://zuul.opendev.org/t/openstack/build/d85b18ed6e2a47f98e96c1ad168ae98a : FAILURE in 4m 00s > - propose-update-constraints https://zuul.opendev.org/t/openstack/build/c2abc022840846c7a87b5804580492ee : SUCCESS in 3m 51s > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures There was a temporary SMTP failure in sending the release announcement for mox3. All other release activities were successful, so I think this error can safely be ignored. Sean

1 0

[all] Nominations for the "W" release name
by Sean McGinnis 07 Feb '20

07 Feb '20

Hello all, We get to be a little proactive this time around and get the release name chosen for the "W" release. Time to start thinking of good names again! Process Changes --------------- There are a couple of changes to be aware of with our naming process. In the past, we had always based our naming criteria on something geographically local to the Summit location. With the event changes to no longer have two large Summit-type events per year, we have tweaked our process to open things up and make it hopefully a little easier to pick a good name that the community likes. There are a couple of significant changes. First, names can now be proposed for anything that starts with the appropriate letter. It is no longer tied to a specific geographic region. Second, in order to simplify the process, the electorate for the poll will be the OpenStack Technical Committee. Full details of the release naming process can be found here: https://governance.openstack.org/tc/reference/release-naming.html Name Selection -------------- With that, the nomination period for the "W" release name is now open. Please add suitable names to: https://wiki.openstack.org/wiki/Release_Naming/W_Proposals We will accept nominations until February 7, 202 at 23:59:59 UTC. We will then have a brief period for any necessary discussions and to get the poll set up, with the TC electorate voting starting by February 17, 2020 and going no longer than February 23, 2020. Based on past timing with trademark and copyright reviews, we will likely have an official release name by mid to late March. Happy naming! Sean

2 2

[Neutron][segments]
by Ignazio Cassano 07 Feb '20

07 Feb '20

Hello, I am reading about openstack neutron routed provider networks. If I understood well, using segments I can create more subnets within the same provider net vlan id. Correct? In documentation seems I must use different physical network for each segment. I am using only one physical network ...in other words I created an openvswitch with a bridge (br-ex) with an interface on which I receive all my vlans (trunk). Why must I use different physical net? Sorry, but my net skill is poor. Ignazio

2 2

[keystone] Keystone Team Update - Week of 3 February 2020
by Vishakha Agarwal 07 Feb '20

07 Feb '20

# Keystone Team Update - Week of 3 February 2020 ## News ### User Support and Bug Duty Every week the duty is being rotated between the members. The person-in-charge for bug duty for current and upcoming week can be seen on the etherpad [1] [1] https://etherpad.openstack.org/p/keystone-l1-duty ## Open Specs Ussuri specs: https://bit.ly/2XDdpkU Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 13 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 27 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Ussuri Roadmap Stories - Groups in keystone SAML assertion https://tree.taiga.io/project/keystone-ussuri-roadmap/us/33 https://review.opendev.org/#/c/588211/ Add openstack_groups to assertion - Add support for modifying resource options to CLI tool https://tree.taiga.io/project/keystone-ussuri-roadmap/us/53 https://review.opendev.org/#/c/697444/ Adding options to user cli * Special Requests https://review.opendev.org/#/c/705887/ Drop py3.5 from tempest plugins ## Bugs This week we opened 2 new bugs and closed 3. Bugs opened (2) Bug #1861695 (keystoneauth:Undecided): Programming error choosing an endpoint. - Opened by Raphaël Droz https://bugs.launchpad.net/keystoneauth/+bug/1861695 Bug #1862035 (keystoneauth:Undecided): Make possible to pass TCP_USER_TIMEOUT in keystoneauth1 session - Opened by Anton Kurbatov https://bugs.launchpad.net/keystoneauth/+bug/1862035 Bugs closed (3) Bug #1756190 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1756190 Bug #1853839 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1853839 Bug #1856286 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1856286 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Next week is spec freeze. One month from now is feature proposal freeze, by which point all code for new features should be proposed and ready for review - no WIPs. This will give us 4 weeks to review. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

[tripleo] no rechecks
by Chandan kumar 07 Feb '20

07 Feb '20

Hello, TripleO jobs are failing with following bug. upstream tripleo jobs using os_tempest failing with ERROR: No matching distribution found for oslo.db===7.0.0 -> https://bugs.launchpad.net/tripleo/+bug/1862134 Fix is in progress: https://review.opendev.org/#/c/706196/ We need this patch to land before it's safe to blindly recheck. We appreciate your patience while we resolve the issues. Thanks, Chandan Kumar

1 1

[all][PTL][tc] U Community Goal: Project PTL & Contrib Docs Update #1
by Kendall Nelson 07 Feb '20

07 Feb '20

Hello All! At last a dedicated update solely to the Contrib & PTL Docs community goal! Get excited :) At this point the goal has been accepted[1], and the template[2] has been created and merged! So, the next step is for all projects to use the cookiecutter template[2] and fill in the extra details after you generate the .rst that should auto populate some of the information. As you are doing that, please assign yourself the associated tasks in the story I created[3]. If you have any questions or concerns, please let me know! -Kendall Nelson (diablo_rojo) [1] Goal: https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-c… [2] Docs Template: https://opendev.org/openstack/cookiecutter/src/branch/master/%7b%7bcookiecu… [3] Tracking: https://storyboard.openstack.org/#!/story/2007236

2 2

[neutron][ptg] Vancouver attendance and planning
by Slawek Kaplonski 07 Feb '20

07 Feb '20

Hi Neutrinos, As You probably know, Victoria PTG will be in Vancouver in June. I have been asked by organisers how much space and time we will need for Neutron so I started etherpad [1]. Please put there Your name if You are planning to go to Vancouver. Even if it’s not confirmed yet. I need to have number of people before Sunday, March 2nd. Also if You have any ideas about topics which we should discuss there, please write them in this etherpad too. [1] https://etherpad.openstack.org/p/neutron-victoria-ptg — Slawek Kaplonski Senior software engineer Red Hat

1 0

[all][requirements][monasca][gnocchi] ujson, not maintained for over 4 years, has compiler issues
by Radosław Piliszek 06 Feb '20

06 Feb '20

This is a spinoff discussion of [1] to attract more people. As the subject goes, the situation of ujson is bad. Still, monasca and gnocchi (both server and client) seem to be using it which may break depending on compiler. The original issue is that the released version of ujson is in non-spec-conforming C which may break randomly based on used compiler and linker. There has been no release of ujson for more than 4 years. Based on general project activity, Monasca is probably able to fix it but Gnocchi not so surely... [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-January/thread.… -yoctozepto

5 10

[nova][ptg] Vancouver Planning
by Eric Fried 06 Feb '20

06 Feb '20

Nova- I've started an etherpad for the Victoria PTG [1]. I've been asked to let the organizers know how much space and time we're going to need within the next few weeks, so please register your attendance and add any topics you know of as soon as possible. Thanks, efried [1] https://etherpad.openstack.org/p/nova-victoria-ptg

1 0

[nova] Ussuri spec push (and scrub)
by Eric Fried 06 Feb '20

06 Feb '20

Hi all. Ahead of spec freeze next Thursday (Feb 13) we've agreed to do a review day next Tuesday, Feb 11th. If you own a blueprint [1] that isn't already Design:Approved (there are 20 as of this writing) and are still interested in landing it in Ussuri, please make sure your spec is review-ready, and plan to be present in #openstack-nova on Tuesday so we can work through any issues quickly. If you are a nova maintainer, please plan as much time as possible on Tuesday to review open specs [2] and discuss them in IRC. As a reminder, soon after spec freeze I would like to scrub the list of Design:Approved blueprints ("if we're going to do this, here's how") to decide which should be Direction:Approved ("we're going to do this in Ussuri") and which should be deferred. I will send a separate email about this after the milestone. Thanks, efried [1] https://blueprints.launchpad.net/nova/ussuri [2] https://review.opendev.org/#/q/project:openstack/nova-specs+path:%255Especs…

1 0

[tc] February meeting agenda
by Rico Lin 06 Feb '20

06 Feb '20

Hello everyone, Our next meeting is happening this Thursday (the 6th), and the agenda is, as usual, on the wiki! Here is a primer of the agenda for this month: - Report on large scale sig - Report on tc/uc merge - report on the post for the analysis of the survey - Report on the convo Telemetry - Report on multi-arch SIG - report on infra liaison and static hosting - report on stable branch policy work - report on the oslo metrics project - report on the community goals for U and V, py2 drop - report on release naming - report on the ideas repo - report on charter change - Report on whether SIG guidelines worked - volunteers to represent OpenStack at the OpenDev advisory board - Report on the OSF board initiatives - Dropping side projects: using golden signals See you all in meeting:) -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 1

[openstack-dev][kuryr] Not working in ARM64 (as Node)
by VeeraReddy 06 Feb '20

06 Feb '20

Hi,I am trying to run kubelet in arm64 platform1. Generated kuryr-cni successfullly. using kur-cni Dockerfile2. Generated kuryr-cni-arm64 container.3. my kube-kuryr-arm64.yml (http://paste.openstack.org/show/789208/) My master node in x86 installed successfully using devstack While running kubelet in arm platform , not able to create kubelet interface (kubelet logs: http://paste.openstack.org/show/789206/) COntroller logs: http://paste.openstack.org/show/789209/ Please help me to fix the issue Veera. Regards, Veera.

2 3

[ops][cinder] Moving volume to new type
by Jonathan Proulx 06 Feb '20

06 Feb '20

Hi All, I'm currently languishing on Mitaka so perhaps further back than help can reach but...if anyone can tell me if this is something dumb I'm doing or a know bug in mitaka that's preventing me for movign volumes from one type to anyother it'd be a big help. In the further past I did a cinder backend migration by creating a new volume type then changing all the existign volume sto the new type. This is how we got from iSCSI to RBD (probably in Grizzly or Havana). Currently I'm starting to move from one RBD pool to an other and seems like this should work in the same way. Both pools and types exist and I can create volumes in either but when I run: openstack volume set --type ssd test-vol it rather silently fails to do anything (CLI returns 0), looking into schedulerlogs I see: # yup 2 "hosts" to check DEBUG cinder.scheduler.base_filter Starting with 2 host(s) get_filtered_objects DEBUG cinder.scheduler.base_filter Filter AvailabilityZoneFilter returned 2 host(s) get_filtered_objects DEBUG cinder.scheduler.filters.capacity_filter Space information for volume creation on host nimbus-1@ssdrbd#ssdrbd (requested / avail): 8/47527.78 host_passes DEBUG cinder.scheduler.base_filter Filter CapacityFilter returned 2 host(s) get_filtered_objects /usr/lib/python2.7/dist-packages/cinder/scheduler/base DEBUG cinder.scheduler.filters.capabilities_filter extra_spec requirement 'ssdrbd' does not match 'rbd' _satisfies_extra_specs /usr/lib/python2.7/dist- DEBUG cinder.scheduler.filters.capabilities_filter host 'nimbus-1@rbd#rbd': free_capacity_gb: 71127.03, pools: None fails resource_type extra_specs req DEBUG cinder.scheduler.base_filter Filter CapabilitiesFilter returned 1 host(s) get_filtered_objects /usr/lib/python2.7/dist-packages/cinder/scheduler/ # after filtering we have one DEBUG cinder.scheduler.filter_scheduler Filtered [host 'nimbus-1@ssdrbd#ssdrbd': free_capacity_gb: 47527.78, pools: None] _get_weighted_candidates # but it fails? ERROR cinder.scheduler.manager Could not find a host for volume 49299c0b-8bcf-4cdb-a0e1-dec055b0e78c with type bc2bc9ad-b0ad-43d2-93db-456d750f194d. successfully creating a volume in ssdrbd is identical to that point, except rather than ERROR on the last line it goes to: # Actually chooses 'nimbus-1@ssdrbd#ssdrbd' as top host DEBUG cinder.scheduler.filter_scheduler Filtered [host 'nimbus-1@ssdrbd#ssdrbd': free_capacity_gb: 47527.8, pools: None] _get_weighted_candidates DEBUG cinder.scheduler.filter_scheduler Choosing nimbus-1@ssdrbd#ssdrbd _choose_top_host # then goes and makes volume DEBUG oslo_messaging._drivers.amqpdriver CAST unique_id: 1b7a9d88402a41f8b889b88a2e2a198d exchange 'openstack' topic 'cinder-volume' _send DEBUG cinder.scheduler.manager Task 'cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create' (e70dcc3f-7d88-4542-abff-f1a1293e90fb) transitioned into state 'SUCCESS' from state 'RUNNING' with result 'None' _task_receiver Anyone recognize this situation? Since I'm retiring the old spinning disks I can also "solve" this on the Ceph side by changing the crush map such that the old rbd pool just picks all ssds. So this isn't critical, but in the transitional period until I have enough SSD capacity to really throw *everything* over, there are some hot spot volumes it would be really nice to move this way. Thanks, -Jon

2 1

[charms] modular deployment
by Florian Rommel 06 Feb '20

06 Feb '20

Hi, we are starting to look into deploying Openstack with Charms ,however there seems to be NO documentation on how to separate ceph osd and mon out of the Openstack-base bundle. We already have a ceph cluster so we would like to reuse that instead of hyperconverging. Is there any way do do this with charms or do we need to look into openstack ansible? Thank you and best regards, //F

2 2

Active-Active Cinder + RBD driver + Co-ordination
by Paul Browne 06 Feb '20

06 Feb '20

Hi list, I had a quick question about Active-Active in cinder-volume and cinder-backup stable/stein and RBD driver, if anyone can help. Using only the Ceph RBD driver for volume backends, is it required to run A-A cinder services with clustering configuration so that they form a cluster? And, if so, is an external coordinator (redis/etcd/Consul) necessary, again only using RBD driver? Best docs I could find on this so far were; https://docs.openstack.org/cinder/latest/contributor/high_availability.html , I support more aimed at devs/contributoers than operators, but it's not 100% clear to me on these questions Thanks, Paul -- ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk Tel: 0044-1223-746548 *******************

2 1

Re: [queens]cinder][iscsi] issue
by Ignazio Cassano 06 Feb '20

06 Feb '20

Hello , On centos kvm nodes, setting skip_kpartx no in multipath.conf solved the problem and now os_brick can flush maps Ignazio Il giorno lun 3 feb 2020 alle ore 15:13 Ignazio Cassano < ignaziocassano(a)gmail.com> ha scritto: > Hello all we are testing openstack queens cinder driver for Unity iscsi > (driver cinder.volume.drivers.dell_emc.unity.Driver). > > The unity storage is a Unity600 Version 4.5.10.5.001 > > We are facing an issue when we try to detach volume from a virtual machine > with two or more volumes attached (this happens often but not always). > > We also facing the same issue live migrating a virtual machine. > > > Multimaph -f does not work because it returns "map in use" and the volume > is not detached. > > Attached here there hare nova-compute e volume logs in debug mode. > > Could anyone help me ? > > Ignazio > > >

1 0

[kolla] All services stats DOWN after re-launch whole cluster.
by Eddie Yen 06 Feb '20

06 Feb '20

Hi everyone, We have the Kolla Openstack site, which is 3 HCI (Controller+Compute) + 3 Storage (Ceph OSD) site without internet. We did the shutdown few days ago since CNY holidays. Today we re-launch whole cluster back. First we met the issue that MariaDB containers keep restarting, and we fixed by using mariadb_recovery command. After that we check the status of each services, and found that all services shown at Admin > System > System Information are DOWN. Strange is no MariaDB, AMQP connection, or other error found when check the downed service log. We tried reboot each servers but the situation still a same. Then we found the RabbitMQ log not updating, the last log still stayed at the date we shutdown. Logged in to RabbitMQ container and type "rabbitmqctl status" shows connection refused, and tried access its web manager from <VIP>:15672 on browser just gave us "503 Service unavailable" message. Also no port 5672 listening. I searched this issue on the internet but only few information about this. One of solution is delete some files in mnesia folder, another is remove rabbitmq container and its volume then re-deploy. But both are not sure. Does anyone know how to solve it? Many thanks, Eddie.

4 8