[openstack-dev] [Fuel] Testing before switching to upstream librarian
iberezovskiy at mirantis.com
Mon Oct 19 19:10:30 UTC 2015
First of all, I want to mention (I don't blame anyone), that two patchsets
in bug description
(, ) were not merged into upstream puppet-openstacklib module (and
messages don't contain links to upstream review). I see only one proposed
from Dmitry Ilyin, which was abandoned at Sep 18. Now it's restored and
those issues should be fixed using it.
Second, our patches (moving to librarian) were tested several times under
Fuel CI jobs,
on BVTs, smoke_neutron tests with Kilo and Liberty code. Unfortunately, we
problems with deployment.
Third, two weeks passed after merging of our patches for librarian, and
we are speaking about regressions.
Patch  covers missing two commits , , that's why I suggest to get
and then recheck issues, because it's very late for reverting.
 - https://review.openstack.org/#/c/219668/
 - https://review.openstack.org/#/c/223676/
 - https://review.openstack.org/#/c/220224/
2015-10-19 20:59 GMT+03:00 Sergii Golovatiuk <sgolovatiuk at mirantis.com>:
> The policy should be revert, IMHO. cherry-pick doesn't guarantee the
> consistency, so it will take more time... Also this way gives time to write
> tests to exclude the regression in future.
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
> On Mon, Oct 19, 2015 at 6:52 PM, Matthew Mosesohn <mmosesohn at mirantis.com>
>> Hi Fuelers,
>> It seems we have a regression on two critical bugs because of switching
>> Fuel to puppet-openstacklib:
>> This regressed to patches that were in Fuel Library that addressed two
>> bugs marked as Critical.
>> We should improve the acceptance criteria for moving to upstream modules
>> to ensure no bugs are regressed that relate to the particular Puppet module
>> being migrated.
>> Secondly, what should our policy be? Revert the switch to upstream
>> module? Or just work on cherry-picking the appropriate fixes?
>> Best Regards,
>> Matthew Mosesohn
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Thanks, Ivan Berezovskiy
MOS Puppet Team Lead
at Mirantis <https://www.mirantis.com/>
phone: + 7-960-343-42-46
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev