September 2019 - openstack-discuss

[neutron] Bug deputy report week of September 9th
by Miguel Lavalle 15 Sep '19

15 Sep '19

Hi, I was the bug deputy for the week of September 9th. Here's the list of what we got reported: Critical: - https://bugs.launchpad.net/neutron/+bug/1843413 neutron-tempest-iptables_hybrid-fedora job is failing with RETRY_LIMIT constantly Status: Assigned to slaweq. Job was made non-voting temporarily while bug is fixed High: - https://bugs.launchpad.net/neutron/+bug/1843478 Mitigate frequent fixtures._fixtures.timeout.TimeoutException in UTs and FTs Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681432/ Medium: - https://bugs.launchpad.net/neutron/+bug/1843418 Functional tests shouldn't fail if kill command will have "no such process" during cleanup Status: Assigned to ralonsoh. Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843425 br-int lose flows ephemerally due to unnecessary flow operation Status: In progress. Proposed fix: https://review.opendev.org/#/c/681462/ - https://bugs.launchpad.net/neutron/+bug/1843428 List port by mac address is case sensitive Status: Fix in progress. Proposed fix: https://review.opendev.org/#/c/681390 - https://bugs.launchpad.net/neutron/+bug/1843446 Implement "kill" operation using python method os.kill() Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843870 ovsdb monitor ignores modified ports Status: proposed fix: https://review.opendev.org/#/c/681984 - https://bugs.launchpad.net/neutron/+bug/1843889 Windows: IPv6 tunnel endpoints Status: proposed fix: https://review.opendev.org/#/c/682031 Incomplete: - https://bugs.launchpad.net/neutron/+bug/1843359 The iptables rules are covered when add a port from the FW group Status: requested more data from submitter - https://bugs.launchpad.net/neutron/+bug/1843801 metadata-proxy process stops listening on port 80 Status: Incomplete. Submitter was directed to use haproxy >= 1.8.15 Invalid: - https://bugs.launchpad.net/neutron/+bug/1843379 Tagging is not work for tags of QoS Policy Status: submitter was using invalid resource for the request RFE: - https://bugs.launchpad.net/neutron/+bug/1843165 RFE: Adding support for direct ports with qos in ovs Status: Under discussion with submitter - https://bugs.launchpad.net/neutron/+bug/1843924 [RFE] Create optional bulk resource_extend Status: Under discussion with submitter

1 0

RE: Rabbitmq error report
by Md. Farhad Hasan Khan 14 Sep '19

14 Sep '19

Hi, [root@controller1 ~]# rabbitmqctl list_queues |grep notification notifications.debug 0 notifications.critical 0 notifications.error 0 notifications.info 0 notifications.warn 0 notifications.audit 0 notifications.sample 0 versioned_notifications.error 6 [root@controller1 ~]# From: Md. Farhad Hasan Khan Sent: Thursday, September 12, 2019 3:29 PM To: 'OpenStack Discuss' Subject: Rabbitmq error report 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

1 0

[keystone] Keystone Team Update - Week of 9 September 2019
by Colleen Murphy 14 Sep '19

14 Sep '19

# Keystone Team Update - Week of 9 September 2019 ## News ### Feature Freeze Status We have a number of policy changes and one spec implementation still crawling through the gate[1]. Since these have all been reviewed and approved we'll continue to babysit them until they have made it. Federated user attributes[2] and expiring group membership[3] are being deferred until next cycle due to insufficient reviews/incomplete implementation. [1[ https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo [2] https://review.opendev.org/#/q/topic:bp/support-federated-attr [3] https://review.opendev.org/#/q/topic:bug/1809116 ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. The topic for next week's office hour will be: bug triage and prioritizing bugs for RC. The location for next week's office hour will be: https://meet.jit.si/keystone-office-hours Add topics you would like to see covered during office hours to the etherpad: https://etherpad.openstack.org/p/keystone-office-hours-topics ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 41 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 51 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo ## Bugs This week we opened 5 new bugs and closed 7. Bugs opened (5) Bug #1843609 (keystone:High) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1843609 Bug #1843464 (keystone:Medium) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1843464 Bug #1843925 (keystone:Undecided) opened by Ben Nemec https://bugs.launchpad.net/keystone/+bug/1843925 Bug #1843903 (python-keystoneclient:Undecided) opened by Andrew Berezovskiy https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bug #1843931 (oslo.policy:Medium) opened by Ben Nemec https://bugs.launchpad.net/oslo.policy/+bug/1843931 Bugs closed (1) Bug #1843903 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bugs fixed (6) Bug #1750669 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1750669 Bug #1805368 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805368 Bug #1805371 (keystone:Medium) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1805371 Bug #1818846 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818846 Bug #1818850 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818850 Bug #1805409 (keystone:Wishlist) fixed by Vishakha Agarwal https://bugs.launchpad.net/keystone/+bug/1805409 ## Milestone Outlook https://releases.openstack.org/train/schedule.html We're now past feature freeze and entering the RC period. Development focus should be on fixing bugs and helping to stabilize CI. RC1 will be cut in 2 weeks. We're also at requirements freeze, which means no new dependencies can be added and versions can't be changed. We're also at soft string freeze, so be mindful of checking that changes are not modifying strings. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

Execute a script on every object upload event (Swift+aodh)
by Anmar Salih 13 Sep '19

13 Sep '19

Hey all, Need help to configure swift and aodh. The idea is to trigger aodh alarm on very object upload event on swift. Once the alarm triggered, a small script should be executed. So the sequence of operations should be like this: 1- Object just uploaded to swift container 2- Alarm triggered by aodh 3- Once alarm triggered , execute python script. I am using Devstack Stein release installed on virtual box. Best regards. Anmar Salih

2 1

[all][PTL] Call for Cycle Highlights for Train
by Kendall Nelson 13 Sep '19

13 Sep '19

Hello Everyone! As you may or may not have read last week in the release update from Sean, its time to call out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from Rocky[1] or this one for Stein[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. *The deadline for cycle highlights is the end of the R-5 week [3] on Sept 13th.* How To Reminder: ------------------------- Simply add them to the deliverables/train/$PROJECT.yaml in the openstack/releases repo similar to this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/train/highlights.html file or the output of the build-openstack-sphinx-docs job under html/train/ highlights.html. Thanks :) -Kendall Nelson (diablo_rojo) [1] https://releases.openstack.org/rocky/highlights.html [2] https://releases.openstack.org/stein/highlights.html [3] https://releases.openstack.org/train/schedule.html <https://releases.openstack.org/train/schedule.html#t-cycle-highlights>

1 2

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 13 Sep '19

13 Sep '19

On Fri, Sep 13, 2019 at 04:07:54PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/c95672e425294127821c55ddf1176218 : RETRY_LIMIT in 1m 18s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures Just to make sure there is a record of it - this was a temporary infrastructure sync issue that was quickly resolved. The job was reenqueued and everything completed fine. Looks like everything is now good and no further action is needed, but of course if anything odd is seen related to this, please let us know. Sean

1 0

[release][freezer][karbor][kuryr][magnum][manila][monasca][neutron][senlin][tacker][winstackers] Missing releases for some deliverables
by Thierry Carrez 13 Sep '19

13 Sep '19

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Train cycle: - freezer and freezer-web-ui - karbor and karbor-dashboard - kuryr-kubernetes - magnum-ui - manila-ui - monasca-agent, monasca-api, monasca-ceilometer, monasca-events-api, monasca-log-api, monasca-notification, monasca-persister and monasca-transform - networking-hyperv - neutron-fwaas-dashboard and neutron-vpnaas-dashboard - senlin-dashboard - tacker-horizon Those should be released ASAP, and in all cases before September 26th, so that we have a release to include in the final Train release. Thanks in advance, -- Thierry Carrez (ttx)

3 2

[release] Release countdown for week R-4, September 16-20
by Sean McGinnis 13 Sep '19

13 Sep '19

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Train deliverables can be proposed, well ahead of the final Train release date. General Information ------------------- We are still finishing up processing a few release requests, but the Train release requirements are now frozen. If new library releases are needed to fix release-critical bugs in Train, you must request a Feature Freeze Exception (FFE) from the requirements team before we can do a new release to avoid having something released in Train that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] FFE requested for $PROJECT_LIB Include justification/reasoning for why a FFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 26 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions --------- stable/train branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Train changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Train cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00913… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 26 (R-3 week) Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

[goal][python3] Train unit tests weekly update (goal-0)
by Corey Bryant 13 Sep '19

13 Sep '19

This is the goal-0 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. Today is the final day for completion of Train community goals [2]. == How can you help? == If your project has failing tests please take a look and help fix. Python 3.7 unit tests will be self-testing in Zuul. Failing patches: https://review.openstack.org/#/q/topic:python3-train +status:open+(+label:Verified-1+OR+label:Verified-2+) If your project has patches with successful tests please help get them merged. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3 -train+is:open Patch automation scripts needing review: https://review.opendev.org/#/c/666934 == Ongoing Work == We're down to 3 projects with failing tests, and 2 projects with successful tests. Barbican and PowerVM are actively working on getting patches landed. I've not been successful in making contact with the Freezer PTL. Thank you to all who have contributed their time and fixes to enable patches to land! == Completed Work == All patches have been submitted to all applicable projects for this goal. Merged patches: https://review.openstack.org/#/q/topic:python3-train +is:merged == What's the Goal? == To ensure (in the Train cycle) that all official OpenStack repositories with Python 3 unit tests are exclusively using the 'openstack-python3-train-jobs' Zuul template or one of its variants (e.g. 'openstack-python3-train-jobs-neutron') to run unit tests, and that tests are passing. This will ensure that all official projects are running py36 and py37 unit tests in Train. For complete details please see [1]. == Reference Material == [1] Goal description: https://governance.openstack.org/tc/goals/train/ python3-updates.html [2] Train release schedule: https://releases.openstack.org/train /schedule.html (see R-5 for "Train Community Goals Completed") Storyboard: https://storyboard.openstack.org/#!/story/2005924 Porting to Python 3.7: https://docs.python.org/3/whatsnew/3.7.html#porting-to-python-3-7 Python Update Process: https://opendev.org/openstack/governance/src/branch/master/resolutions/2018… Train runtimes: https://opendev.org/openstack/governance/src/branch/master/reference/runtim… train.rst Thanks, Corey

1 0

[tc][uc][meta-sig] How to help SIGs to have a better life? (Needs feedback for SIGs guideline)
by Rico Lin 13 Sep '19

13 Sep '19

Hi all, The question I would like to ask is, what else we can do here to help SIGs to have a better life? What can we do from here? And is there any feedback regarding on experience of participate a SIG or chairing one? For some work in progress (or completed) actions: I'm working on a guideline for SIGs ( https://etherpad.openstack.org/p/SIGs-guideline ) because I believe it might provide some value for SIGs, especially new-formed SIGs. Please kindly provide your feedback on it. Will send a patch to update current document under governance-sigs once we got good enough confident on it. On the other hand, the reason I start this work is because we're thinking `How to help SIGs to have a better life?` There're some actions I can think of and the most easier answers are to get SIGs status, update guidelines and explain why we need SIG in general. So actions: I'm working on SIG guideline ( https://etherpad.openstack.org/p/SIGs-guideline ) and document `Comparison of Official Group Structures` ( https://review.opendev.org/#/c/668093/ ). Also, reach out to SIGs earlier this year to collect help most needed information for SIGs and WGs ( https://etherpad.openstack.org/p/DEN-help-most-needed-for-sigs-and-wgs ) Also, I know Belmiro Moreira (UC member) has reached out to SIGs too, so there are some up to date information. I will try to put all the above information together for share. And now, back to the question, what can we do from here? Or is there any other feedback? Before I start to disturb everyone with crazy ideas in my mind, would like to hear feedback from all of you. Finally, feedback on SIG guideline is desired. Thanks! -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

2 1