Anyone run latest master today with full dev? I'm seeing
NoClassDefFoundError exceptions on starting enrichments. I upgraded to
latest Ansible and the provisioning part seemed to work just fine.
https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3


On Mon, Oct 1, 2018 at 6:46 AM zeo...@gmail.com <zeo...@gmail.com> wrote:

> Hi All,
>
> This has been pushed to master.  Please updated your Ansible
> appropriately.  Thanks!
>
> Jon
>
> On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler <ottobackwa...@gmail.com>
> wrote:
>
>> Yeah,  I thought we had more but maybe they where removed.
>> Many places in *.md files referencing Ansible and versions too
>>
>>
>> On September 28, 2018 at 11:45:14, zeo...@gmail.com (zeo...@gmail.com)
>> wrote:
>>
>> Do you mean this
>> <https://cwiki.apache.org/confluence/display/METRON/Downgrade+Ansible>?
>> It was the only reference I could find on the wiki.  All of the READMEs
>> should be updated as a part of the PR, but feel free to provide your input
>> if I missed anything.
>>
>> Jon
>>
>> On Fri, Sep 28, 2018 at 10:15 AM Otto Fowler <ottobackwa...@gmail.com>
>> wrote:
>>
>>> We should make sure the non-source documentation is updated
>>>
>>>
>>> On September 28, 2018 at 09:32:52, zeo...@gmail.com (zeo...@gmail.com)
>>> wrote:
>>>
>>> Hi All,
>>>
>>> As it currently sits, once METRON-1758
>>> <https://github.com/apache/metron/pull/1179> is merged into the code
>>> base, Ansible 2.4 or later will be required to use any of the Metron
>>> ansible playbooks.  This is in contrast to the prior version requirements
>>> outlined in Metron documentation which specifically point to 2.0.0.2 and
>>> 2.2.0.0 as supported/recommended Ansible versions.  If you install Ansible
>>> 2.5.0 exactly you should not experience any issues spinning up pre- and 
>>> post-
>>> merge versions of Metron.
>>>
>>> I am broadcasting this to both the user and dev communities in advance
>>> of any changes to provide an opportunity to voice any concerns.  Thanks,
>>>
>>> Jon
>>> --
>>>
>>> Jon
>>>
>>> --
>>
>> Jon
>>
>> --
>
> Jon
>

Reply via email to