You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by "Zeolla@GMail.com" <ze...@gmail.com> on 2017/02/09 18:05:06 UTC
Unable to build Ansible 2.0.0.2 on macOS using our instructions
Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac
using brew and the steps we outline here
<https://github.com/apache/incubator-metron/tree/master/metron-deployment/vagrant/full-dev-platform#os-x>?
I received a new laptop this week, so I ran through some of our setup
documentation to test any assumptions that may exist in our READMEs (see
METRON-708 <https://github.com/apache/incubator-metron/pull/447> for some
of my updates) before restoring my TM backup.
It looks like the installation process broke because of some function
renaming <https://github.com/openssl/openssl/issues/1190> within openssl. I'd
like to get some secondary validation of this issue if anybody else has an
environment where they can give it a shot. I think I was able to resolve
the issue by back-porting this commit
<https://github.com/Homebrew/homebrew-core/commit/e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
I just haven't had time to complete more comprehensive testing (i.e.
spinning up quick-dev or full-dev). Once we agree on the resolution to
this I can update METRON-708 appropriately.
Here are some relevant logs taken from
~/Library/Logs/Homebrew/ansible/09.python:
building '_openssl' extension
creating build/temp.macosx-10.12-intel-2.7/build
creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-intel-2.7
clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g
-Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE -DMACOSX
-DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv
-Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
-c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-intel-2.7/_openssl.o
build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error: conflicting
types for 'BIO_new_mem_buf'
BIO *BIO_new_mem_buf(void *, int);
^
/usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
declaration is here
BIO *BIO_new_mem_buf(const void *buf, int len);
^
build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error: redefinition
of 'SSLv2_method' as different kind of symbol
SSL_METHOD* (*SSLv2_method)(void) = NULL;
^
/usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
definition is here
const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
^
build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error: redefinition
of 'SSLv2_client_method' as different kind of symbol
SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
^
/usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
definition is here
const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
^
build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error: redefinition
of 'SSLv2_server_method' as different kind of symbol
SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
^
/usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
definition is here
const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
^
4 errors generated.
error: command 'clang' failed with exit status 1
Jon
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Hey Dave,
Can you point me to which branch you were referring to? I'd be happy to
take a stab at this - I really don't like having broken instructions
sitting out there. Thanks,
Jon
On Wed, Mar 1, 2017 at 4:22 PM Zeolla@GMail.com <ze...@gmail.com> wrote:
> Sounds good to me, I'll keep an eye out. Thanks,
>
> Jon
>
>
> On Wed, Mar 1, 2017 at 1:47 PM David Lyle <dl...@gmail.com> wrote:
>
> Hi Jon,
>
> Unfortunately the branch I have working touches much of the same code that
> is getting refactored as part of METRON-671. I'm wrapping that up now, so
> how about if I get that done and then publish a reconciled branch with the
> changes I had to make to get 671 working?
>
> -D...
>
>
> On Wed, Mar 1, 2017 at 1:32 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
>
> > Hey Dave,
> >
> > Any luck with METRON-196 <
> https://issues.apache.org/jira/browse/METRON-196
> > >?
> > Happy to help now that I'm back in the swing of things. Thanks,
> >
> > Jon
> >
> > On Mon, Feb 13, 2017 at 9:38 AM David Lyle <dl...@gmail.com> wrote:
> >
> > > That'll be great, thanks. It'd be great to run it up on your rig.
> > >
> > > On Mon, Feb 13, 2017 at 09:34 Zeolla@GMail.com <ze...@gmail.com>
> wrote:
> > >
> > > > Ok sounds good. I'm traveling next week, but if the stars align I'll
> > > > review when I get back.
> > > >
> > > > Jon
> > > >
> > > > On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com>
> > wrote:
> > > >
> > > > > I've got a working branch that needs a bit of testing. I'm
> traveling
> > > this
> > > > > week, so I won't get it in a submittable state prior to next week.
> > > > >
> > > > > I didn't find anything but the issues I've already mentioned.
> > > > >
> > > > > -D...
> > > > >
> > > > > On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Are you handling this one under METRON-196? I'd be happy to
> lend a
> > > > hand
> > > > > if
> > > > > > it's easy to split up. I'd like to get this one resolved
> (before I
> > > > > forget
> > > > > > that it exists) either by upgrading or by fixing the
> documentation.
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dlyle65535@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Hi Jon,
> > > > > > >
> > > > > > > There are a few issues.
> > > > > > >
> > > > > > > So far:
> > > > > > >
> > > > > > > Ansible modules has deprecated choices=BOOLEANS in favor of
> > > > type='bool'
> > > > > > > (ambari_cluster_state.py)
> > > > > > > The Ansible URI module JSON handling is broken again, I've
> > replaced
> > > > it
> > > > > > with
> > > > > > > curl in load_templates.yml
> > > > > > > Ansible's 'register' seems to have a length limitation now-
> > that's
> > > > > > causing
> > > > > > > a problem in ansible_gather_facts ln 133. I'm fixing that with
> a
> > > > > > > combination of curl and grep.
> > > > > > >
> > > > > > > I'll give it a bit more and see if I can roll through it.
> > > > > > >
> > > > > > > -D...
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <
> > > zeolla@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Yes I would definitely love to use this as a reason to update
> > > > > Ansible.
> > > > > > > > I'll run it up with 2.2.1.0 as well right now.
> > > > > > > >
> > > > > > > > Jon
> > > > > > > >
> > > > > > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <
> > dlyle65535@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC
> > there
> > > > > were
> > > > > > a
> > > > > > > > few
> > > > > > > > > issues with other versions as well. I'm spinning up
> quick-dev
> > > in
> > > > a
> > > > > > venv
> > > > > > > > > now, I'll let you know.
> > > > > > > > >
> > > > > > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <
> > > > cestella@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Sure, of course. I thought we had some known issues with
> > > > > 2.2.1.0,
> > > > > > > but
> > > > > > > > I
> > > > > > > > > am
> > > > > > > > > > probably misremembering.
> > > > > > > > > >
> > > > > > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> > > > > dlyle65535@gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Would it make sense to give Ansible 2.2.1.0 a try
> first?
> > > I'd
> > > > > like
> > > > > > > to
> > > > > > > > > > avoid
> > > > > > > > > > > backporting to Ansible if we can avoid it.
> > > > > > > > > > >
> > > > > > > > > > > -D...
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > > > > > cestella@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> > > > > documenting
> > > > > > > the
> > > > > > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > > > > > zeolla@gmail.com
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2
> > > recently
> > > > > on a
> > > > > > > > fresh
> > > > > > > > > > mac
> > > > > > > > > > > > > using brew and the steps we outline here
> > > > > > > > > > > > > <
> > > https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > > > > > I received a new laptop this week, so I ran through
> > > some
> > > > of
> > > > > > our
> > > > > > > > > setup
> > > > > > > > > > > > > documentation to test any assumptions that may
> exist
> > in
> > > > our
> > > > > > > > READMEs
> > > > > > > > > > > (see
> > > > > > > > > > > > > METRON-708 <
> > > > > > > https://github.com/apache/incubator-metron/pull/447>
> > > > > > > > > for
> > > > > > > > > > > > some
> > > > > > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > > > > > >
> > > > > > > > > > > > > It looks like the installation process broke
> because
> > of
> > > > > some
> > > > > > > > > function
> > > > > > > > > > > > > renaming <
> > > https://github.com/openssl/openssl/issues/1190
> > > > >
> > > > > > > within
> > > > > > > > > > > > > openssl. I'd
> > > > > > > > > > > > > like to get some secondary validation of this issue
> > if
> > > > > > anybody
> > > > > > > > else
> > > > > > > > > > has
> > > > > > > > > > > > an
> > > > > > > > > > > > > environment where they can give it a shot. I
> think I
> > > was
> > > > > > able
> > > > > > > to
> > > > > > > > > > > resolve
> > > > > > > > > > > > > the issue by back-porting this commit
> > > > > > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > > > > > I just haven't had time to complete more
> > comprehensive
> > > > > > testing
> > > > > > > > > (i.e.
> > > > > > > > > > > > > spinning up quick-dev or full-dev). Once we agree
> on
> > > the
> > > > > > > > > resolution
> > > > > > > > > > to
> > > > > > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > > > > > >
> > > > > > > > > > > > > building '_openssl' extension
> > > > > > > > > > > > >
> > > > > > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > > > > > >
> > > > > > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > > > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > > intel-2.7
> > > > > > > > > > > > >
> > > > > > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic
> -arch
> > > > > x86_64
> > > > > > > > -arch
> > > > > > > > > > i386
> > > > > > > > > > > > -g
> > > > > > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > > > > > -DENABLE_DTRACE
> > > > > > > > > > > > -DMACOSX
> > > > > > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes
> -Wshorten-64-to-32
> > > > > > -DNDEBUG
> > > > > > > -g
> > > > > > > > > > > -fwrapv
> > > > > > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch
> > > > x86_64
> > > > > > > -arch
> > > > > > > > > i386
> > > > > > > > > > > > -pipe
> > > > > > > > > > > > >
> > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > > > > > include/python2.7
> > > > > > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > > > > >
> > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > > > > > >
> > > > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6:
> > > > error:
> > > > > > > > > > conflicting
> > > > > > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > > > > > >
> > > > > > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > > declaration is here
> > > > > > > > > > > > >
> > > > > > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > build/temp.macosx-10.12-intel-
> > 2.7/_openssl.c:2089:15:
> > > > > error:
> > > > > > > > > > > > redefinition
> > > > > > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > > > > > >
> > > > > > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > /usr/local/opt/openssl/
> > include/openssl/ssl.h:2349:19:
> > > > note:
> > > > > > > > > previous
> > > > > > > > > > > > > definition is here
> > > > > > > > > > > > >
> > > > > > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > build/temp.macosx-10.12-intel-
> > 2.7/_openssl.c:2090:15:
> > > > > error:
> > > > > > > > > > > > redefinition
> > > > > > > > > > > > > of 'SSLv2_client_method' as different kind of
> symbol
> > > > > > > > > > > > >
> > > > > > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > /usr/local/opt/openssl/
> > include/openssl/ssl.h:2351:19:
> > > > note:
> > > > > > > > > previous
> > > > > > > > > > > > > definition is here
> > > > > > > > > > > > >
> > > > > > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /*
> SSLv2
> > > */
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > build/temp.macosx-10.12-intel-
> > 2.7/_openssl.c:2091:15:
> > > > > error:
> > > > > > > > > > > > redefinition
> > > > > > > > > > > > > of 'SSLv2_server_method' as different kind of
> symbol
> > > > > > > > > > > > >
> > > > > > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > /usr/local/opt/openssl/
> > include/openssl/ssl.h:2350:19:
> > > > note:
> > > > > > > > > previous
> > > > > > > > > > > > > definition is here
> > > > > > > > > > > > >
> > > > > > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /*
> SSLv2
> > > */
> > > > > > > > > > > > >
> > > > > > > > > > > > > ^
> > > > > > > > > > > > >
> > > > > > > > > > > > > 4 errors generated.
> > > > > > > > > > > > >
> > > > > > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Jon
> > > > > > > > > > > > > --
> > > > > > > > > > > > >
> > > > > > > > > > > > > Jon
> > > > > > > > > > > > >
> > > > > > > > > > > > > Sent from my mobile device
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Jon
> > > > > > > >
> > > > > > > > Sent from my mobile device
> > > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > > Sent from my mobile device
> > > > > >
> > > > >
> > > > --
> > > >
> > > > Jon
> > > >
> > > > Sent from my mobile device
> > > >
> > >
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>
> --
>
> Jon
>
> Sent from my mobile device
>
--
Jon
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Sounds good to me, I'll keep an eye out. Thanks,
Jon
On Wed, Mar 1, 2017 at 1:47 PM David Lyle <dl...@gmail.com> wrote:
Hi Jon,
Unfortunately the branch I have working touches much of the same code that
is getting refactored as part of METRON-671. I'm wrapping that up now, so
how about if I get that done and then publish a reconciled branch with the
changes I had to make to get 671 working?
-D...
On Wed, Mar 1, 2017 at 1:32 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
> Hey Dave,
>
> Any luck with METRON-196 <https://issues.apache.org/jira/browse/METRON-196
> >?
> Happy to help now that I'm back in the swing of things. Thanks,
>
> Jon
>
> On Mon, Feb 13, 2017 at 9:38 AM David Lyle <dl...@gmail.com> wrote:
>
> > That'll be great, thanks. It'd be great to run it up on your rig.
> >
> > On Mon, Feb 13, 2017 at 09:34 Zeolla@GMail.com <ze...@gmail.com> wrote:
> >
> > > Ok sounds good. I'm traveling next week, but if the stars align I'll
> > > review when I get back.
> > >
> > > Jon
> > >
> > > On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com>
> wrote:
> > >
> > > > I've got a working branch that needs a bit of testing. I'm traveling
> > this
> > > > week, so I won't get it in a submittable state prior to next week.
> > > >
> > > > I didn't find anything but the issues I've already mentioned.
> > > >
> > > > -D...
> > > >
> > > > On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com>
> > wrote:
> > > >
> > > > > Are you handling this one under METRON-196? I'd be happy to lend
a
> > > hand
> > > > if
> > > > > it's easy to split up. I'd like to get this one resolved (before
I
> > > > forget
> > > > > that it exists) either by upgrading or by fixing the
documentation.
> > > > >
> > > > > Jon
> > > > >
> > > > > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hi Jon,
> > > > > >
> > > > > > There are a few issues.
> > > > > >
> > > > > > So far:
> > > > > >
> > > > > > Ansible modules has deprecated choices=BOOLEANS in favor of
> > > type='bool'
> > > > > > (ambari_cluster_state.py)
> > > > > > The Ansible URI module JSON handling is broken again, I've
> replaced
> > > it
> > > > > with
> > > > > > curl in load_templates.yml
> > > > > > Ansible's 'register' seems to have a length limitation now-
> that's
> > > > > causing
> > > > > > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > > > > > combination of curl and grep.
> > > > > >
> > > > > > I'll give it a bit more and see if I can roll through it.
> > > > > >
> > > > > > -D...
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <
> > zeolla@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Yes I would definitely love to use this as a reason to update
> > > > Ansible.
> > > > > > > I'll run it up with 2.2.1.0 as well right now.
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <
> dlyle65535@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC
> there
> > > > were
> > > > > a
> > > > > > > few
> > > > > > > > issues with other versions as well. I'm spinning up
quick-dev
> > in
> > > a
> > > > > venv
> > > > > > > > now, I'll let you know.
> > > > > > > >
> > > > > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <
> > > cestella@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Sure, of course. I thought we had some known issues with
> > > > 2.2.1.0,
> > > > > > but
> > > > > > > I
> > > > > > > > am
> > > > > > > > > probably misremembering.
> > > > > > > > >
> > > > > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> > > > dlyle65535@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Would it make sense to give Ansible 2.2.1.0 a try first?
> > I'd
> > > > like
> > > > > > to
> > > > > > > > > avoid
> > > > > > > > > > backporting to Ansible if we can avoid it.
> > > > > > > > > >
> > > > > > > > > > -D...
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > > > > cestella@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> > > > documenting
> > > > > > the
> > > > > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > > > > zeolla@gmail.com
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2
> > recently
> > > > on a
> > > > > > > fresh
> > > > > > > > > mac
> > > > > > > > > > > > using brew and the steps we outline here
> > > > > > > > > > > > <
> > https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > > > > I received a new laptop this week, so I ran through
> > some
> > > of
> > > > > our
> > > > > > > > setup
> > > > > > > > > > > > documentation to test any assumptions that may exist
> in
> > > our
> > > > > > > READMEs
> > > > > > > > > > (see
> > > > > > > > > > > > METRON-708 <
> > > > > > https://github.com/apache/incubator-metron/pull/447>
> > > > > > > > for
> > > > > > > > > > > some
> > > > > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > > > > >
> > > > > > > > > > > > It looks like the installation process broke because
> of
> > > > some
> > > > > > > > function
> > > > > > > > > > > > renaming <
> > https://github.com/openssl/openssl/issues/1190
> > > >
> > > > > > within
> > > > > > > > > > > > openssl. I'd
> > > > > > > > > > > > like to get some secondary validation of this issue
> if
> > > > > anybody
> > > > > > > else
> > > > > > > > > has
> > > > > > > > > > > an
> > > > > > > > > > > > environment where they can give it a shot. I think
I
> > was
> > > > > able
> > > > > > to
> > > > > > > > > > resolve
> > > > > > > > > > > > the issue by back-porting this commit
> > > > > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > > > > I just haven't had time to complete more
> comprehensive
> > > > > testing
> > > > > > > > (i.e.
> > > > > > > > > > > > spinning up quick-dev or full-dev). Once we agree
on
> > the
> > > > > > > > resolution
> > > > > > > > > to
> > > > > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > > > > >
> > > > > > > > > > > > building '_openssl' extension
> > > > > > > > > > > >
> > > > > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > > > > >
> > > > > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > intel-2.7
> > > > > > > > > > > >
> > > > > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic
-arch
> > > > x86_64
> > > > > > > -arch
> > > > > > > > > i386
> > > > > > > > > > > -g
> > > > > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > > > > -DENABLE_DTRACE
> > > > > > > > > > > -DMACOSX
> > > > > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes
-Wshorten-64-to-32
> > > > > -DNDEBUG
> > > > > > -g
> > > > > > > > > > -fwrapv
> > > > > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch
> > > x86_64
> > > > > > -arch
> > > > > > > > i386
> > > > > > > > > > > -pipe
> > > > > > > > > > > >
> > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > > > > include/python2.7
> > > > > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > > > >
> > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6:
> > > error:
> > > > > > > > > conflicting
> > > > > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > > > > >
> > > > > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6:
> > note:
> > > > > > > previous
> > > > > > > > > > > > declaration is here
> > > > > > > > > > > >
> > > > > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2089:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2349:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2090:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2351:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /*
SSLv2
> > */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2091:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2350:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /*
SSLv2
> > */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > 4 errors generated.
> > > > > > > > > > > >
> > > > > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Jon
> > > > > > > > > > > > --
> > > > > > > > > > > >
> > > > > > > > > > > > Jon
> > > > > > > > > > > >
> > > > > > > > > > > > Sent from my mobile device
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > Sent from my mobile device
> > > > > > >
> > > > > >
> > > > > --
> > > > >
> > > > > Jon
> > > > >
> > > > > Sent from my mobile device
> > > > >
> > > >
> > > --
> > >
> > > Jon
> > >
> > > Sent from my mobile device
> > >
> >
> --
>
> Jon
>
> Sent from my mobile device
>
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
Hi Jon,
Unfortunately the branch I have working touches much of the same code that
is getting refactored as part of METRON-671. I'm wrapping that up now, so
how about if I get that done and then publish a reconciled branch with the
changes I had to make to get 671 working?
-D...
On Wed, Mar 1, 2017 at 1:32 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
> Hey Dave,
>
> Any luck with METRON-196 <https://issues.apache.org/jira/browse/METRON-196
> >?
> Happy to help now that I'm back in the swing of things. Thanks,
>
> Jon
>
> On Mon, Feb 13, 2017 at 9:38 AM David Lyle <dl...@gmail.com> wrote:
>
> > That'll be great, thanks. It'd be great to run it up on your rig.
> >
> > On Mon, Feb 13, 2017 at 09:34 Zeolla@GMail.com <ze...@gmail.com> wrote:
> >
> > > Ok sounds good. I'm traveling next week, but if the stars align I'll
> > > review when I get back.
> > >
> > > Jon
> > >
> > > On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com>
> wrote:
> > >
> > > > I've got a working branch that needs a bit of testing. I'm traveling
> > this
> > > > week, so I won't get it in a submittable state prior to next week.
> > > >
> > > > I didn't find anything but the issues I've already mentioned.
> > > >
> > > > -D...
> > > >
> > > > On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com>
> > wrote:
> > > >
> > > > > Are you handling this one under METRON-196? I'd be happy to lend a
> > > hand
> > > > if
> > > > > it's easy to split up. I'd like to get this one resolved (before I
> > > > forget
> > > > > that it exists) either by upgrading or by fixing the documentation.
> > > > >
> > > > > Jon
> > > > >
> > > > > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hi Jon,
> > > > > >
> > > > > > There are a few issues.
> > > > > >
> > > > > > So far:
> > > > > >
> > > > > > Ansible modules has deprecated choices=BOOLEANS in favor of
> > > type='bool'
> > > > > > (ambari_cluster_state.py)
> > > > > > The Ansible URI module JSON handling is broken again, I've
> replaced
> > > it
> > > > > with
> > > > > > curl in load_templates.yml
> > > > > > Ansible's 'register' seems to have a length limitation now-
> that's
> > > > > causing
> > > > > > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > > > > > combination of curl and grep.
> > > > > >
> > > > > > I'll give it a bit more and see if I can roll through it.
> > > > > >
> > > > > > -D...
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <
> > zeolla@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Yes I would definitely love to use this as a reason to update
> > > > Ansible.
> > > > > > > I'll run it up with 2.2.1.0 as well right now.
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <
> dlyle65535@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC
> there
> > > > were
> > > > > a
> > > > > > > few
> > > > > > > > issues with other versions as well. I'm spinning up quick-dev
> > in
> > > a
> > > > > venv
> > > > > > > > now, I'll let you know.
> > > > > > > >
> > > > > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <
> > > cestella@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Sure, of course. I thought we had some known issues with
> > > > 2.2.1.0,
> > > > > > but
> > > > > > > I
> > > > > > > > am
> > > > > > > > > probably misremembering.
> > > > > > > > >
> > > > > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> > > > dlyle65535@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Would it make sense to give Ansible 2.2.1.0 a try first?
> > I'd
> > > > like
> > > > > > to
> > > > > > > > > avoid
> > > > > > > > > > backporting to Ansible if we can avoid it.
> > > > > > > > > >
> > > > > > > > > > -D...
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > > > > cestella@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> > > > documenting
> > > > > > the
> > > > > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > > > > zeolla@gmail.com
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2
> > recently
> > > > on a
> > > > > > > fresh
> > > > > > > > > mac
> > > > > > > > > > > > using brew and the steps we outline here
> > > > > > > > > > > > <
> > https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > > > > I received a new laptop this week, so I ran through
> > some
> > > of
> > > > > our
> > > > > > > > setup
> > > > > > > > > > > > documentation to test any assumptions that may exist
> in
> > > our
> > > > > > > READMEs
> > > > > > > > > > (see
> > > > > > > > > > > > METRON-708 <
> > > > > > https://github.com/apache/incubator-metron/pull/447>
> > > > > > > > for
> > > > > > > > > > > some
> > > > > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > > > > >
> > > > > > > > > > > > It looks like the installation process broke because
> of
> > > > some
> > > > > > > > function
> > > > > > > > > > > > renaming <
> > https://github.com/openssl/openssl/issues/1190
> > > >
> > > > > > within
> > > > > > > > > > > > openssl. I'd
> > > > > > > > > > > > like to get some secondary validation of this issue
> if
> > > > > anybody
> > > > > > > else
> > > > > > > > > has
> > > > > > > > > > > an
> > > > > > > > > > > > environment where they can give it a shot. I think I
> > was
> > > > > able
> > > > > > to
> > > > > > > > > > resolve
> > > > > > > > > > > > the issue by back-porting this commit
> > > > > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > > > > I just haven't had time to complete more
> comprehensive
> > > > > testing
> > > > > > > > (i.e.
> > > > > > > > > > > > spinning up quick-dev or full-dev). Once we agree on
> > the
> > > > > > > > resolution
> > > > > > > > > to
> > > > > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > > > > >
> > > > > > > > > > > > building '_openssl' extension
> > > > > > > > > > > >
> > > > > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > > > > >
> > > > > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > intel-2.7
> > > > > > > > > > > >
> > > > > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch
> > > > x86_64
> > > > > > > -arch
> > > > > > > > > i386
> > > > > > > > > > > -g
> > > > > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > > > > -DENABLE_DTRACE
> > > > > > > > > > > -DMACOSX
> > > > > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32
> > > > > -DNDEBUG
> > > > > > -g
> > > > > > > > > > -fwrapv
> > > > > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch
> > > x86_64
> > > > > > -arch
> > > > > > > > i386
> > > > > > > > > > > -pipe
> > > > > > > > > > > >
> > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > > > > include/python2.7
> > > > > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > > > >
> > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6:
> > > error:
> > > > > > > > > conflicting
> > > > > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > > > > >
> > > > > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6:
> > note:
> > > > > > > previous
> > > > > > > > > > > > declaration is here
> > > > > > > > > > > >
> > > > > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2089:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2349:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2090:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2351:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2
> > */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > build/temp.macosx-10.12-intel-
> 2.7/_openssl.c:2091:15:
> > > > error:
> > > > > > > > > > > redefinition
> > > > > > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > > > > > >
> > > > > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > /usr/local/opt/openssl/
> include/openssl/ssl.h:2350:19:
> > > note:
> > > > > > > > previous
> > > > > > > > > > > > definition is here
> > > > > > > > > > > >
> > > > > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2
> > */
> > > > > > > > > > > >
> > > > > > > > > > > > ^
> > > > > > > > > > > >
> > > > > > > > > > > > 4 errors generated.
> > > > > > > > > > > >
> > > > > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Jon
> > > > > > > > > > > > --
> > > > > > > > > > > >
> > > > > > > > > > > > Jon
> > > > > > > > > > > >
> > > > > > > > > > > > Sent from my mobile device
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > Sent from my mobile device
> > > > > > >
> > > > > >
> > > > > --
> > > > >
> > > > > Jon
> > > > >
> > > > > Sent from my mobile device
> > > > >
> > > >
> > > --
> > >
> > > Jon
> > >
> > > Sent from my mobile device
> > >
> >
> --
>
> Jon
>
> Sent from my mobile device
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Hey Dave,
Any luck with METRON-196 <https://issues.apache.org/jira/browse/METRON-196>?
Happy to help now that I'm back in the swing of things. Thanks,
Jon
On Mon, Feb 13, 2017 at 9:38 AM David Lyle <dl...@gmail.com> wrote:
> That'll be great, thanks. It'd be great to run it up on your rig.
>
> On Mon, Feb 13, 2017 at 09:34 Zeolla@GMail.com <ze...@gmail.com> wrote:
>
> > Ok sounds good. I'm traveling next week, but if the stars align I'll
> > review when I get back.
> >
> > Jon
> >
> > On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com> wrote:
> >
> > > I've got a working branch that needs a bit of testing. I'm traveling
> this
> > > week, so I won't get it in a submittable state prior to next week.
> > >
> > > I didn't find anything but the issues I've already mentioned.
> > >
> > > -D...
> > >
> > > On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com>
> wrote:
> > >
> > > > Are you handling this one under METRON-196? I'd be happy to lend a
> > hand
> > > if
> > > > it's easy to split up. I'd like to get this one resolved (before I
> > > forget
> > > > that it exists) either by upgrading or by fixing the documentation.
> > > >
> > > > Jon
> > > >
> > > > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com>
> > wrote:
> > > >
> > > > > Hi Jon,
> > > > >
> > > > > There are a few issues.
> > > > >
> > > > > So far:
> > > > >
> > > > > Ansible modules has deprecated choices=BOOLEANS in favor of
> > type='bool'
> > > > > (ambari_cluster_state.py)
> > > > > The Ansible URI module JSON handling is broken again, I've replaced
> > it
> > > > with
> > > > > curl in load_templates.yml
> > > > > Ansible's 'register' seems to have a length limitation now- that's
> > > > causing
> > > > > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > > > > combination of curl and grep.
> > > > >
> > > > > I'll give it a bit more and see if I can roll through it.
> > > > >
> > > > > -D...
> > > > >
> > > > >
> > > > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <
> zeolla@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Yes I would definitely love to use this as a reason to update
> > > Ansible.
> > > > > > I'll run it up with 2.2.1.0 as well right now.
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC there
> > > were
> > > > a
> > > > > > few
> > > > > > > issues with other versions as well. I'm spinning up quick-dev
> in
> > a
> > > > venv
> > > > > > > now, I'll let you know.
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <
> > cestella@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Sure, of course. I thought we had some known issues with
> > > 2.2.1.0,
> > > > > but
> > > > > > I
> > > > > > > am
> > > > > > > > probably misremembering.
> > > > > > > >
> > > > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> > > dlyle65535@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Would it make sense to give Ansible 2.2.1.0 a try first?
> I'd
> > > like
> > > > > to
> > > > > > > > avoid
> > > > > > > > > backporting to Ansible if we can avoid it.
> > > > > > > > >
> > > > > > > > > -D...
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > > > cestella@gmail.com>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> > > documenting
> > > > > the
> > > > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > > > >
> > > > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > > > zeolla@gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2
> recently
> > > on a
> > > > > > fresh
> > > > > > > > mac
> > > > > > > > > > > using brew and the steps we outline here
> > > > > > > > > > > <
> https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > > > I received a new laptop this week, so I ran through
> some
> > of
> > > > our
> > > > > > > setup
> > > > > > > > > > > documentation to test any assumptions that may exist in
> > our
> > > > > > READMEs
> > > > > > > > > (see
> > > > > > > > > > > METRON-708 <
> > > > > https://github.com/apache/incubator-metron/pull/447>
> > > > > > > for
> > > > > > > > > > some
> > > > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > > > >
> > > > > > > > > > > It looks like the installation process broke because of
> > > some
> > > > > > > function
> > > > > > > > > > > renaming <
> https://github.com/openssl/openssl/issues/1190
> > >
> > > > > within
> > > > > > > > > > > openssl. I'd
> > > > > > > > > > > like to get some secondary validation of this issue if
> > > > anybody
> > > > > > else
> > > > > > > > has
> > > > > > > > > > an
> > > > > > > > > > > environment where they can give it a shot. I think I
> was
> > > > able
> > > > > to
> > > > > > > > > resolve
> > > > > > > > > > > the issue by back-porting this commit
> > > > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > > > I just haven't had time to complete more comprehensive
> > > > testing
> > > > > > > (i.e.
> > > > > > > > > > > spinning up quick-dev or full-dev). Once we agree on
> the
> > > > > > > resolution
> > > > > > > > to
> > > > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > > > >
> > > > > > > > > > > building '_openssl' extension
> > > > > > > > > > >
> > > > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > > > >
> > > > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > > > intel-2.7
> > > > > > > > > > >
> > > > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch
> > > x86_64
> > > > > > -arch
> > > > > > > > i386
> > > > > > > > > > -g
> > > > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > > > -DENABLE_DTRACE
> > > > > > > > > > -DMACOSX
> > > > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32
> > > > -DNDEBUG
> > > > > -g
> > > > > > > > > -fwrapv
> > > > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch
> > x86_64
> > > > > -arch
> > > > > > > i386
> > > > > > > > > > -pipe
> > > > > > > > > > >
> > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > > > include/python2.7
> > > > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > > >
> > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > > > >
> > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6:
> > error:
> > > > > > > > conflicting
> > > > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > > > >
> > > > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6:
> note:
> > > > > > previous
> > > > > > > > > > > declaration is here
> > > > > > > > > > >
> > > > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15:
> > > error:
> > > > > > > > > > redefinition
> > > > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > > > >
> > > > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19:
> > note:
> > > > > > > previous
> > > > > > > > > > > definition is here
> > > > > > > > > > >
> > > > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15:
> > > error:
> > > > > > > > > > redefinition
> > > > > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > > > > >
> > > > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19:
> > note:
> > > > > > > previous
> > > > > > > > > > > definition is here
> > > > > > > > > > >
> > > > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2
> */
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15:
> > > error:
> > > > > > > > > > redefinition
> > > > > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > > > > >
> > > > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19:
> > note:
> > > > > > > previous
> > > > > > > > > > > definition is here
> > > > > > > > > > >
> > > > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2
> */
> > > > > > > > > > >
> > > > > > > > > > > ^
> > > > > > > > > > >
> > > > > > > > > > > 4 errors generated.
> > > > > > > > > > >
> > > > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Jon
> > > > > > > > > > > --
> > > > > > > > > > >
> > > > > > > > > > > Jon
> > > > > > > > > > >
> > > > > > > > > > > Sent from my mobile device
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > > Sent from my mobile device
> > > > > >
> > > > >
> > > > --
> > > >
> > > > Jon
> > > >
> > > > Sent from my mobile device
> > > >
> > >
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
That'll be great, thanks. It'd be great to run it up on your rig.
On Mon, Feb 13, 2017 at 09:34 Zeolla@GMail.com <ze...@gmail.com> wrote:
> Ok sounds good. I'm traveling next week, but if the stars align I'll
> review when I get back.
>
> Jon
>
> On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com> wrote:
>
> > I've got a working branch that needs a bit of testing. I'm traveling this
> > week, so I won't get it in a submittable state prior to next week.
> >
> > I didn't find anything but the issues I've already mentioned.
> >
> > -D...
> >
> > On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com> wrote:
> >
> > > Are you handling this one under METRON-196? I'd be happy to lend a
> hand
> > if
> > > it's easy to split up. I'd like to get this one resolved (before I
> > forget
> > > that it exists) either by upgrading or by fixing the documentation.
> > >
> > > Jon
> > >
> > > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com>
> wrote:
> > >
> > > > Hi Jon,
> > > >
> > > > There are a few issues.
> > > >
> > > > So far:
> > > >
> > > > Ansible modules has deprecated choices=BOOLEANS in favor of
> type='bool'
> > > > (ambari_cluster_state.py)
> > > > The Ansible URI module JSON handling is broken again, I've replaced
> it
> > > with
> > > > curl in load_templates.yml
> > > > Ansible's 'register' seems to have a length limitation now- that's
> > > causing
> > > > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > > > combination of curl and grep.
> > > >
> > > > I'll give it a bit more and see if I can roll through it.
> > > >
> > > > -D...
> > > >
> > > >
> > > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <ze...@gmail.com>
> > > > wrote:
> > > >
> > > > > Yes I would definitely love to use this as a reason to update
> > Ansible.
> > > > > I'll run it up with 2.2.1.0 as well right now.
> > > > >
> > > > > Jon
> > > > >
> > > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com>
> > > wrote:
> > > > >
> > > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC there
> > were
> > > a
> > > > > few
> > > > > > issues with other versions as well. I'm spinning up quick-dev in
> a
> > > venv
> > > > > > now, I'll let you know.
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <
> cestella@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Sure, of course. I thought we had some known issues with
> > 2.2.1.0,
> > > > but
> > > > > I
> > > > > > am
> > > > > > > probably misremembering.
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> > dlyle65535@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd
> > like
> > > > to
> > > > > > > avoid
> > > > > > > > backporting to Ansible if we can avoid it.
> > > > > > > >
> > > > > > > > -D...
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > > cestella@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> > documenting
> > > > the
> > > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > > >
> > > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > > zeolla@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2 recently
> > on a
> > > > > fresh
> > > > > > > mac
> > > > > > > > > > using brew and the steps we outline here
> > > > > > > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > > I received a new laptop this week, so I ran through some
> of
> > > our
> > > > > > setup
> > > > > > > > > > documentation to test any assumptions that may exist in
> our
> > > > > READMEs
> > > > > > > > (see
> > > > > > > > > > METRON-708 <
> > > > https://github.com/apache/incubator-metron/pull/447>
> > > > > > for
> > > > > > > > > some
> > > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > > >
> > > > > > > > > > It looks like the installation process broke because of
> > some
> > > > > > function
> > > > > > > > > > renaming <https://github.com/openssl/openssl/issues/1190
> >
> > > > within
> > > > > > > > > > openssl. I'd
> > > > > > > > > > like to get some secondary validation of this issue if
> > > anybody
> > > > > else
> > > > > > > has
> > > > > > > > > an
> > > > > > > > > > environment where they can give it a shot. I think I was
> > > able
> > > > to
> > > > > > > > resolve
> > > > > > > > > > the issue by back-porting this commit
> > > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > > I just haven't had time to complete more comprehensive
> > > testing
> > > > > > (i.e.
> > > > > > > > > > spinning up quick-dev or full-dev). Once we agree on the
> > > > > > resolution
> > > > > > > to
> > > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > > >
> > > > > > > > > > building '_openssl' extension
> > > > > > > > > >
> > > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > > >
> > > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > > intel-2.7
> > > > > > > > > >
> > > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch
> > x86_64
> > > > > -arch
> > > > > > > i386
> > > > > > > > > -g
> > > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > > -DENABLE_DTRACE
> > > > > > > > > -DMACOSX
> > > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32
> > > -DNDEBUG
> > > > -g
> > > > > > > > -fwrapv
> > > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch
> x86_64
> > > > -arch
> > > > > > i386
> > > > > > > > > -pipe
> > > > > > > > > >
> -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > > include/python2.7
> > > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > >
> build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > > >
> > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6:
> error:
> > > > > > > conflicting
> > > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > > >
> > > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note:
> > > > > previous
> > > > > > > > > > declaration is here
> > > > > > > > > >
> > > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15:
> > error:
> > > > > > > > > redefinition
> > > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > > >
> > > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19:
> note:
> > > > > > previous
> > > > > > > > > > definition is here
> > > > > > > > > >
> > > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15:
> > error:
> > > > > > > > > redefinition
> > > > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > > > >
> > > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19:
> note:
> > > > > > previous
> > > > > > > > > > definition is here
> > > > > > > > > >
> > > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15:
> > error:
> > > > > > > > > redefinition
> > > > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > > > >
> > > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19:
> note:
> > > > > > previous
> > > > > > > > > > definition is here
> > > > > > > > > >
> > > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > > > > > > >
> > > > > > > > > > ^
> > > > > > > > > >
> > > > > > > > > > 4 errors generated.
> > > > > > > > > >
> > > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Jon
> > > > > > > > > > --
> > > > > > > > > >
> > > > > > > > > > Jon
> > > > > > > > > >
> > > > > > > > > > Sent from my mobile device
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > --
> > > > >
> > > > > Jon
> > > > >
> > > > > Sent from my mobile device
> > > > >
> > > >
> > > --
> > >
> > > Jon
> > >
> > > Sent from my mobile device
> > >
> >
> --
>
> Jon
>
> Sent from my mobile device
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Ok sounds good. I'm traveling next week, but if the stars align I'll
review when I get back.
Jon
On Mon, Feb 13, 2017 at 9:08 AM David Lyle <dl...@gmail.com> wrote:
> I've got a working branch that needs a bit of testing. I'm traveling this
> week, so I won't get it in a submittable state prior to next week.
>
> I didn't find anything but the issues I've already mentioned.
>
> -D...
>
> On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com> wrote:
>
> > Are you handling this one under METRON-196? I'd be happy to lend a hand
> if
> > it's easy to split up. I'd like to get this one resolved (before I
> forget
> > that it exists) either by upgrading or by fixing the documentation.
> >
> > Jon
> >
> > On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com> wrote:
> >
> > > Hi Jon,
> > >
> > > There are a few issues.
> > >
> > > So far:
> > >
> > > Ansible modules has deprecated choices=BOOLEANS in favor of type='bool'
> > > (ambari_cluster_state.py)
> > > The Ansible URI module JSON handling is broken again, I've replaced it
> > with
> > > curl in load_templates.yml
> > > Ansible's 'register' seems to have a length limitation now- that's
> > causing
> > > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > > combination of curl and grep.
> > >
> > > I'll give it a bit more and see if I can roll through it.
> > >
> > > -D...
> > >
> > >
> > > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <ze...@gmail.com>
> > > wrote:
> > >
> > > > Yes I would definitely love to use this as a reason to update
> Ansible.
> > > > I'll run it up with 2.2.1.0 as well right now.
> > > >
> > > > Jon
> > > >
> > > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com>
> > wrote:
> > > >
> > > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC there
> were
> > a
> > > > few
> > > > > issues with other versions as well. I'm spinning up quick-dev in a
> > venv
> > > > > now, I'll let you know.
> > > > >
> > > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <cestella@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Sure, of course. I thought we had some known issues with
> 2.2.1.0,
> > > but
> > > > I
> > > > > am
> > > > > > probably misremembering.
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <
> dlyle65535@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd
> like
> > > to
> > > > > > avoid
> > > > > > > backporting to Ansible if we can avoid it.
> > > > > > >
> > > > > > > -D...
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> > cestella@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hmm, that's disconcerting. I certainly don't mind
> documenting
> > > the
> > > > > > > > workaround that you've proposed in METRON-708
> > > > > > > >
> > > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > > zeolla@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Has anybody attempted to set up ansible 2.0.0.2 recently
> on a
> > > > fresh
> > > > > > mac
> > > > > > > > > using brew and the steps we outline here
> > > > > > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > > I received a new laptop this week, so I ran through some of
> > our
> > > > > setup
> > > > > > > > > documentation to test any assumptions that may exist in our
> > > > READMEs
> > > > > > > (see
> > > > > > > > > METRON-708 <
> > > https://github.com/apache/incubator-metron/pull/447>
> > > > > for
> > > > > > > > some
> > > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > > >
> > > > > > > > > It looks like the installation process broke because of
> some
> > > > > function
> > > > > > > > > renaming <https://github.com/openssl/openssl/issues/1190>
> > > within
> > > > > > > > > openssl. I'd
> > > > > > > > > like to get some secondary validation of this issue if
> > anybody
> > > > else
> > > > > > has
> > > > > > > > an
> > > > > > > > > environment where they can give it a shot. I think I was
> > able
> > > to
> > > > > > > resolve
> > > > > > > > > the issue by back-porting this commit
> > > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > > I just haven't had time to complete more comprehensive
> > testing
> > > > > (i.e.
> > > > > > > > > spinning up quick-dev or full-dev). Once we agree on the
> > > > > resolution
> > > > > > to
> > > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Here are some relevant logs taken from
> > > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > > >
> > > > > > > > > building '_openssl' extension
> > > > > > > > >
> > > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > > >
> > > > > > > > > creating build/temp.macosx-10.12-intel-
> > > > 2.7/build/temp.macosx-10.12-
> > > > > > > > > intel-2.7
> > > > > > > > >
> > > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch
> x86_64
> > > > -arch
> > > > > > i386
> > > > > > > > -g
> > > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > > -DENABLE_DTRACE
> > > > > > > > -DMACOSX
> > > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32
> > -DNDEBUG
> > > -g
> > > > > > > -fwrapv
> > > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64
> > > -arch
> > > > > i386
> > > > > > > > -pipe
> > > > > > > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > > include/python2.7
> > > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > > intel-2.7/_openssl.o
> > > > > > > > >
> > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> > > > > > conflicting
> > > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > > >
> > > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note:
> > > > previous
> > > > > > > > > declaration is here
> > > > > > > > >
> > > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15:
> error:
> > > > > > > > redefinition
> > > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > > >
> > > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note:
> > > > > previous
> > > > > > > > > definition is here
> > > > > > > > >
> > > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15:
> error:
> > > > > > > > redefinition
> > > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > > >
> > > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note:
> > > > > previous
> > > > > > > > > definition is here
> > > > > > > > >
> > > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15:
> error:
> > > > > > > > redefinition
> > > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > > >
> > > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note:
> > > > > previous
> > > > > > > > > definition is here
> > > > > > > > >
> > > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > > > > > >
> > > > > > > > > ^
> > > > > > > > >
> > > > > > > > > 4 errors generated.
> > > > > > > > >
> > > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Jon
> > > > > > > > > --
> > > > > > > > >
> > > > > > > > > Jon
> > > > > > > > >
> > > > > > > > > Sent from my mobile device
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > --
> > > >
> > > > Jon
> > > >
> > > > Sent from my mobile device
> > > >
> > >
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
I've got a working branch that needs a bit of testing. I'm traveling this
week, so I won't get it in a submittable state prior to next week.
I didn't find anything but the issues I've already mentioned.
-D...
On Mon, Feb 13, 2017 at 08:58 Zeolla@GMail.com <ze...@gmail.com> wrote:
> Are you handling this one under METRON-196? I'd be happy to lend a hand if
> it's easy to split up. I'd like to get this one resolved (before I forget
> that it exists) either by upgrading or by fixing the documentation.
>
> Jon
>
> On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com> wrote:
>
> > Hi Jon,
> >
> > There are a few issues.
> >
> > So far:
> >
> > Ansible modules has deprecated choices=BOOLEANS in favor of type='bool'
> > (ambari_cluster_state.py)
> > The Ansible URI module JSON handling is broken again, I've replaced it
> with
> > curl in load_templates.yml
> > Ansible's 'register' seems to have a length limitation now- that's
> causing
> > a problem in ansible_gather_facts ln 133. I'm fixing that with a
> > combination of curl and grep.
> >
> > I'll give it a bit more and see if I can roll through it.
> >
> > -D...
> >
> >
> > On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <ze...@gmail.com>
> > wrote:
> >
> > > Yes I would definitely love to use this as a reason to update Ansible.
> > > I'll run it up with 2.2.1.0 as well right now.
> > >
> > > Jon
> > >
> > > On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com>
> wrote:
> > >
> > > > I think that was 2.0.2.0 or 2.1.something.something. IIRC there were
> a
> > > few
> > > > issues with other versions as well. I'm spinning up quick-dev in a
> venv
> > > > now, I'll let you know.
> > > >
> > > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <ce...@gmail.com>
> > > wrote:
> > > >
> > > > > Sure, of course. I thought we had some known issues with 2.2.1.0,
> > but
> > > I
> > > > am
> > > > > probably misremembering.
> > > > >
> > > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dlyle65535@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd like
> > to
> > > > > avoid
> > > > > > backporting to Ansible if we can avoid it.
> > > > > >
> > > > > > -D...
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <
> cestella@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Hmm, that's disconcerting. I certainly don't mind documenting
> > the
> > > > > > > workaround that you've proposed in METRON-708
> > > > > > >
> > > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> > zeolla@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Has anybody attempted to set up ansible 2.0.0.2 recently on a
> > > fresh
> > > > > mac
> > > > > > > > using brew and the steps we outline here
> > > > > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > > I received a new laptop this week, so I ran through some of
> our
> > > > setup
> > > > > > > > documentation to test any assumptions that may exist in our
> > > READMEs
> > > > > > (see
> > > > > > > > METRON-708 <
> > https://github.com/apache/incubator-metron/pull/447>
> > > > for
> > > > > > > some
> > > > > > > > of my updates) before restoring my TM backup.
> > > > > > > >
> > > > > > > > It looks like the installation process broke because of some
> > > > function
> > > > > > > > renaming <https://github.com/openssl/openssl/issues/1190>
> > within
> > > > > > > > openssl. I'd
> > > > > > > > like to get some secondary validation of this issue if
> anybody
> > > else
> > > > > has
> > > > > > > an
> > > > > > > > environment where they can give it a shot. I think I was
> able
> > to
> > > > > > resolve
> > > > > > > > the issue by back-porting this commit
> > > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > > I just haven't had time to complete more comprehensive
> testing
> > > > (i.e.
> > > > > > > > spinning up quick-dev or full-dev). Once we agree on the
> > > > resolution
> > > > > to
> > > > > > > > this I can update METRON-708 appropriately.
> > > > > > > >
> > > > > > > >
> > > > > > > > Here are some relevant logs taken from
> > > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > > >
> > > > > > > > building '_openssl' extension
> > > > > > > >
> > > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > > >
> > > > > > > > creating build/temp.macosx-10.12-intel-
> > > 2.7/build/temp.macosx-10.12-
> > > > > > > > intel-2.7
> > > > > > > >
> > > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64
> > > -arch
> > > > > i386
> > > > > > > -g
> > > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > > -DENABLE_DTRACE
> > > > > > > -DMACOSX
> > > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32
> -DNDEBUG
> > -g
> > > > > > -fwrapv
> > > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64
> > -arch
> > > > i386
> > > > > > > -pipe
> > > > > > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > > include/python2.7
> > > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > > intel-2.7/_openssl.o
> > > > > > > >
> > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> > > > > conflicting
> > > > > > > > types for 'BIO_new_mem_buf'
> > > > > > > >
> > > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note:
> > > previous
> > > > > > > > declaration is here
> > > > > > > >
> > > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > > > > > > redefinition
> > > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > > >
> > > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note:
> > > > previous
> > > > > > > > definition is here
> > > > > > > >
> > > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > > > > > > redefinition
> > > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > > >
> > > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note:
> > > > previous
> > > > > > > > definition is here
> > > > > > > >
> > > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > > > > > > redefinition
> > > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > > >
> > > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note:
> > > > previous
> > > > > > > > definition is here
> > > > > > > >
> > > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > > > > >
> > > > > > > > ^
> > > > > > > >
> > > > > > > > 4 errors generated.
> > > > > > > >
> > > > > > > > error: command 'clang' failed with exit status 1
> > > > > > > >
> > > > > > > >
> > > > > > > > Jon
> > > > > > > > --
> > > > > > > >
> > > > > > > > Jon
> > > > > > > >
> > > > > > > > Sent from my mobile device
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > --
> > >
> > > Jon
> > >
> > > Sent from my mobile device
> > >
> >
> --
>
> Jon
>
> Sent from my mobile device
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Are you handling this one under METRON-196? I'd be happy to lend a hand if
it's easy to split up. I'd like to get this one resolved (before I forget
that it exists) either by upgrading or by fixing the documentation.
Jon
On Fri, Feb 10, 2017 at 2:01 PM David Lyle <dl...@gmail.com> wrote:
> Hi Jon,
>
> There are a few issues.
>
> So far:
>
> Ansible modules has deprecated choices=BOOLEANS in favor of type='bool'
> (ambari_cluster_state.py)
> The Ansible URI module JSON handling is broken again, I've replaced it with
> curl in load_templates.yml
> Ansible's 'register' seems to have a length limitation now- that's causing
> a problem in ansible_gather_facts ln 133. I'm fixing that with a
> combination of curl and grep.
>
> I'll give it a bit more and see if I can roll through it.
>
> -D...
>
>
> On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <ze...@gmail.com>
> wrote:
>
> > Yes I would definitely love to use this as a reason to update Ansible.
> > I'll run it up with 2.2.1.0 as well right now.
> >
> > Jon
> >
> > On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com> wrote:
> >
> > > I think that was 2.0.2.0 or 2.1.something.something. IIRC there were a
> > few
> > > issues with other versions as well. I'm spinning up quick-dev in a venv
> > > now, I'll let you know.
> > >
> > > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <ce...@gmail.com>
> > wrote:
> > >
> > > > Sure, of course. I thought we had some known issues with 2.2.1.0,
> but
> > I
> > > am
> > > > probably misremembering.
> > > >
> > > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dl...@gmail.com>
> > > wrote:
> > > >
> > > > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd like
> to
> > > > avoid
> > > > > backporting to Ansible if we can avoid it.
> > > > >
> > > > > -D...
> > > > >
> > > > >
> > > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Hmm, that's disconcerting. I certainly don't mind documenting
> the
> > > > > > workaround that you've proposed in METRON-708
> > > > > >
> > > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <
> zeolla@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Has anybody attempted to set up ansible 2.0.0.2 recently on a
> > fresh
> > > > mac
> > > > > > > using brew and the steps we outline here
> > > > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > > I received a new laptop this week, so I ran through some of our
> > > setup
> > > > > > > documentation to test any assumptions that may exist in our
> > READMEs
> > > > > (see
> > > > > > > METRON-708 <
> https://github.com/apache/incubator-metron/pull/447>
> > > for
> > > > > > some
> > > > > > > of my updates) before restoring my TM backup.
> > > > > > >
> > > > > > > It looks like the installation process broke because of some
> > > function
> > > > > > > renaming <https://github.com/openssl/openssl/issues/1190>
> within
> > > > > > > openssl. I'd
> > > > > > > like to get some secondary validation of this issue if anybody
> > else
> > > > has
> > > > > > an
> > > > > > > environment where they can give it a shot. I think I was able
> to
> > > > > resolve
> > > > > > > the issue by back-porting this commit
> > > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > > I just haven't had time to complete more comprehensive testing
> > > (i.e.
> > > > > > > spinning up quick-dev or full-dev). Once we agree on the
> > > resolution
> > > > to
> > > > > > > this I can update METRON-708 appropriately.
> > > > > > >
> > > > > > >
> > > > > > > Here are some relevant logs taken from
> > > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > > >
> > > > > > > building '_openssl' extension
> > > > > > >
> > > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > > >
> > > > > > > creating build/temp.macosx-10.12-intel-
> > 2.7/build/temp.macosx-10.12-
> > > > > > > intel-2.7
> > > > > > >
> > > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64
> > -arch
> > > > i386
> > > > > > -g
> > > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> > -DENABLE_DTRACE
> > > > > > -DMACOSX
> > > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG
> -g
> > > > > -fwrapv
> > > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64
> -arch
> > > i386
> > > > > > -pipe
> > > > > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > > include/python2.7
> > > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > > intel-2.7/_openssl.o
> > > > > > >
> > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> > > > conflicting
> > > > > > > types for 'BIO_new_mem_buf'
> > > > > > >
> > > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note:
> > previous
> > > > > > > declaration is here
> > > > > > >
> > > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > > > > > redefinition
> > > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > > >
> > > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note:
> > > previous
> > > > > > > definition is here
> > > > > > >
> > > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > > > > > redefinition
> > > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > > >
> > > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note:
> > > previous
> > > > > > > definition is here
> > > > > > >
> > > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > > > > > redefinition
> > > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > > >
> > > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note:
> > > previous
> > > > > > > definition is here
> > > > > > >
> > > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > > > >
> > > > > > > ^
> > > > > > >
> > > > > > > 4 errors generated.
> > > > > > >
> > > > > > > error: command 'clang' failed with exit status 1
> > > > > > >
> > > > > > >
> > > > > > > Jon
> > > > > > > --
> > > > > > >
> > > > > > > Jon
> > > > > > >
> > > > > > > Sent from my mobile device
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
Hi Jon,
There are a few issues.
So far:
Ansible modules has deprecated choices=BOOLEANS in favor of type='bool'
(ambari_cluster_state.py)
The Ansible URI module JSON handling is broken again, I've replaced it with
curl in load_templates.yml
Ansible's 'register' seems to have a length limitation now- that's causing
a problem in ansible_gather_facts ln 133. I'm fixing that with a
combination of curl and grep.
I'll give it a bit more and see if I can roll through it.
-D...
On Fri, Feb 10, 2017 at 1:48 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
> Yes I would definitely love to use this as a reason to update Ansible.
> I'll run it up with 2.2.1.0 as well right now.
>
> Jon
>
> On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com> wrote:
>
> > I think that was 2.0.2.0 or 2.1.something.something. IIRC there were a
> few
> > issues with other versions as well. I'm spinning up quick-dev in a venv
> > now, I'll let you know.
> >
> > On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <ce...@gmail.com>
> wrote:
> >
> > > Sure, of course. I thought we had some known issues with 2.2.1.0, but
> I
> > am
> > > probably misremembering.
> > >
> > > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dl...@gmail.com>
> > wrote:
> > >
> > > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to
> > > avoid
> > > > backporting to Ansible if we can avoid it.
> > > >
> > > > -D...
> > > >
> > > >
> > > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com>
> > > wrote:
> > > >
> > > > > Hmm, that's disconcerting. I certainly don't mind documenting the
> > > > > workaround that you've proposed in METRON-708
> > > > >
> > > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <zeolla@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > Has anybody attempted to set up ansible 2.0.0.2 recently on a
> fresh
> > > mac
> > > > > > using brew and the steps we outline here
> > > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > > I received a new laptop this week, so I ran through some of our
> > setup
> > > > > > documentation to test any assumptions that may exist in our
> READMEs
> > > > (see
> > > > > > METRON-708 <https://github.com/apache/incubator-metron/pull/447>
> > for
> > > > > some
> > > > > > of my updates) before restoring my TM backup.
> > > > > >
> > > > > > It looks like the installation process broke because of some
> > function
> > > > > > renaming <https://github.com/openssl/openssl/issues/1190> within
> > > > > > openssl. I'd
> > > > > > like to get some secondary validation of this issue if anybody
> else
> > > has
> > > > > an
> > > > > > environment where they can give it a shot. I think I was able to
> > > > resolve
> > > > > > the issue by back-porting this commit
> > > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > > I just haven't had time to complete more comprehensive testing
> > (i.e.
> > > > > > spinning up quick-dev or full-dev). Once we agree on the
> > resolution
> > > to
> > > > > > this I can update METRON-708 appropriately.
> > > > > >
> > > > > >
> > > > > > Here are some relevant logs taken from
> > > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > > >
> > > > > > building '_openssl' extension
> > > > > >
> > > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > > >
> > > > > > creating build/temp.macosx-10.12-intel-
> 2.7/build/temp.macosx-10.12-
> > > > > > intel-2.7
> > > > > >
> > > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64
> -arch
> > > i386
> > > > > -g
> > > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv
> -DENABLE_DTRACE
> > > > > -DMACOSX
> > > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g
> > > > -fwrapv
> > > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch
> > i386
> > > > > -pipe
> > > > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > > include/python2.7
> > > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > > intel-2.7/_openssl.o
> > > > > >
> > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> > > conflicting
> > > > > > types for 'BIO_new_mem_buf'
> > > > > >
> > > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note:
> previous
> > > > > > declaration is here
> > > > > >
> > > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > > > > redefinition
> > > > > > of 'SSLv2_method' as different kind of symbol
> > > > > >
> > > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note:
> > previous
> > > > > > definition is here
> > > > > >
> > > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > > > > redefinition
> > > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > > >
> > > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note:
> > previous
> > > > > > definition is here
> > > > > >
> > > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > > > > redefinition
> > > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > > >
> > > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note:
> > previous
> > > > > > definition is here
> > > > > >
> > > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > > >
> > > > > > ^
> > > > > >
> > > > > > 4 errors generated.
> > > > > >
> > > > > > error: command 'clang' failed with exit status 1
> > > > > >
> > > > > >
> > > > > > Jon
> > > > > > --
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > > Sent from my mobile device
> > > > > >
> > > > >
> > > >
> > >
> >
> --
>
> Jon
>
> Sent from my mobile device
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by "Zeolla@GMail.com" <ze...@gmail.com>.
Yes I would definitely love to use this as a reason to update Ansible.
I'll run it up with 2.2.1.0 as well right now.
Jon
On Fri, Feb 10, 2017, 10:06 AM David Lyle <dl...@gmail.com> wrote:
> I think that was 2.0.2.0 or 2.1.something.something. IIRC there were a few
> issues with other versions as well. I'm spinning up quick-dev in a venv
> now, I'll let you know.
>
> On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <ce...@gmail.com> wrote:
>
> > Sure, of course. I thought we had some known issues with 2.2.1.0, but I
> am
> > probably misremembering.
> >
> > On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dl...@gmail.com>
> wrote:
> >
> > > Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to
> > avoid
> > > backporting to Ansible if we can avoid it.
> > >
> > > -D...
> > >
> > >
> > > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com>
> > wrote:
> > >
> > > > Hmm, that's disconcerting. I certainly don't mind documenting the
> > > > workaround that you've proposed in METRON-708
> > > >
> > > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <ze...@gmail.com>
> > > wrote:
> > > >
> > > > > Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh
> > mac
> > > > > using brew and the steps we outline here
> > > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > > I received a new laptop this week, so I ran through some of our
> setup
> > > > > documentation to test any assumptions that may exist in our READMEs
> > > (see
> > > > > METRON-708 <https://github.com/apache/incubator-metron/pull/447>
> for
> > > > some
> > > > > of my updates) before restoring my TM backup.
> > > > >
> > > > > It looks like the installation process broke because of some
> function
> > > > > renaming <https://github.com/openssl/openssl/issues/1190> within
> > > > > openssl. I'd
> > > > > like to get some secondary validation of this issue if anybody else
> > has
> > > > an
> > > > > environment where they can give it a shot. I think I was able to
> > > resolve
> > > > > the issue by back-porting this commit
> > > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > > I just haven't had time to complete more comprehensive testing
> (i.e.
> > > > > spinning up quick-dev or full-dev). Once we agree on the
> resolution
> > to
> > > > > this I can update METRON-708 appropriately.
> > > > >
> > > > >
> > > > > Here are some relevant logs taken from
> > > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > > >
> > > > > building '_openssl' extension
> > > > >
> > > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > > >
> > > > > creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > intel-2.7
> > > > >
> > > > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch
> > i386
> > > > -g
> > > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE
> > > > -DMACOSX
> > > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g
> > > -fwrapv
> > > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch
> i386
> > > > -pipe
> > > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > > include/python2.7
> > > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > > intel-2.7/_openssl.o
> > > > >
> > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> > conflicting
> > > > > types for 'BIO_new_mem_buf'
> > > > >
> > > > > BIO *BIO_new_mem_buf(void *, int);
> > > > >
> > > > > ^
> > > > >
> > > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> > > > > declaration is here
> > > > >
> > > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > > >
> > > > > ^
> > > > >
> > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > > > redefinition
> > > > > of 'SSLv2_method' as different kind of symbol
> > > > >
> > > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > > >
> > > > > ^
> > > > >
> > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note:
> previous
> > > > > definition is here
> > > > >
> > > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > > >
> > > > > ^
> > > > >
> > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > > > redefinition
> > > > > of 'SSLv2_client_method' as different kind of symbol
> > > > >
> > > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > > >
> > > > > ^
> > > > >
> > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note:
> previous
> > > > > definition is here
> > > > >
> > > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > > >
> > > > > ^
> > > > >
> > > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > > > redefinition
> > > > > of 'SSLv2_server_method' as different kind of symbol
> > > > >
> > > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > > >
> > > > > ^
> > > > >
> > > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note:
> previous
> > > > > definition is here
> > > > >
> > > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > > >
> > > > > ^
> > > > >
> > > > > 4 errors generated.
> > > > >
> > > > > error: command 'clang' failed with exit status 1
> > > > >
> > > > >
> > > > > Jon
> > > > > --
> > > > >
> > > > > Jon
> > > > >
> > > > > Sent from my mobile device
> > > > >
> > > >
> > >
> >
>
--
Jon
Sent from my mobile device
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
I think that was 2.0.2.0 or 2.1.something.something. IIRC there were a few
issues with other versions as well. I'm spinning up quick-dev in a venv
now, I'll let you know.
On Fri, Feb 10, 2017 at 10:02 AM, Casey Stella <ce...@gmail.com> wrote:
> Sure, of course. I thought we had some known issues with 2.2.1.0, but I am
> probably misremembering.
>
> On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dl...@gmail.com> wrote:
>
> > Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to
> avoid
> > backporting to Ansible if we can avoid it.
> >
> > -D...
> >
> >
> > On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com>
> wrote:
> >
> > > Hmm, that's disconcerting. I certainly don't mind documenting the
> > > workaround that you've proposed in METRON-708
> > >
> > > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <ze...@gmail.com>
> > wrote:
> > >
> > > > Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh
> mac
> > > > using brew and the steps we outline here
> > > > <https://github.com/apache/incubator-metron/tree/master/
> > > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > > I received a new laptop this week, so I ran through some of our setup
> > > > documentation to test any assumptions that may exist in our READMEs
> > (see
> > > > METRON-708 <https://github.com/apache/incubator-metron/pull/447> for
> > > some
> > > > of my updates) before restoring my TM backup.
> > > >
> > > > It looks like the installation process broke because of some function
> > > > renaming <https://github.com/openssl/openssl/issues/1190> within
> > > > openssl. I'd
> > > > like to get some secondary validation of this issue if anybody else
> has
> > > an
> > > > environment where they can give it a shot. I think I was able to
> > resolve
> > > > the issue by back-porting this commit
> > > > <https://github.com/Homebrew/homebrew-core/commit/
> > > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > > I just haven't had time to complete more comprehensive testing (i.e.
> > > > spinning up quick-dev or full-dev). Once we agree on the resolution
> to
> > > > this I can update METRON-708 appropriately.
> > > >
> > > >
> > > > Here are some relevant logs taken from
> > > > ~/Library/Logs/Homebrew/ansible/09.python:
> > > >
> > > > building '_openssl' extension
> > > >
> > > > creating build/temp.macosx-10.12-intel-2.7/build
> > > >
> > > > creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > intel-2.7
> > > >
> > > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch
> i386
> > > -g
> > > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE
> > > -DMACOSX
> > > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g
> > -fwrapv
> > > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386
> > > -pipe
> > > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > > include/python2.7
> > > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > > intel-2.7/_openssl.o
> > > >
> > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error:
> conflicting
> > > > types for 'BIO_new_mem_buf'
> > > >
> > > > BIO *BIO_new_mem_buf(void *, int);
> > > >
> > > > ^
> > > >
> > > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> > > > declaration is here
> > > >
> > > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > > >
> > > > ^
> > > >
> > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > > redefinition
> > > > of 'SSLv2_method' as different kind of symbol
> > > >
> > > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > > >
> > > > ^
> > > >
> > > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
> > > > definition is here
> > > >
> > > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > > >
> > > > ^
> > > >
> > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > > redefinition
> > > > of 'SSLv2_client_method' as different kind of symbol
> > > >
> > > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > > >
> > > > ^
> > > >
> > > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
> > > > definition is here
> > > >
> > > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > > >
> > > > ^
> > > >
> > > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > > redefinition
> > > > of 'SSLv2_server_method' as different kind of symbol
> > > >
> > > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > > >
> > > > ^
> > > >
> > > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
> > > > definition is here
> > > >
> > > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > > >
> > > > ^
> > > >
> > > > 4 errors generated.
> > > >
> > > > error: command 'clang' failed with exit status 1
> > > >
> > > >
> > > > Jon
> > > > --
> > > >
> > > > Jon
> > > >
> > > > Sent from my mobile device
> > > >
> > >
> >
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by Casey Stella <ce...@gmail.com>.
Sure, of course. I thought we had some known issues with 2.2.1.0, but I am
probably misremembering.
On Fri, Feb 10, 2017 at 10:01 AM, David Lyle <dl...@gmail.com> wrote:
> Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to avoid
> backporting to Ansible if we can avoid it.
>
> -D...
>
>
> On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com> wrote:
>
> > Hmm, that's disconcerting. I certainly don't mind documenting the
> > workaround that you've proposed in METRON-708
> >
> > On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <ze...@gmail.com>
> wrote:
> >
> > > Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac
> > > using brew and the steps we outline here
> > > <https://github.com/apache/incubator-metron/tree/master/
> > > metron-deployment/vagrant/full-dev-platform#os-x>?
> > > I received a new laptop this week, so I ran through some of our setup
> > > documentation to test any assumptions that may exist in our READMEs
> (see
> > > METRON-708 <https://github.com/apache/incubator-metron/pull/447> for
> > some
> > > of my updates) before restoring my TM backup.
> > >
> > > It looks like the installation process broke because of some function
> > > renaming <https://github.com/openssl/openssl/issues/1190> within
> > > openssl. I'd
> > > like to get some secondary validation of this issue if anybody else has
> > an
> > > environment where they can give it a shot. I think I was able to
> resolve
> > > the issue by back-porting this commit
> > > <https://github.com/Homebrew/homebrew-core/commit/
> > > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > > I just haven't had time to complete more comprehensive testing (i.e.
> > > spinning up quick-dev or full-dev). Once we agree on the resolution to
> > > this I can update METRON-708 appropriately.
> > >
> > >
> > > Here are some relevant logs taken from
> > > ~/Library/Logs/Homebrew/ansible/09.python:
> > >
> > > building '_openssl' extension
> > >
> > > creating build/temp.macosx-10.12-intel-2.7/build
> > >
> > > creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > intel-2.7
> > >
> > > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386
> > -g
> > > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE
> > -DMACOSX
> > > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g
> -fwrapv
> > > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386
> > -pipe
> > > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > > include/python2.7
> > > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > > intel-2.7/_openssl.o
> > >
> > > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error: conflicting
> > > types for 'BIO_new_mem_buf'
> > >
> > > BIO *BIO_new_mem_buf(void *, int);
> > >
> > > ^
> > >
> > > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> > > declaration is here
> > >
> > > BIO *BIO_new_mem_buf(const void *buf, int len);
> > >
> > > ^
> > >
> > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> > redefinition
> > > of 'SSLv2_method' as different kind of symbol
> > >
> > > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> > >
> > > ^
> > >
> > > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
> > > definition is here
> > >
> > > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> > >
> > > ^
> > >
> > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> > redefinition
> > > of 'SSLv2_client_method' as different kind of symbol
> > >
> > > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> > >
> > > ^
> > >
> > > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
> > > definition is here
> > >
> > > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> > >
> > > ^
> > >
> > > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> > redefinition
> > > of 'SSLv2_server_method' as different kind of symbol
> > >
> > > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> > >
> > > ^
> > >
> > > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
> > > definition is here
> > >
> > > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> > >
> > > ^
> > >
> > > 4 errors generated.
> > >
> > > error: command 'clang' failed with exit status 1
> > >
> > >
> > > Jon
> > > --
> > >
> > > Jon
> > >
> > > Sent from my mobile device
> > >
> >
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by David Lyle <dl...@gmail.com>.
Would it make sense to give Ansible 2.2.1.0 a try first? I'd like to avoid
backporting to Ansible if we can avoid it.
-D...
On Fri, Feb 10, 2017 at 9:26 AM, Casey Stella <ce...@gmail.com> wrote:
> Hmm, that's disconcerting. I certainly don't mind documenting the
> workaround that you've proposed in METRON-708
>
> On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
>
> > Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac
> > using brew and the steps we outline here
> > <https://github.com/apache/incubator-metron/tree/master/
> > metron-deployment/vagrant/full-dev-platform#os-x>?
> > I received a new laptop this week, so I ran through some of our setup
> > documentation to test any assumptions that may exist in our READMEs (see
> > METRON-708 <https://github.com/apache/incubator-metron/pull/447> for
> some
> > of my updates) before restoring my TM backup.
> >
> > It looks like the installation process broke because of some function
> > renaming <https://github.com/openssl/openssl/issues/1190> within
> > openssl. I'd
> > like to get some secondary validation of this issue if anybody else has
> an
> > environment where they can give it a shot. I think I was able to resolve
> > the issue by back-porting this commit
> > <https://github.com/Homebrew/homebrew-core/commit/
> > e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> > I just haven't had time to complete more comprehensive testing (i.e.
> > spinning up quick-dev or full-dev). Once we agree on the resolution to
> > this I can update METRON-708 appropriately.
> >
> >
> > Here are some relevant logs taken from
> > ~/Library/Logs/Homebrew/ansible/09.python:
> >
> > building '_openssl' extension
> >
> > creating build/temp.macosx-10.12-intel-2.7/build
> >
> > creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > intel-2.7
> >
> > clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386
> -g
> > -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE
> -DMACOSX
> > -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv
> > -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386
> -pipe
> > -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> > include/python2.7
> > -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> > build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> > intel-2.7/_openssl.o
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error: conflicting
> > types for 'BIO_new_mem_buf'
> >
> > BIO *BIO_new_mem_buf(void *, int);
> >
> > ^
> >
> > /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> > declaration is here
> >
> > BIO *BIO_new_mem_buf(const void *buf, int len);
> >
> > ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error:
> redefinition
> > of 'SSLv2_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_method)(void) = NULL;
> >
> > ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
> >
> > ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error:
> redefinition
> > of 'SSLv2_client_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
> >
> > ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
> >
> > ^
> >
> > build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error:
> redefinition
> > of 'SSLv2_server_method' as different kind of symbol
> >
> > SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
> >
> > ^
> >
> > /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
> > definition is here
> >
> > const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
> >
> > ^
> >
> > 4 errors generated.
> >
> > error: command 'clang' failed with exit status 1
> >
> >
> > Jon
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>
Re: Unable to build Ansible 2.0.0.2 on macOS using our instructions
Posted by Casey Stella <ce...@gmail.com>.
Hmm, that's disconcerting. I certainly don't mind documenting the
workaround that you've proposed in METRON-708
On Thu, Feb 9, 2017 at 1:05 PM, Zeolla@GMail.com <ze...@gmail.com> wrote:
> Has anybody attempted to set up ansible 2.0.0.2 recently on a fresh mac
> using brew and the steps we outline here
> <https://github.com/apache/incubator-metron/tree/master/
> metron-deployment/vagrant/full-dev-platform#os-x>?
> I received a new laptop this week, so I ran through some of our setup
> documentation to test any assumptions that may exist in our READMEs (see
> METRON-708 <https://github.com/apache/incubator-metron/pull/447> for some
> of my updates) before restoring my TM backup.
>
> It looks like the installation process broke because of some function
> renaming <https://github.com/openssl/openssl/issues/1190> within
> openssl. I'd
> like to get some secondary validation of this issue if anybody else has an
> environment where they can give it a shot. I think I was able to resolve
> the issue by back-porting this commit
> <https://github.com/Homebrew/homebrew-core/commit/
> e08a5323e9d06a70dae20bc7b2387fbe9af983a8>,
> I just haven't had time to complete more comprehensive testing (i.e.
> spinning up quick-dev or full-dev). Once we agree on the resolution to
> this I can update METRON-708 appropriately.
>
>
> Here are some relevant logs taken from
> ~/Library/Logs/Homebrew/ansible/09.python:
>
> building '_openssl' extension
>
> creating build/temp.macosx-10.12-intel-2.7/build
>
> creating build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> intel-2.7
>
> clang -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g
> -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE -DMACOSX
> -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv
> -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe
> -I/System/Library/Frameworks/Python.framework/Versions/2.7/
> include/python2.7
> -c build/temp.macosx-10.12-intel-2.7/_openssl.c -o
> build/temp.macosx-10.12-intel-2.7/build/temp.macosx-10.12-
> intel-2.7/_openssl.o
>
> build/temp.macosx-10.12-intel-2.7/_openssl.c:710:6: error: conflicting
> types for 'BIO_new_mem_buf'
>
> BIO *BIO_new_mem_buf(void *, int);
>
> ^
>
> /usr/local/opt/openssl/include/openssl/bio.h:692:6: note: previous
> declaration is here
>
> BIO *BIO_new_mem_buf(const void *buf, int len);
>
> ^
>
> build/temp.macosx-10.12-intel-2.7/_openssl.c:2089:15: error: redefinition
> of 'SSLv2_method' as different kind of symbol
>
> SSL_METHOD* (*SSLv2_method)(void) = NULL;
>
> ^
>
> /usr/local/opt/openssl/include/openssl/ssl.h:2349:19: note: previous
> definition is here
>
> const SSL_METHOD *SSLv2_method(void); /* SSLv2 */
>
> ^
>
> build/temp.macosx-10.12-intel-2.7/_openssl.c:2090:15: error: redefinition
> of 'SSLv2_client_method' as different kind of symbol
>
> SSL_METHOD* (*SSLv2_client_method)(void) = NULL;
>
> ^
>
> /usr/local/opt/openssl/include/openssl/ssl.h:2351:19: note: previous
> definition is here
>
> const SSL_METHOD *SSLv2_client_method(void); /* SSLv2 */
>
> ^
>
> build/temp.macosx-10.12-intel-2.7/_openssl.c:2091:15: error: redefinition
> of 'SSLv2_server_method' as different kind of symbol
>
> SSL_METHOD* (*SSLv2_server_method)(void) = NULL;
>
> ^
>
> /usr/local/opt/openssl/include/openssl/ssl.h:2350:19: note: previous
> definition is here
>
> const SSL_METHOD *SSLv2_server_method(void); /* SSLv2 */
>
> ^
>
> 4 errors generated.
>
> error: command 'clang' failed with exit status 1
>
>
> Jon
> --
>
> Jon
>
> Sent from my mobile device
>