September 2019 - openstack-discuss

Outreachy Application Deadline - Call for mentors and projects
by Samuel de Medeiros Queiroz 17 Sep '19

17 Sep '19

Hi everyone! Outreachy <https://www.outreachy.org/> helps people from underrepresented groups get involved in free and open source software by matching interns with established mentors in the upstream communities. OpenStack is a participating organization in the Outreachy Dec 2019 to Mar 2020 round. If you're interested to be a mentor, please register as a mentor in the Outreachy website and publish your project ideas. According to this round's schedule <https://www.outreachy.org/docs/applicant/#outreachy-schedule>, the initial application is due next week: - *Sept. 24, 2019 at 4pm UTC Initial application deadline * - *Nov. 5, 2019 at 4pm UTC Final application deadline* It is important to get projects submitted *as soon as possible* so that applicants can sign up before the *Sept. 24 deadline*. Once signed up, they will have between *Oct. 1, 2019 to Nov. 5, 2019 to contribute to the projects*. If you have any questions about becoming a mentor or want to sponsor an intern, please contact me (samueldmq(a)gmail.com) or Mahati Chamarthy ( mahati.chamarthy(a)gmail.com). Thank you, Samuel de Medeiros Queiroz

1 0

[sdk][release][requirements] FFE requested for openstacksdk
by Monty Taylor 17 Sep '19

17 Sep '19

Heya, We’d like to cut an 0.35.1 bugfix release as part of train to grab https://review.opendev.org/#/c/680649/ and https://review.opendev.org/#/c/682454/. The first is landed and is in support of the Ironic Nova driver. The second is making its way through the gate right now and is in support of OSC v4. Thanks! Monty

3 4

[zuul3] zuul2 -> zuul3 migration
by Lenny Verkhovsky 17 Sep '19

17 Sep '19

Hi Team, We would like to migrate our Third Party CI[1] from zuul2 to zuul3. We have a lot of Jenkins jobs initially based on infra project-config-example But I guess we need to re write all the jobs now to support ansible. Any guide/example/tips are highly appreciated. [1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI [2] https://github.com/openstack-infra/project-config-example/tree/master/jenki… Best Regards Lenny Verkhovsky (aka lennyb) Mellanox Technologies<http://www.mellanox.com/> office: +972 74 712 92 44 fax: +972 74 712 91 11 mobile: +972 54 554 02 33 irc: lennyb

2 2

[requirements] Issues while trying to bump-up ovsdbapp requirement for stable/queens
by Maciej Jozefczyk 17 Sep '19

17 Sep '19

Hello, I'm trying to bump-up ovsdbapp requirement in networking-ovn [0] from 0.8.0 [1] to 0.10.4 [2]. Those two are in the same stable/queens release and we need that change to merge some serious performance improvements to stable/queens. Unfortunately the requirements-check jobs fails on this change [3] with: Requirement for package ovsdbapp : Requirement(package=u'ovsdbapp', location='', specifiers='>=0.10.4', markers=u'', comment=u'# Apache-2.0', extras=frozenset([])) does not match openstack/requirements value : set([Requirement(package='ovsdbapp', location='', specifiers='>=0.8.0', markers='', comment='# Apache-2.0', extras=frozenset([]))]) The only place where >=0.8.0 is set is global-requirements [4]. Do we need to bump up it also there, even the upper-requirements bot proposal [5] has been merged? It is string match? I proposed a change to bump it in global-requirements [6]. Thanks, Maciej [0] https://review.opendev.org/#/c/681562/ [1] https://github.com/openstack/ovsdbapp/releases/tag/0.8.0 [2] https://github.com/openstack/ovsdbapp/releases/tag/0.10.4 [3] https://bb8048f0749367929365-38c02a6f4c2535c3f3f9bfdb5440d261.ssl.cf1.rackc… [4] https://github.com/openstack/requirements/blob/stable/queens/global-require… [5] https://review.opendev.org/#/c/682323 [6] https://review.opendev.org/#/c/682588 -- Best regards, Maciej Józefczyk

2 2

[os-win][requirements] FFE requested for os-win
by Lucian Petrut 17 Sep '19

17 Sep '19

Hi, I’d like to request a FFE for os-win. One important bug fix has missed the train (4.3.1) release, for which reason we’d need to have a subsequent one. The bug in question prevents Nova from starting after host reboots when using the Hyper-V driver on recent Windows Server 2019 builds. Thanks, Lucian Petrut

2 1

[oslo] Stepping down from core reviewer
by ChangBo Guo 17 Sep '19

17 Sep '19

Hi folks, I no longer have the time to contribute to Oslo in a meaningful way in past few months, due to the company internal stuff, and would like to step down from core reviewer. It was an honor to be one of the great team since 4 years ago. I still work on OpenStack, just have no enough time to focus on Oslo. I hope have more time to contribute again in the future :-) All the best! -- ChangBo Guo(gcb)

2 1

[all] stable/ocata gate failure
by Ghanshyam Mann 17 Sep '19

17 Sep '19

Hello Everyone, If you have noticed that stable/ocata gate is blocked where 'legacy-tempest-dsvm-neutron-full/-*' job is failing due to the latest Tempest changes. Tempest started the JSON schema strict validation for Volume APIs which caught the failure or you can say Tempest master cannot be used in Ocata testing. More details- https://bugs.launchpad.net/tempest/+bug/1843762 As per the Tempest stable branch testing policy[1], Tempst does not support the stable/ocata (which is EM )in the current development cycle. Current supported stable branches by Tempest are Queens, Rocky, Stein and Train-on-going. We can keep using Tempest master on EM stable/branches as long as it run successfully and if it start failing which is current case of stable/ocata then use Tempest tag to test that EM stable branch. To unblock the stable/ocata gate, I am trying to install the Tempest 20.0.0(compatible version for Ocata) in ocata gate - https://review.opendev.org/#/c/681950/ Fix is not working as of now (it still install Tempest master). I will debug that later (my current priority is for Train feature freeze). [1] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html -gmann

2 3

[all] Please do not bump openstackdocstheme minimum version if possible
by Thomas Goirand 17 Sep '19

17 Sep '19

Hi, The openstackdocstheme package in Debian is highly modified, because otherwise, building docs just fail. Namely, we have reverted commit d87aaca30f64502b3dd13cc1ddf46beec90fc015 because otherwise, the docs wouldn't build. Rebasing it is *very* annoying. So, it'd be nice if packages didn't depend on the very latest version of openstackdocstheme so we could keep version 1.20.0. I don't think it's that important to depend on the very latest version (please let me know if I'm wrong, and let me know why). Cheers, Thomas Goirand (zigo)

3 3

[kolla] Support Octavia for ubuntu binary on stable/rocky?
by Eddie Yen 17 Sep '19

17 Sep '19

Hi, I'm trying to install Octavia in Rocky release with Ubuntu binary distro. And found that there're no docker images for Ubuntu binary. Then I checked the Kolla dockerfile and found that it will not build the image since it's not support yet. But I found that the Ubuntu Cloud Archive Team has already putted Octavia packages into cloud repository [1]. Since some images built using from this PPA, I think it can support ubuntu binary in Rocky release. I tried put package code into Docker files and build, but it gave me an error message like below: ERROR:kolla.common.utils:octavia-api Failed with status: matched ERROR:kolla.common.utils:octavia-health-manager Failed with status: matched ERROR:kolla.common.utils:octavia-housekeeping Failed with status: matched ERROR:kolla.common.utils:octavia-worker Failed with status: matched So I think there's limit somewhere. How can I release it? Thanks, Eddie. [1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/rocky-staging

2 4

Rabbitmq error report
by Md. Farhad Hasan Khan 17 Sep '19

17 Sep '19

Hi, I'm getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this. rabbitmq version: rabbitmq_server-3.6.16 =ERROR REPORT==== 12-Sep-2019::13:04:55 === Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1: operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout =WARNING REPORT==== 12-Sep-2019::13:04:55 === closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'): client unexpectedly closed TCP connection Thanks & B'Rgds, Rony

3 4