Here is the status update / focus settings mail for w39.
notification is never emitted
We still have to figure out what is the expected behavior here based on:http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html
A proposed a patch with on of the possible solution and I hope this will
help starting some discussion.
Remove dead code of
api.fault notification sending
instance.live.migration.force.complete is not a versioned notification
and not whitelisted
Solution is simple and ready for review:
testresizeservererrorandreschedulewas_failed failing due to
Test stability issue. The fix only needs a second +2
[Undecided] https://bugs.launchpad.net/nova/+bug/1718226 bdm is
wastefully loaded for versioned instance notifications
This is a bug to follow up of the closed bp
The fix removes lot of unnecessary BDM loading from the notification
code path: https://review.openstack.org/#/q/topic:bug/1718226
TestRPC.testcleanupnotifier_null fails with timeout
[High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error:
Cannot recover from stack overflow. - in py35 unit test job
The first bug is just a duplicate of the second. It seems the TetRPC
test suite has a way to end up in an infinite recusion.
I don't know about a way to reproduce it localy or to change the gate
env so that python prints out the full stack trace to see where the
problematic call is. Also adding extra log messages won't help as a
timed out test doesn't have the log messages printed to the logs. So
this bug is pretty stuck.
Versioned notification transformation
There are 3 transformation patches that only need a second +2:
* https://review.openstack.org/#/c/396211 Transform
Factor out duplicated notification sample data
This is a start of a longer patch series to deduplicate notification
sample data. The third patch already shows how much sample data can be
deleted from nova tree. We added a minimal hand rolled json ref
implementation to notification sample test as the existing python json
ref implementations are not well maintained.
Next subteam meeting will be held on 26th of September, Tuesday 17:00
UTC on openstack-meeting-4.https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170926T170000
OpenStack Development Mailing List (not for usage questions)