You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2015/11/14 02:20:18 UTC

Any recent changes to the docker images?

Looks like our docker images don't have ant anymore... I see (at least) datafu
and solr builds failing on all platforms because of that...

By looking into git history I don't see any evidences of it, but the builds
are failing nonetheless... Thoughts?

Cos

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Peter Linnell <pl...@apache.org>.
Hi,

Those "extra packages" have been needed to build HUE among others since
Hadoop 1.x days. They should be installable in SLES 11 or 12 if you
have the SDK repo enabled.

All should be available in openSUSE for a long time...

Ping me on IRC to discuss.

I'm back from SUSECon in Amsterdam, so I won't be so invisible. Plus my
travel is less insane ;)  (I've been in a plane 23 of the last 25
weeks.)

Cheers,
Peter

On Wed, 18 Nov 2015 11:56:09 +0800
Evans Ye <ev...@apache.org> wrote:

> Okay, it seems these extra packages introduced in BIGTOP-2120 brings
> up the issue:
> 
> "python-devel", "python-setuptools", "libxml2-devel",
> "libxslt-devel", " cyrus-sasl-devel", "sqlite3-devel",
> "openldap2-devel", "libyaml-devel", " krb5-devel", "asciidoc",
> "libmysqlclient-devel"
> 
> 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
> > I haven't seen Peter for awhile, he might know the answer or have a
> > fix for it.
> >
> > Cos
> >
> > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:  
> > > You got it. The opensuse image is failing for a long while
> > > (All the trunk images will be rebuilt after code change
> > > regardless  
> > whether  
> > > it's failing or not
> > > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > >
> > > The maven things is just some network issue which can be solved
> > > by rerun. However, the package confliction is a bit more
> > > difficult to handle.
> > >
> > > The build was still ok back in Nov. 8
> > >  
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/  
> > >
> > > The only two changes during these days are:
> > > 1. add gmp-devel
> > > 2. remove krb5-mini
> > >  
> > https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp  
> > >
> > > Which seems not related to me.
> > > I don't have awswer yet and still looking into it...
> > >
> > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > >  
> > > > Looking into the recent builds on Suse I see that pretty much
> > > > all of  
> > them  
> > > > are
> > > > failing for two reasons:
> > > >  - mvn isn't found
> > > >  - some lib requirements aren't met
> > > >
> > > > While the former seems like a small omission in the container,
> > > > the  
> > other  
> > > > one
> > > > looks like a bigger issue with the toolchain. I personally
> > > > don't have  
> > any  
> > > > cycles to work on this.
> > > >
> > > > Thoughts?
> > > >   Cos
> > > >
> > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:  
> > > > > Yeah, that was caused by that images has been changed.
> > > > > For some unknown reason the ant installation failed:
> > > > >
> > > > >  
> > > >  
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console  
> > > > >
> > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > >  [91m [1;31mError: /usr/bin/wget
> > > > >  
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz  
> > > > > returned 8 instead of one of [0] [0m
> > > > >  [0m [91m [1;31mError:
> > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > >  
> > > >  
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns  
> > > > :  
> > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > >  
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz  
> > > > > returned 8 instead of one of [0] [0m
> > > > >  [0m
> > > > > [mNotice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget 
> > > >  
> > http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns  
> > > > :  
> > > > > executed successfully [0m
> > > > >
> > > > >
> > > > > But the build continue to do downstream image push and pull
> > > > > because puppet apply returns 0 even with errors.
> > > > >
> > > > > Let me rerun this first and then try to add some thing
> > > > > prevent things happened again.
> > > > >
> > > > >
> > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > >  
> > > > > > Looks like our docker images don't have ant anymore... I
> > > > > > see (at  
> > least)  
> > > > > > datafu
> > > > > > and solr builds failing on all platforms because of that...
> > > > > >
> > > > > > By looking into git history I don't see any evidences of
> > > > > > it, but  
> > the  
> > > > builds  
> > > > > > are failing nonetheless... Thoughts?
> > > > > >
> > > > > > Cos
> > > > > >  
> > > >  
> >

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Olaf Flebbe <of...@oflebbe.de>.
Seems there is a easy fix. Will try to provide it with BIGTOP-2152

Olaf
> Am 18.11.2015 um 20:45 schrieb Konstantin Boudnik <co...@apache.org>:
> 
> On Wed, Nov 18, 2015 at 10:39AM, Olaf Flebbe wrote:
>> Hi,
>> 
>> Yep I broke it. ;-/   But opensuse broke itself, too. As far as I can tell
>> this change came from a suse update to the OS container.
>> 
>> Of course openssl and libressl cannot coexist, since libressl replaces
>> openssl. The docker images are weird.  I will look into it this evening if I
>> can work out  a quick fix.
>> 
>> If a quick fix is not found,  I propose to drop support for opensuse 13.2, now.
>> 
>> Propose to make a vote to support opensuse leap 42.1 instead or drop it
>> completly. Perhaps this will not make it into the release in time, since
>> there are a lot of issues for SuSE pending.
> 
> That might be a way to go, if it indeed solves the problem we see.
> 
>> In the wild I have seen more requests for SLES support then for openSuSE.
>> but we cannot support SLES since we are not allowed to push docker of it
>> images to the public. Peter: Are there solutions to this problem ? We are
>> right now not in the technical position to use the SuSE Build service.
>> 
>> --Olaf
>> 
>> 
>> 
>>> Am 18.11.2015 um 10:09 schrieb Evans Ye <ev...@apache.org>:
>>> 
>>> It looks like the two packages truly(libressl-devel and libopenssl-devel)
>>> can't co-exist on opensuse:
>>> 
>>> ---------------------------------------------------------------------------------------------------------
>>> $ docker pull opensuse:13.2
>>> 13.2: Pulling from opensuse
>>> 717905e6e6af: Pull complete
>>> 5b8dd08af89b: Already exists
>>> Digest:
>>> sha256:325785de46c5c706fc529f28d4f6f70db1b7d57f82a9d328ab945425959741e7
>>> Status: Downloaded newer image for opensuse:13.2
>>> $ docker run -ti --rm opensuse:13.2 bash
>>> bash-4.2# zypper install libressl-devel libopenssl-devel
>>> Retrieving repository 'NON-OSS' metadata
>>> ..............................................................................................................[done]
>>> Building repository 'NON-OSS' cache
>>> ...................................................................................................................[done]
>>> Retrieving repository 'OSS' metadata
>>> ..................................................................................................................[done]
>>> Building repository 'OSS' cache
>>> .......................................................................................................................[done]
>>> Retrieving repository 'OSS Update' metadata
>>> ...........................................................................................................[done]
>>> Building repository 'OSS Update' cache
>>> ................................................................................................................[done]
>>> Retrieving repository 'Update Non-Oss' metadata
>>> .......................................................................................................[done]
>>> Building repository 'Update Non-Oss' cache
>>> ............................................................................................................[done]
>>> Loading repository data...
>>> Reading installed packages...
>>> Resolving package dependencies...
>>> 
>>> Problem: libressl-devel-2.2.1-2.6.1.x86_64 conflicts with libopenssl-devel
>>> provided by libopenssl-devel-1.0.1k-2.24.1.x86_64
>>> Solution 1: do not install libressl-devel-2.2.1-2.6.1.x86_64
>>> Solution 2: do not install libopenssl-devel-1.0.1k-2.24.1.x86_64
>>> 
>>> Choose from above solutions by number or cancel [1/2/c] (c):
>>> ---------------------------------------------------------------------------------------------------------
>>> 
>>> For the record libressl-devel is depended by libmysqlclient-devel
>>> I have no idea how to proceed now, shall we upstream the problem?
>>> 
>>> 2015-11-18 15:11 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>> 
>>>> On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
>>>>> Well, I need to turn myself in.
>>>> 
>>>> Doesn't matter man - it was a joke ;)
>>>> 
>>>>> In fact that patch has been tested and +1ed by me,
>>>>> but I remember my manual build was OK by then...
>>>> 
>>>> With the complexities like that - this stuff happens, unfortunately. We
>>>> already weeded out a bunch of issues by switching to standardized
>>>> toolchains
>>>> and build environments. I am pretty sure we'll figure out this one as well.
>>>> 
>>>>> Anyhow, I can't understand why it has conflict when we only install
>>>>> packages available from official repo...
>>>> 
>>>> Yeah, that's weird ;( unless the official packages have some issues, which
>>>> isn't likely I suppose.
>>>> 
>>>> Cos
>>>> 
>>>> 
>>>>> 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>>>> 
>>>>>> Well, perhaps now Olaf won't brag as much ;)
>>>>>> 
>>>>>> (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
>>>>>> 
>>>>>> Cos
>>>>>> 
>>>>>> On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
>>>>>>> Okay, it seems these extra packages introduced in BIGTOP-2120 brings
>>>> up
>>>>>> the
>>>>>>> issue:
>>>>>>> 
>>>>>>> "python-devel", "python-setuptools", "libxml2-devel",
>>>> "libxslt-devel", "
>>>>>>> cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel",
>>>> "libyaml-devel", "
>>>>>>> krb5-devel", "asciidoc", "libmysqlclient-devel"
>>>>>>> 
>>>>>>> 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>>>>>> 
>>>>>>>> I haven't seen Peter for awhile, he might know the answer or have a
>>>>>> fix for
>>>>>>>> it.
>>>>>>>> 
>>>>>>>> Cos
>>>>>>>> 
>>>>>>>> On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
>>>>>>>>> You got it. The opensuse image is failing for a long while
>>>>>>>>> (All the trunk images will be rebuilt after code change
>>>> regardless
>>>>>>>> whether
>>>>>>>>> it's failing or not
>>>>>>>>> 
>>>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
>>>>>>>>> 
>>>>>>>>> The maven things is just some network issue which can be solved
>>>> by
>>>>>> rerun.
>>>>>>>>> However, the package confliction is a bit more difficult to
>>>> handle.
>>>>>>>>> 
>>>>>>>>> The build was still ok back in Nov. 8
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
>>>>>>>>> 
>>>>>>>>> The only two changes during these days are:
>>>>>>>>> 1. add gmp-devel
>>>>>>>>> 2. remove krb5-mini
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
>>>>>>>>> 
>>>>>>>>> Which seems not related to me.
>>>>>>>>> I don't have awswer yet and still looking into it...
>>>>>>>>> 
>>>>>>>>> 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>>>>>>>> 
>>>>>>>>>> Looking into the recent builds on Suse I see that pretty much
>>>> all
>>>>>> of
>>>>>>>> them
>>>>>>>>>> are
>>>>>>>>>> failing for two reasons:
>>>>>>>>>> - mvn isn't found
>>>>>>>>>> - some lib requirements aren't met
>>>>>>>>>> 
>>>>>>>>>> While the former seems like a small omission in the container,
>>>> the
>>>>>>>> other
>>>>>>>>>> one
>>>>>>>>>> looks like a bigger issue with the toolchain. I personally
>>>> don't
>>>>>> have
>>>>>>>> any
>>>>>>>>>> cycles to work on this.
>>>>>>>>>> 
>>>>>>>>>> Thoughts?
>>>>>>>>>> Cos
>>>>>>>>>> 
>>>>>>>>>> On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
>>>>>>>>>>> Yeah, that was caused by that images has been changed.
>>>>>>>>>>> For some unknown reason the ant installation failed:
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
>>>>>>>>>>> 
>>>>>>>>>>> 14:40:11 ERROR 404: Not Found. [0m
>>>>>>>>>>> [91m [1;31mError: /usr/bin/wget
>>>>>>>>>>> 
>>>>>>>> 
>>>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
>>>>>>>>>>> returned 8 instead of one of [0] [0m
>>>>>>>>>>> [0m [91m [1;31mError:
>>>>>>>>>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
>>>>>>>>>> :
>>>>>>>>>>> change from notrun to 0 failed: /usr/bin/wget
>>>>>>>>>>> 
>>>>>>>> 
>>>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
>>>>>>>>>>> returned 8 instead of one of [0] [0m
>>>>>>>>>>> [0m [mNotice:
>>>>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
>>>>>>>>>> :
>>>>>>>>>>> executed successfully [0m
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> But the build continue to do downstream image push and pull
>>>>>> because
>>>>>>>>>>> puppet apply returns 0 even with errors.
>>>>>>>>>>> 
>>>>>>>>>>> Let me rerun this first and then try to add some thing
>>>> prevent
>>>>>> things
>>>>>>>>>>> happened again.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <cos@apache.org
>>>>> :
>>>>>>>>>>> 
>>>>>>>>>>>> Looks like our docker images don't have ant anymore... I
>>>> see
>>>>>> (at
>>>>>>>> least)
>>>>>>>>>>>> datafu
>>>>>>>>>>>> and solr builds failing on all platforms because of that...
>>>>>>>>>>>> 
>>>>>>>>>>>> By looking into git history I don't see any evidences of
>>>> it,
>>>>>> but
>>>>>>>> the
>>>>>>>>>> builds
>>>>>>>>>>>> are failing nonetheless... Thoughts?
>>>>>>>>>>>> 
>>>>>>>>>>>> Cos
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>> 
> 
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Nov 18, 2015 at 10:39AM, Olaf Flebbe wrote:
> Hi,
> 
> Yep I broke it. ;-/   But opensuse broke itself, too. As far as I can tell
> this change came from a suse update to the OS container.
> 
> Of course openssl and libressl cannot coexist, since libressl replaces
> openssl. The docker images are weird.  I will look into it this evening if I
> can work out  a quick fix.
> 
> If a quick fix is not found,  I propose to drop support for opensuse 13.2, now.
> 
> Propose to make a vote to support opensuse leap 42.1 instead or drop it
> completly. Perhaps this will not make it into the release in time, since
> there are a lot of issues for SuSE pending.

That might be a way to go, if it indeed solves the problem we see.

> In the wild I have seen more requests for SLES support then for openSuSE.
> but we cannot support SLES since we are not allowed to push docker of it
> images to the public. Peter: Are there solutions to this problem ? We are
> right now not in the technical position to use the SuSE Build service.
> 
> --Olaf
> 
> 
> 
> > Am 18.11.2015 um 10:09 schrieb Evans Ye <ev...@apache.org>:
> > 
> > It looks like the two packages truly(libressl-devel and libopenssl-devel)
> > can't co-exist on opensuse:
> > 
> > ---------------------------------------------------------------------------------------------------------
> > $ docker pull opensuse:13.2
> > 13.2: Pulling from opensuse
> > 717905e6e6af: Pull complete
> > 5b8dd08af89b: Already exists
> > Digest:
> > sha256:325785de46c5c706fc529f28d4f6f70db1b7d57f82a9d328ab945425959741e7
> > Status: Downloaded newer image for opensuse:13.2
> > $ docker run -ti --rm opensuse:13.2 bash
> > bash-4.2# zypper install libressl-devel libopenssl-devel
> > Retrieving repository 'NON-OSS' metadata
> > ..............................................................................................................[done]
> > Building repository 'NON-OSS' cache
> > ...................................................................................................................[done]
> > Retrieving repository 'OSS' metadata
> > ..................................................................................................................[done]
> > Building repository 'OSS' cache
> > .......................................................................................................................[done]
> > Retrieving repository 'OSS Update' metadata
> > ...........................................................................................................[done]
> > Building repository 'OSS Update' cache
> > ................................................................................................................[done]
> > Retrieving repository 'Update Non-Oss' metadata
> > .......................................................................................................[done]
> > Building repository 'Update Non-Oss' cache
> > ............................................................................................................[done]
> > Loading repository data...
> > Reading installed packages...
> > Resolving package dependencies...
> > 
> > Problem: libressl-devel-2.2.1-2.6.1.x86_64 conflicts with libopenssl-devel
> > provided by libopenssl-devel-1.0.1k-2.24.1.x86_64
> > Solution 1: do not install libressl-devel-2.2.1-2.6.1.x86_64
> > Solution 2: do not install libopenssl-devel-1.0.1k-2.24.1.x86_64
> > 
> > Choose from above solutions by number or cancel [1/2/c] (c):
> > ---------------------------------------------------------------------------------------------------------
> > 
> > For the record libressl-devel is depended by libmysqlclient-devel
> > I have no idea how to proceed now, shall we upstream the problem?
> > 
> > 2015-11-18 15:11 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > 
> >> On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
> >>> Well, I need to turn myself in.
> >> 
> >> Doesn't matter man - it was a joke ;)
> >> 
> >>> In fact that patch has been tested and +1ed by me,
> >>> but I remember my manual build was OK by then...
> >> 
> >> With the complexities like that - this stuff happens, unfortunately. We
> >> already weeded out a bunch of issues by switching to standardized
> >> toolchains
> >> and build environments. I am pretty sure we'll figure out this one as well.
> >> 
> >>> Anyhow, I can't understand why it has conflict when we only install
> >>> packages available from official repo...
> >> 
> >> Yeah, that's weird ;( unless the official packages have some issues, which
> >> isn't likely I suppose.
> >> 
> >> Cos
> >> 
> >> 
> >>> 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >>> 
> >>>> Well, perhaps now Olaf won't brag as much ;)
> >>>> 
> >>>> (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
> >>>> 
> >>>> Cos
> >>>> 
> >>>> On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> >>>>> Okay, it seems these extra packages introduced in BIGTOP-2120 brings
> >> up
> >>>> the
> >>>>> issue:
> >>>>> 
> >>>>> "python-devel", "python-setuptools", "libxml2-devel",
> >> "libxslt-devel", "
> >>>>> cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel",
> >> "libyaml-devel", "
> >>>>> krb5-devel", "asciidoc", "libmysqlclient-devel"
> >>>>> 
> >>>>> 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >>>>> 
> >>>>>> I haven't seen Peter for awhile, he might know the answer or have a
> >>>> fix for
> >>>>>> it.
> >>>>>> 
> >>>>>> Cos
> >>>>>> 
> >>>>>> On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> >>>>>>> You got it. The opensuse image is failing for a long while
> >>>>>>> (All the trunk images will be rebuilt after code change
> >> regardless
> >>>>>> whether
> >>>>>>> it's failing or not
> >>>>>>> 
> >> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> >>>>>>> 
> >>>>>>> The maven things is just some network issue which can be solved
> >> by
> >>>> rerun.
> >>>>>>> However, the package confliction is a bit more difficult to
> >> handle.
> >>>>>>> 
> >>>>>>> The build was still ok back in Nov. 8
> >>>>>>> 
> >>>>>> 
> >>>> 
> >> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> >>>>>>> 
> >>>>>>> The only two changes during these days are:
> >>>>>>> 1. add gmp-devel
> >>>>>>> 2. remove krb5-mini
> >>>>>>> 
> >>>>>> 
> >>>> 
> >> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> >>>>>>> 
> >>>>>>> Which seems not related to me.
> >>>>>>> I don't have awswer yet and still looking into it...
> >>>>>>> 
> >>>>>>> 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >>>>>>> 
> >>>>>>>> Looking into the recent builds on Suse I see that pretty much
> >> all
> >>>> of
> >>>>>> them
> >>>>>>>> are
> >>>>>>>> failing for two reasons:
> >>>>>>>> - mvn isn't found
> >>>>>>>> - some lib requirements aren't met
> >>>>>>>> 
> >>>>>>>> While the former seems like a small omission in the container,
> >> the
> >>>>>> other
> >>>>>>>> one
> >>>>>>>> looks like a bigger issue with the toolchain. I personally
> >> don't
> >>>> have
> >>>>>> any
> >>>>>>>> cycles to work on this.
> >>>>>>>> 
> >>>>>>>> Thoughts?
> >>>>>>>>  Cos
> >>>>>>>> 
> >>>>>>>> On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> >>>>>>>>> Yeah, that was caused by that images has been changed.
> >>>>>>>>> For some unknown reason the ant installation failed:
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>> 
> >>>> 
> >> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> >>>>>>>>> 
> >>>>>>>>> 14:40:11 ERROR 404: Not Found. [0m
> >>>>>>>>> [91m [1;31mError: /usr/bin/wget
> >>>>>>>>> 
> >>>>>> 
> >> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> >>>>>>>>> returned 8 instead of one of [0] [0m
> >>>>>>>>> [0m [91m [1;31mError:
> >>>>>>>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>> 
> >>>> 
> >> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> >>>>>>>> :
> >>>>>>>>> change from notrun to 0 failed: /usr/bin/wget
> >>>>>>>>> 
> >>>>>> 
> >> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> >>>>>>>>> returned 8 instead of one of [0] [0m
> >>>>>>>>> [0m [mNotice:
> >>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>> 
> >>>> 
> >> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> >>>>>>>> :
> >>>>>>>>> executed successfully [0m
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> But the build continue to do downstream image push and pull
> >>>> because
> >>>>>>>>> puppet apply returns 0 even with errors.
> >>>>>>>>> 
> >>>>>>>>> Let me rerun this first and then try to add some thing
> >> prevent
> >>>> things
> >>>>>>>>> happened again.
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <cos@apache.org
> >>> :
> >>>>>>>>> 
> >>>>>>>>>> Looks like our docker images don't have ant anymore... I
> >> see
> >>>> (at
> >>>>>> least)
> >>>>>>>>>> datafu
> >>>>>>>>>> and solr builds failing on all platforms because of that...
> >>>>>>>>>> 
> >>>>>>>>>> By looking into git history I don't see any evidences of
> >> it,
> >>>> but
> >>>>>> the
> >>>>>>>> builds
> >>>>>>>>>> are failing nonetheless... Thoughts?
> >>>>>>>>>> 
> >>>>>>>>>> Cos
> >>>>>>>>>> 
> >>>>>>>> 
> >>>>>> 
> >>>> 
> >> 
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Olaf Flebbe <of...@oflebbe.de>.
Hi,

Yep I broke it. ;-/   But opensuse broke itself, too. As far as I can tell this change came from a suse update to the OS container.

Of course openssl and libressl cannot coexist, since libressl replaces openssl. The docker images are weird.  I will look into it this evening if I can work out  a quick fix.

If a quick fix is not found,  I propose to drop support for opensuse 13.2, now.

Propose to make a vote to support opensuse leap 42.1 instead or drop it completly. Perhaps this will not make it into the release in time, since there are a lot of issues for SuSE pending.

In the wild I have seen more requests for SLES support then for openSuSE. but we cannot support SLES since we are not allowed to push docker of it images to the public. Peter: Are there solutions to this problem ? We are right now not in the technical position to use the SuSE Build service.

--Olaf



> Am 18.11.2015 um 10:09 schrieb Evans Ye <ev...@apache.org>:
> 
> It looks like the two packages truly(libressl-devel and libopenssl-devel)
> can't co-exist on opensuse:
> 
> ---------------------------------------------------------------------------------------------------------
> $ docker pull opensuse:13.2
> 13.2: Pulling from opensuse
> 717905e6e6af: Pull complete
> 5b8dd08af89b: Already exists
> Digest:
> sha256:325785de46c5c706fc529f28d4f6f70db1b7d57f82a9d328ab945425959741e7
> Status: Downloaded newer image for opensuse:13.2
> $ docker run -ti --rm opensuse:13.2 bash
> bash-4.2# zypper install libressl-devel libopenssl-devel
> Retrieving repository 'NON-OSS' metadata
> ..............................................................................................................[done]
> Building repository 'NON-OSS' cache
> ...................................................................................................................[done]
> Retrieving repository 'OSS' metadata
> ..................................................................................................................[done]
> Building repository 'OSS' cache
> .......................................................................................................................[done]
> Retrieving repository 'OSS Update' metadata
> ...........................................................................................................[done]
> Building repository 'OSS Update' cache
> ................................................................................................................[done]
> Retrieving repository 'Update Non-Oss' metadata
> .......................................................................................................[done]
> Building repository 'Update Non-Oss' cache
> ............................................................................................................[done]
> Loading repository data...
> Reading installed packages...
> Resolving package dependencies...
> 
> Problem: libressl-devel-2.2.1-2.6.1.x86_64 conflicts with libopenssl-devel
> provided by libopenssl-devel-1.0.1k-2.24.1.x86_64
> Solution 1: do not install libressl-devel-2.2.1-2.6.1.x86_64
> Solution 2: do not install libopenssl-devel-1.0.1k-2.24.1.x86_64
> 
> Choose from above solutions by number or cancel [1/2/c] (c):
> ---------------------------------------------------------------------------------------------------------
> 
> For the record libressl-devel is depended by libmysqlclient-devel
> I have no idea how to proceed now, shall we upstream the problem?
> 
> 2015-11-18 15:11 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
>> On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
>>> Well, I need to turn myself in.
>> 
>> Doesn't matter man - it was a joke ;)
>> 
>>> In fact that patch has been tested and +1ed by me,
>>> but I remember my manual build was OK by then...
>> 
>> With the complexities like that - this stuff happens, unfortunately. We
>> already weeded out a bunch of issues by switching to standardized
>> toolchains
>> and build environments. I am pretty sure we'll figure out this one as well.
>> 
>>> Anyhow, I can't understand why it has conflict when we only install
>>> packages available from official repo...
>> 
>> Yeah, that's weird ;( unless the official packages have some issues, which
>> isn't likely I suppose.
>> 
>> Cos
>> 
>> 
>>> 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>> 
>>>> Well, perhaps now Olaf won't brag as much ;)
>>>> 
>>>> (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
>>>> 
>>>> Cos
>>>> 
>>>> On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
>>>>> Okay, it seems these extra packages introduced in BIGTOP-2120 brings
>> up
>>>> the
>>>>> issue:
>>>>> 
>>>>> "python-devel", "python-setuptools", "libxml2-devel",
>> "libxslt-devel", "
>>>>> cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel",
>> "libyaml-devel", "
>>>>> krb5-devel", "asciidoc", "libmysqlclient-devel"
>>>>> 
>>>>> 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>>>> 
>>>>>> I haven't seen Peter for awhile, he might know the answer or have a
>>>> fix for
>>>>>> it.
>>>>>> 
>>>>>> Cos
>>>>>> 
>>>>>> On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
>>>>>>> You got it. The opensuse image is failing for a long while
>>>>>>> (All the trunk images will be rebuilt after code change
>> regardless
>>>>>> whether
>>>>>>> it's failing or not
>>>>>>> 
>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
>>>>>>> 
>>>>>>> The maven things is just some network issue which can be solved
>> by
>>>> rerun.
>>>>>>> However, the package confliction is a bit more difficult to
>> handle.
>>>>>>> 
>>>>>>> The build was still ok back in Nov. 8
>>>>>>> 
>>>>>> 
>>>> 
>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
>>>>>>> 
>>>>>>> The only two changes during these days are:
>>>>>>> 1. add gmp-devel
>>>>>>> 2. remove krb5-mini
>>>>>>> 
>>>>>> 
>>>> 
>> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
>>>>>>> 
>>>>>>> Which seems not related to me.
>>>>>>> I don't have awswer yet and still looking into it...
>>>>>>> 
>>>>>>> 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
>>>>>>> 
>>>>>>>> Looking into the recent builds on Suse I see that pretty much
>> all
>>>> of
>>>>>> them
>>>>>>>> are
>>>>>>>> failing for two reasons:
>>>>>>>> - mvn isn't found
>>>>>>>> - some lib requirements aren't met
>>>>>>>> 
>>>>>>>> While the former seems like a small omission in the container,
>> the
>>>>>> other
>>>>>>>> one
>>>>>>>> looks like a bigger issue with the toolchain. I personally
>> don't
>>>> have
>>>>>> any
>>>>>>>> cycles to work on this.
>>>>>>>> 
>>>>>>>> Thoughts?
>>>>>>>>  Cos
>>>>>>>> 
>>>>>>>> On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
>>>>>>>>> Yeah, that was caused by that images has been changed.
>>>>>>>>> For some unknown reason the ant installation failed:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
>>>>>>>>> 
>>>>>>>>> 14:40:11 ERROR 404: Not Found. [0m
>>>>>>>>> [91m [1;31mError: /usr/bin/wget
>>>>>>>>> 
>>>>>> 
>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
>>>>>>>>> returned 8 instead of one of [0] [0m
>>>>>>>>> [0m [91m [1;31mError:
>>>>>>>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
>>>>>>>> :
>>>>>>>>> change from notrun to 0 failed: /usr/bin/wget
>>>>>>>>> 
>>>>>> 
>> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
>>>>>>>>> returned 8 instead of one of [0] [0m
>>>>>>>>> [0m [mNotice:
>>>> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
>>>>>>>> :
>>>>>>>>> executed successfully [0m
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> But the build continue to do downstream image push and pull
>>>> because
>>>>>>>>> puppet apply returns 0 even with errors.
>>>>>>>>> 
>>>>>>>>> Let me rerun this first and then try to add some thing
>> prevent
>>>> things
>>>>>>>>> happened again.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <cos@apache.org
>>> :
>>>>>>>>> 
>>>>>>>>>> Looks like our docker images don't have ant anymore... I
>> see
>>>> (at
>>>>>> least)
>>>>>>>>>> datafu
>>>>>>>>>> and solr builds failing on all platforms because of that...
>>>>>>>>>> 
>>>>>>>>>> By looking into git history I don't see any evidences of
>> it,
>>>> but
>>>>>> the
>>>>>>>> builds
>>>>>>>>>> are failing nonetheless... Thoughts?
>>>>>>>>>> 
>>>>>>>>>> Cos
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Evans Ye <ev...@apache.org>.
It looks like the two packages truly(libressl-devel and libopenssl-devel)
can't co-exist on opensuse:

---------------------------------------------------------------------------------------------------------
$ docker pull opensuse:13.2
13.2: Pulling from opensuse
717905e6e6af: Pull complete
5b8dd08af89b: Already exists
Digest:
sha256:325785de46c5c706fc529f28d4f6f70db1b7d57f82a9d328ab945425959741e7
Status: Downloaded newer image for opensuse:13.2
$ docker run -ti --rm opensuse:13.2 bash
bash-4.2# zypper install libressl-devel libopenssl-devel
Retrieving repository 'NON-OSS' metadata
..............................................................................................................[done]
Building repository 'NON-OSS' cache
...................................................................................................................[done]
Retrieving repository 'OSS' metadata
..................................................................................................................[done]
Building repository 'OSS' cache
.......................................................................................................................[done]
Retrieving repository 'OSS Update' metadata
...........................................................................................................[done]
Building repository 'OSS Update' cache
................................................................................................................[done]
Retrieving repository 'Update Non-Oss' metadata
.......................................................................................................[done]
Building repository 'Update Non-Oss' cache
............................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: libressl-devel-2.2.1-2.6.1.x86_64 conflicts with libopenssl-devel
provided by libopenssl-devel-1.0.1k-2.24.1.x86_64
 Solution 1: do not install libressl-devel-2.2.1-2.6.1.x86_64
 Solution 2: do not install libopenssl-devel-1.0.1k-2.24.1.x86_64

Choose from above solutions by number or cancel [1/2/c] (c):
---------------------------------------------------------------------------------------------------------

For the record libressl-devel is depended by libmysqlclient-devel
I have no idea how to proceed now, shall we upstream the problem?

2015-11-18 15:11 GMT+08:00 Konstantin Boudnik <co...@apache.org>:

> On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
> > Well, I need to turn myself in.
>
> Doesn't matter man - it was a joke ;)
>
> > In fact that patch has been tested and +1ed by me,
> > but I remember my manual build was OK by then...
>
> With the complexities like that - this stuff happens, unfortunately. We
> already weeded out a bunch of issues by switching to standardized
> toolchains
> and build environments. I am pretty sure we'll figure out this one as well.
>
> > Anyhow, I can't understand why it has conflict when we only install
> > packages available from official repo...
>
> Yeah, that's weird ;( unless the official packages have some issues, which
> isn't likely I suppose.
>
> Cos
>
>
> > 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >
> > > Well, perhaps now Olaf won't brag as much ;)
> > >
> > > (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
> > >
> > > Cos
> > >
> > > On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> > > > Okay, it seems these extra packages introduced in BIGTOP-2120 brings
> up
> > > the
> > > > issue:
> > > >
> > > > "python-devel", "python-setuptools", "libxml2-devel",
> "libxslt-devel", "
> > > > cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel",
> "libyaml-devel", "
> > > > krb5-devel", "asciidoc", "libmysqlclient-devel"
> > > >
> > > > 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > >
> > > > > I haven't seen Peter for awhile, he might know the answer or have a
> > > fix for
> > > > > it.
> > > > >
> > > > > Cos
> > > > >
> > > > > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > > > > > You got it. The opensuse image is failing for a long while
> > > > > > (All the trunk images will be rebuilt after code change
> regardless
> > > > > whether
> > > > > > it's failing or not
> > > > > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > > > > >
> > > > > > The maven things is just some network issue which can be solved
> by
> > > rerun.
> > > > > > However, the package confliction is a bit more difficult to
> handle.
> > > > > >
> > > > > > The build was still ok back in Nov. 8
> > > > > >
> > > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> > > > > >
> > > > > > The only two changes during these days are:
> > > > > > 1. add gmp-devel
> > > > > > 2. remove krb5-mini
> > > > > >
> > > > >
> > >
> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> > > > > >
> > > > > > Which seems not related to me.
> > > > > > I don't have awswer yet and still looking into it...
> > > > > >
> > > > > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > > >
> > > > > > > Looking into the recent builds on Suse I see that pretty much
> all
> > > of
> > > > > them
> > > > > > > are
> > > > > > > failing for two reasons:
> > > > > > >  - mvn isn't found
> > > > > > >  - some lib requirements aren't met
> > > > > > >
> > > > > > > While the former seems like a small omission in the container,
> the
> > > > > other
> > > > > > > one
> > > > > > > looks like a bigger issue with the toolchain. I personally
> don't
> > > have
> > > > > any
> > > > > > > cycles to work on this.
> > > > > > >
> > > > > > > Thoughts?
> > > > > > >   Cos
> > > > > > >
> > > > > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > > > > > Yeah, that was caused by that images has been changed.
> > > > > > > > For some unknown reason the ant installation failed:
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > > > > > >
> > > > > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > > > > >  [91m [1;31mError: /usr/bin/wget
> > > > > > > >
> > > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > > returned 8 instead of one of [0] [0m
> > > > > > > >  [0m [91m [1;31mError:
> > > > > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > > > > > :
> > > > > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > > > > >
> > > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > > returned 8 instead of one of [0] [0m
> > > > > > > >  [0m [mNotice:
> > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > > >
> > > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > > > > > :
> > > > > > > > executed successfully [0m
> > > > > > > >
> > > > > > > >
> > > > > > > > But the build continue to do downstream image push and pull
> > > because
> > > > > > > > puppet apply returns 0 even with errors.
> > > > > > > >
> > > > > > > > Let me rerun this first and then try to add some thing
> prevent
> > > things
> > > > > > > > happened again.
> > > > > > > >
> > > > > > > >
> > > > > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <cos@apache.org
> >:
> > > > > > > >
> > > > > > > > > Looks like our docker images don't have ant anymore... I
> see
> > > (at
> > > > > least)
> > > > > > > > > datafu
> > > > > > > > > and solr builds failing on all platforms because of that...
> > > > > > > > >
> > > > > > > > > By looking into git history I don't see any evidences of
> it,
> > > but
> > > > > the
> > > > > > > builds
> > > > > > > > > are failing nonetheless... Thoughts?
> > > > > > > > >
> > > > > > > > > Cos
> > > > > > > > >
> > > > > > >
> > > > >
> > >
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Konstantin Boudnik <co...@apache.org>.
On Wed, Nov 18, 2015 at 02:54PM, Evans Ye wrote:
> Well, I need to turn myself in.

Doesn't matter man - it was a joke ;)

> In fact that patch has been tested and +1ed by me,
> but I remember my manual build was OK by then...

With the complexities like that - this stuff happens, unfortunately. We
already weeded out a bunch of issues by switching to standardized toolchains
and build environments. I am pretty sure we'll figure out this one as well.

> Anyhow, I can't understand why it has conflict when we only install
> packages available from official repo...

Yeah, that's weird ;( unless the official packages have some issues, which
isn't likely I suppose.

Cos


> 2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
> > Well, perhaps now Olaf won't brag as much ;)
> >
> > (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
> >
> > Cos
> >
> > On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> > > Okay, it seems these extra packages introduced in BIGTOP-2120 brings up
> > the
> > > issue:
> > >
> > > "python-devel", "python-setuptools", "libxml2-devel", "libxslt-devel", "
> > > cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel", "libyaml-devel", "
> > > krb5-devel", "asciidoc", "libmysqlclient-devel"
> > >
> > > 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > >
> > > > I haven't seen Peter for awhile, he might know the answer or have a
> > fix for
> > > > it.
> > > >
> > > > Cos
> > > >
> > > > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > > > > You got it. The opensuse image is failing for a long while
> > > > > (All the trunk images will be rebuilt after code change regardless
> > > > whether
> > > > > it's failing or not
> > > > > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > > > >
> > > > > The maven things is just some network issue which can be solved by
> > rerun.
> > > > > However, the package confliction is a bit more difficult to handle.
> > > > >
> > > > > The build was still ok back in Nov. 8
> > > > >
> > > >
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> > > > >
> > > > > The only two changes during these days are:
> > > > > 1. add gmp-devel
> > > > > 2. remove krb5-mini
> > > > >
> > > >
> > https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> > > > >
> > > > > Which seems not related to me.
> > > > > I don't have awswer yet and still looking into it...
> > > > >
> > > > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > >
> > > > > > Looking into the recent builds on Suse I see that pretty much all
> > of
> > > > them
> > > > > > are
> > > > > > failing for two reasons:
> > > > > >  - mvn isn't found
> > > > > >  - some lib requirements aren't met
> > > > > >
> > > > > > While the former seems like a small omission in the container, the
> > > > other
> > > > > > one
> > > > > > looks like a bigger issue with the toolchain. I personally don't
> > have
> > > > any
> > > > > > cycles to work on this.
> > > > > >
> > > > > > Thoughts?
> > > > > >   Cos
> > > > > >
> > > > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > > > > Yeah, that was caused by that images has been changed.
> > > > > > > For some unknown reason the ant installation failed:
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > > > > >
> > > > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > > > >  [91m [1;31mError: /usr/bin/wget
> > > > > > >
> > > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > returned 8 instead of one of [0] [0m
> > > > > > >  [0m [91m [1;31mError:
> > > > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > >
> > > > > >
> > > >
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > > > > :
> > > > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > > > >
> > > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > > returned 8 instead of one of [0] [0m
> > > > > > >  [0m [mNotice:
> > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > > >
> > > > > >
> > > >
> > http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > > > > :
> > > > > > > executed successfully [0m
> > > > > > >
> > > > > > >
> > > > > > > But the build continue to do downstream image push and pull
> > because
> > > > > > > puppet apply returns 0 even with errors.
> > > > > > >
> > > > > > > Let me rerun this first and then try to add some thing prevent
> > things
> > > > > > > happened again.
> > > > > > >
> > > > > > >
> > > > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > > > >
> > > > > > > > Looks like our docker images don't have ant anymore... I see
> > (at
> > > > least)
> > > > > > > > datafu
> > > > > > > > and solr builds failing on all platforms because of that...
> > > > > > > >
> > > > > > > > By looking into git history I don't see any evidences of it,
> > but
> > > > the
> > > > > > builds
> > > > > > > > are failing nonetheless... Thoughts?
> > > > > > > >
> > > > > > > > Cos
> > > > > > > >
> > > > > >
> > > >
> >

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Evans Ye <ev...@apache.org>.
Well, I need to turn myself in.
In fact that patch has been tested and +1ed by me,
but I remember my manual build was OK by then...

Anyhow, I can't understand why it has conflict when we only install
packages available from official repo...

2015-11-18 12:09 GMT+08:00 Konstantin Boudnik <co...@apache.org>:

> Well, perhaps now Olaf won't brag as much ;)
>
> (Sorry, Olaf, couldn't resist - the timing was almost perfect ;)
>
> Cos
>
> On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> > Okay, it seems these extra packages introduced in BIGTOP-2120 brings up
> the
> > issue:
> >
> > "python-devel", "python-setuptools", "libxml2-devel", "libxslt-devel", "
> > cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel", "libyaml-devel", "
> > krb5-devel", "asciidoc", "libmysqlclient-devel"
> >
> > 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >
> > > I haven't seen Peter for awhile, he might know the answer or have a
> fix for
> > > it.
> > >
> > > Cos
> > >
> > > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > > > You got it. The opensuse image is failing for a long while
> > > > (All the trunk images will be rebuilt after code change regardless
> > > whether
> > > > it's failing or not
> > > > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > > >
> > > > The maven things is just some network issue which can be solved by
> rerun.
> > > > However, the package confliction is a bit more difficult to handle.
> > > >
> > > > The build was still ok back in Nov. 8
> > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> > > >
> > > > The only two changes during these days are:
> > > > 1. add gmp-devel
> > > > 2. remove krb5-mini
> > > >
> > >
> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> > > >
> > > > Which seems not related to me.
> > > > I don't have awswer yet and still looking into it...
> > > >
> > > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > >
> > > > > Looking into the recent builds on Suse I see that pretty much all
> of
> > > them
> > > > > are
> > > > > failing for two reasons:
> > > > >  - mvn isn't found
> > > > >  - some lib requirements aren't met
> > > > >
> > > > > While the former seems like a small omission in the container, the
> > > other
> > > > > one
> > > > > looks like a bigger issue with the toolchain. I personally don't
> have
> > > any
> > > > > cycles to work on this.
> > > > >
> > > > > Thoughts?
> > > > >   Cos
> > > > >
> > > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > > > Yeah, that was caused by that images has been changed.
> > > > > > For some unknown reason the ant installation failed:
> > > > > >
> > > > > >
> > > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > > > >
> > > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > > >  [91m [1;31mError: /usr/bin/wget
> > > > > >
> > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > returned 8 instead of one of [0] [0m
> > > > > >  [0m [91m [1;31mError:
> > > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > > > :
> > > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > > >
> > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > > returned 8 instead of one of [0] [0m
> > > > > >  [0m [mNotice:
> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > > >
> > > > >
> > >
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > > > :
> > > > > > executed successfully [0m
> > > > > >
> > > > > >
> > > > > > But the build continue to do downstream image push and pull
> because
> > > > > > puppet apply returns 0 even with errors.
> > > > > >
> > > > > > Let me rerun this first and then try to add some thing prevent
> things
> > > > > > happened again.
> > > > > >
> > > > > >
> > > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > > >
> > > > > > > Looks like our docker images don't have ant anymore... I see
> (at
> > > least)
> > > > > > > datafu
> > > > > > > and solr builds failing on all platforms because of that...
> > > > > > >
> > > > > > > By looking into git history I don't see any evidences of it,
> but
> > > the
> > > > > builds
> > > > > > > are failing nonetheless... Thoughts?
> > > > > > >
> > > > > > > Cos
> > > > > > >
> > > > >
> > >
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Konstantin Boudnik <co...@apache.org>.
Well, perhaps now Olaf won't brag as much ;) 

(Sorry, Olaf, couldn't resist - the timing was almost perfect ;)

Cos

On Wed, Nov 18, 2015 at 11:56AM, Evans Ye wrote:
> Okay, it seems these extra packages introduced in BIGTOP-2120 brings up the
> issue:
> 
> "python-devel", "python-setuptools", "libxml2-devel", "libxslt-devel", "
> cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel", "libyaml-devel", "
> krb5-devel", "asciidoc", "libmysqlclient-devel"
> 
> 2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
> > I haven't seen Peter for awhile, he might know the answer or have a fix for
> > it.
> >
> > Cos
> >
> > On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > > You got it. The opensuse image is failing for a long while
> > > (All the trunk images will be rebuilt after code change regardless
> > whether
> > > it's failing or not
> > > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> > >
> > > The maven things is just some network issue which can be solved by rerun.
> > > However, the package confliction is a bit more difficult to handle.
> > >
> > > The build was still ok back in Nov. 8
> > >
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> > >
> > > The only two changes during these days are:
> > > 1. add gmp-devel
> > > 2. remove krb5-mini
> > >
> > https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> > >
> > > Which seems not related to me.
> > > I don't have awswer yet and still looking into it...
> > >
> > > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > >
> > > > Looking into the recent builds on Suse I see that pretty much all of
> > them
> > > > are
> > > > failing for two reasons:
> > > >  - mvn isn't found
> > > >  - some lib requirements aren't met
> > > >
> > > > While the former seems like a small omission in the container, the
> > other
> > > > one
> > > > looks like a bigger issue with the toolchain. I personally don't have
> > any
> > > > cycles to work on this.
> > > >
> > > > Thoughts?
> > > >   Cos
> > > >
> > > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > > Yeah, that was caused by that images has been changed.
> > > > > For some unknown reason the ant installation failed:
> > > > >
> > > > >
> > > >
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > > >
> > > > > 14:40:11 ERROR 404: Not Found. [0m
> > > > >  [91m [1;31mError: /usr/bin/wget
> > > > >
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > returned 8 instead of one of [0] [0m
> > > > >  [0m [91m [1;31mError:
> > > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > >
> > > >
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > > :
> > > > > change from notrun to 0 failed: /usr/bin/wget
> > > > >
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > > returned 8 instead of one of [0] [0m
> > > > >  [0m [mNotice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > > >
> > > >
> > http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > > :
> > > > > executed successfully [0m
> > > > >
> > > > >
> > > > > But the build continue to do downstream image push and pull because
> > > > > puppet apply returns 0 even with errors.
> > > > >
> > > > > Let me rerun this first and then try to add some thing prevent things
> > > > > happened again.
> > > > >
> > > > >
> > > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > > >
> > > > > > Looks like our docker images don't have ant anymore... I see (at
> > least)
> > > > > > datafu
> > > > > > and solr builds failing on all platforms because of that...
> > > > > >
> > > > > > By looking into git history I don't see any evidences of it, but
> > the
> > > > builds
> > > > > > are failing nonetheless... Thoughts?
> > > > > >
> > > > > > Cos
> > > > > >
> > > >
> >

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Evans Ye <ev...@apache.org>.
Okay, it seems these extra packages introduced in BIGTOP-2120 brings up the
issue:

"python-devel", "python-setuptools", "libxml2-devel", "libxslt-devel", "
cyrus-sasl-devel", "sqlite3-devel", "openldap2-devel", "libyaml-devel", "
krb5-devel", "asciidoc", "libmysqlclient-devel"

2015-11-18 11:19 GMT+08:00 Konstantin Boudnik <co...@apache.org>:

> I haven't seen Peter for awhile, he might know the answer or have a fix for
> it.
>
> Cos
>
> On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> > You got it. The opensuse image is failing for a long while
> > (All the trunk images will be rebuilt after code change regardless
> whether
> > it's failing or not
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> >
> > The maven things is just some network issue which can be solved by rerun.
> > However, the package confliction is a bit more difficult to handle.
> >
> > The build was still ok back in Nov. 8
> >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> >
> > The only two changes during these days are:
> > 1. add gmp-devel
> > 2. remove krb5-mini
> >
> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> >
> > Which seems not related to me.
> > I don't have awswer yet and still looking into it...
> >
> > 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >
> > > Looking into the recent builds on Suse I see that pretty much all of
> them
> > > are
> > > failing for two reasons:
> > >  - mvn isn't found
> > >  - some lib requirements aren't met
> > >
> > > While the former seems like a small omission in the container, the
> other
> > > one
> > > looks like a bigger issue with the toolchain. I personally don't have
> any
> > > cycles to work on this.
> > >
> > > Thoughts?
> > >   Cos
> > >
> > > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > > Yeah, that was caused by that images has been changed.
> > > > For some unknown reason the ant installation failed:
> > > >
> > > >
> > >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > > >
> > > > 14:40:11 ERROR 404: Not Found. [0m
> > > >  [91m [1;31mError: /usr/bin/wget
> > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > returned 8 instead of one of [0] [0m
> > > >  [0m [91m [1;31mError:
> > > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > >
> > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > > :
> > > > change from notrun to 0 failed: /usr/bin/wget
> > > >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > > returned 8 instead of one of [0] [0m
> > > >  [0m [mNotice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > > >
> > >
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > > :
> > > > executed successfully [0m
> > > >
> > > >
> > > > But the build continue to do downstream image push and pull because
> > > > puppet apply returns 0 even with errors.
> > > >
> > > > Let me rerun this first and then try to add some thing prevent things
> > > > happened again.
> > > >
> > > >
> > > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > > >
> > > > > Looks like our docker images don't have ant anymore... I see (at
> least)
> > > > > datafu
> > > > > and solr builds failing on all platforms because of that...
> > > > >
> > > > > By looking into git history I don't see any evidences of it, but
> the
> > > builds
> > > > > are failing nonetheless... Thoughts?
> > > > >
> > > > > Cos
> > > > >
> > >
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Konstantin Boudnik <co...@apache.org>.
I haven't seen Peter for awhile, he might know the answer or have a fix for
it.

Cos

On Wed, Nov 18, 2015 at 11:13AM, Evans Ye wrote:
> You got it. The opensuse image is failing for a long while
> (All the trunk images will be rebuilt after code change regardless whether
> it's failing or not
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)
> 
> The maven things is just some network issue which can be solved by rerun.
> However, the package confliction is a bit more difficult to handle.
> 
> The build was still ok back in Nov. 8
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/
> 
> The only two changes during these days are:
> 1. add gmp-devel
> 2. remove krb5-mini
> https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp
> 
> Which seems not related to me.
> I don't have awswer yet and still looking into it...
> 
> 2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
> > Looking into the recent builds on Suse I see that pretty much all of them
> > are
> > failing for two reasons:
> >  - mvn isn't found
> >  - some lib requirements aren't met
> >
> > While the former seems like a small omission in the container, the other
> > one
> > looks like a bigger issue with the toolchain. I personally don't have any
> > cycles to work on this.
> >
> > Thoughts?
> >   Cos
> >
> > On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > > Yeah, that was caused by that images has been changed.
> > > For some unknown reason the ant installation failed:
> > >
> > >
> > http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> > >
> > > 14:40:11 ERROR 404: Not Found. [0m
> > >  [91m [1;31mError: /usr/bin/wget
> > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > returned 8 instead of one of [0] [0m
> > >  [0m [91m [1;31mError:
> > > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > >
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> > :
> > > change from notrun to 0 failed: /usr/bin/wget
> > > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > > returned 8 instead of one of [0] [0m
> > >  [0m [mNotice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> > >
> > http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> > :
> > > executed successfully [0m
> > >
> > >
> > > But the build continue to do downstream image push and pull because
> > > puppet apply returns 0 even with errors.
> > >
> > > Let me rerun this first and then try to add some thing prevent things
> > > happened again.
> > >
> > >
> > > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> > >
> > > > Looks like our docker images don't have ant anymore... I see (at least)
> > > > datafu
> > > > and solr builds failing on all platforms because of that...
> > > >
> > > > By looking into git history I don't see any evidences of it, but the
> > builds
> > > > are failing nonetheless... Thoughts?
> > > >
> > > > Cos
> > > >
> >

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Evans Ye <ev...@apache.org>.
You got it. The opensuse image is failing for a long while
(All the trunk images will be rebuilt after code change regardless whether
it's failing or not
http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/)

The maven things is just some network issue which can be solved by rerun.
However, the package confliction is a bit more difficult to handle.

The build was still ok back in Nov. 8
http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=opensuse-13.2,label=docker-slave-06/5/

The only two changes during these days are:
1. add gmp-devel
2. remove krb5-mini
https://github.com/apache/bigtop/commits/master/bigtop_toolchain/manifests/packages.pp

Which seems not related to me.
I don't have awswer yet and still looking into it...

2015-11-18 7:27 GMT+08:00 Konstantin Boudnik <co...@apache.org>:

> Looking into the recent builds on Suse I see that pretty much all of them
> are
> failing for two reasons:
>  - mvn isn't found
>  - some lib requirements aren't met
>
> While the former seems like a small omission in the container, the other
> one
> looks like a bigger issue with the toolchain. I personally don't have any
> cycles to work on this.
>
> Thoughts?
>   Cos
>
> On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> > Yeah, that was caused by that images has been changed.
> > For some unknown reason the ant installation failed:
> >
> >
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> >
> > 14:40:11 ERROR 404: Not Found. [0m
> >  [91m [1;31mError: /usr/bin/wget
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > returned 8 instead of one of [0] [0m
> >  [0m [91m [1;31mError:
> > /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> >
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns
> :
> > change from notrun to 0 failed: /usr/bin/wget
> > http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> > returned 8 instead of one of [0] [0m
> >  [0m [mNotice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> >
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns
> :
> > executed successfully [0m
> >
> >
> > But the build continue to do downstream image push and pull because
> > puppet apply returns 0 even with errors.
> >
> > Let me rerun this first and then try to add some thing prevent things
> > happened again.
> >
> >
> > 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> >
> > > Looks like our docker images don't have ant anymore... I see (at least)
> > > datafu
> > > and solr builds failing on all platforms because of that...
> > >
> > > By looking into git history I don't see any evidences of it, but the
> builds
> > > are failing nonetheless... Thoughts?
> > >
> > > Cos
> > >
>

Re: OpenSUSE failures [Was: Any recent changes to the docker images?]

Posted by Konstantin Boudnik <co...@apache.org>.
Looking into the recent builds on Suse I see that pretty much all of them are
failing for two reasons:
 - mvn isn't found
 - some lib requirements aren't met

While the former seems like a small omission in the container, the other one
looks like a bigger issue with the toolchain. I personally don't have any
cycles to work on this.

Thoughts?
  Cos

On Sat, Nov 14, 2015 at 11:00AM, Evans Ye wrote:
> Yeah, that was caused by that images has been changed.
> For some unknown reason the ant installation failed:
> 
> http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console
> 
> 14:40:11 ERROR 404: Not Found.
> Error: /usr/bin/wget
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> returned 8 instead of one of [0]
> Error:
> /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns:
> change from notrun to 0 failed: /usr/bin/wget
> http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
> returned 8 instead of one of [0]
> Notice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
> http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns:
> executed successfully
> 
> 
> But the build continue to do downstream image push and pull because
> puppet apply returns 0 even with errors.
> 
> Let me rerun this first and then try to add some thing prevent things
> happened again.
> 
> 
> 2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:
> 
> > Looks like our docker images don't have ant anymore... I see (at least)
> > datafu
> > and solr builds failing on all platforms because of that...
> >
> > By looking into git history I don't see any evidences of it, but the builds
> > are failing nonetheless... Thoughts?
> >
> > Cos
> >

Re: Any recent changes to the docker images?

Posted by Evans Ye <ev...@apache.org>.
Yeah, that was caused by that images has been changed.
For some unknown reason the ant installation failed:

http://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-Trunk/BUILD_ENVIRONMENTS=centos-7,label=docker-slave-06/7/console

14:40:11 ERROR 404: Not Found.
Error: /usr/bin/wget
http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
returned 8 instead of one of [0]
Error:
/Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz]/returns:
change from notrun to 0 failed: /usr/bin/wget
http://ftp.wayne.edu/apache//ant/binaries/apache-ant-1.9.5-bin.tar.gz
returned 8 instead of one of [0]
Notice: /Stage[main]/Bigtop_toolchain::Deps/Exec[/usr/bin/wget
http://ftp.wayne.edu/apache//maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz]/returns:
executed successfully


But the build continue to do downstream image push and pull because
puppet apply returns 0 even with errors.

Let me rerun this first and then try to add some thing prevent things
happened again.


2015-11-14 9:20 GMT+08:00 Konstantin Boudnik <co...@apache.org>:

> Looks like our docker images don't have ant anymore... I see (at least)
> datafu
> and solr builds failing on all platforms because of that...
>
> By looking into git history I don't see any evidences of it, but the builds
> are failing nonetheless... Thoughts?
>
> Cos
>