I'm with Cos, something changed in opensuse to omit the profile sourcing.

We used to run bash -l -c ... to let login shell do the trick to source
/etc/profile.d/bigtop.sh.

I've added back the manual sourcing to our packaging CI.

We need to push 1.1 forward anyway.

2016-01-05 16:32 GMT+08:00 Olaf Flebbe <[email protected]>:

> Hi
>
> the image is screwed up...  java is missing for some reason.
>
> Olaf
>
> > Am 05.01.2016 um 07:59 schrieb Konstantin Boudnik <[email protected]>:
> >
> > On Mon, Jan 04, 2016 at 09:28PM, Peter Linnell wrote:
> >> On Mon, 4 Jan 2016 14:31:24 -0800
> >> Konstantin Boudnik <[email protected]> wrote:
> >>
> >>> Guys,
> >>>
> >>> something quite weird is happening. I have rebuilt and pushed the
> >>> slaves images on 12/29 to reflect the fix for BIGTOP-2171. From that
> >>> moment on all opensuse builds are failing seemingly because JAVA_HOME
> >>> couldn't be determined ie http://is.gd/5YPZoP
> >>>
> >>> Manually examining the latest available image for that slave
> >>> (a44e80ff8c88) I see this
> >>> bash-4.2# su - jenkins
> >>> -bash: /etc/profile: No such file or directory
> >>>
> >>> and manually running
> >>> -bash-4.2$ . /etc/profile.d/bigtop.sh
> >>> -bash-4.2$ echo $JAVA_HOME
> >>> /usr/lib64/jvm/java-1.7.0-openjdk-1.7.0
> >>>
> >>> solves the problem with JAVA_HOME. Considering that we haven't changed
> >>> anything on our side that might have caused this behavior, I wonder
> >>> if there's something happening on the opensuse core image side,
> >>> perhaps? Any ideas?
> >>>
> >>> Thanks,
> >>>  Cos
> >>
> >> Hi all,
> >>
> >> Really odd.  Even root should get a root profile on openSUSE. It has
> >> been that way since SLES 9.
> >>
> >> How can I access this machine to have a peek ?
> >
> > Peter, just do
> >    docker run bigtop/slaves:trunk-opensuse-13.2 -i -t /bin/bash
> >
> > and you'll get the image we're discussing here. It is quite possible that
> > image creation got screwed for some weird reason, although I couldn't
> find any
> > traces of it in the build's logs. Thanks!
> >
> > Cos
> >
>
>

Reply via email to