Saturday, 2017-11-11

dirkhwoarang: what's the question about the wheel job?06:36
*** sdague has joined #openstack-requirements12:18
*** sdague has quit IRC14:20
*** zenpwner has joined #openstack-requirements14:43
*** zenpwner has quit IRC14:44
fried_riceHey kids - what are the chances of getting a pypowervm bump backported to pike?16:53
*** fried_rice is now known as efried16:53
efrieddirk prometheanfire ^16:53
efriedsmcginnis tonyb ^16:55
dirkefried: min version bump or changing uc to a new version?18:06
efrieddirk Both18:06
dirkefried: by default dependencies don't change for projects following stable policy. What is the reason for the new version requirement?18:07
efrieddirk Found a bug that'll cause an OVS-based VM to lose network connectivity if the host reboots.18:08
efrieddirk To fix it in the driver, we effectively have to monkey-patch the lib, which is... not ideal.18:08
efriedBut doable.18:08
efrieddirk https://review.openstack.org/#/c/519030/2/nova_powervm/virt/powervm/vif.py@616 if you're interested.18:09
dirkefried: hmm... In the case of of pypowervm I personally wouldn't mind a version update as it affects only those that are affected.18:12
efrieddirk Okay, cool.  So once we cut the new version, what's the protocol?  Do we wait for generate-constraints to bump u-c in master, then propose the g-r bump in master, then... backport something?  Or propose a new something in pike?18:14
*** lxnch_ has joined #openstack-requirements18:45
*** lxnch has quit IRC18:48
*** rakhmerov has quit IRC21:53
*** rakhmerov has joined #openstack-requirements21:58
prometheanfireefried: I would say no to the min version bump22:58
prometheanfirebut uc bump makes sense22:58
prometheanfirewe can mask that bad version though22:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!