[Fuego] [PATCH 00/11] Add Fuego Functional.fuegotest

Guilherme Camargo guicc at profusion.mobi
Fri Mar 9 19:29:03 UTC 2018


​Hello, Tim, hope everything is going well.

Can you please give it a couple more tries by checking out the two
new branches that I've just pushed to our fuego repo?

You can just fetch them, checkout and run, because
we haven't force pushed anything since yesterday.

They have one commit each (above fuego-test branch),
with a potential fix to the problem.


The repo/branches are these ones:

* https://bitbucket.org/profusionmobi/fuego/branch/chown-all?dest=fuego-test

  git fetch && git checkout chown-all

  On this patch we're just using `chown -R --from` to chown all jenkins
  files that may still exist outside of the directories that we were
chowning
  so far.

  Please Try This One First. And if it works, great. If not, please
  try the next branch (below).


*
https://bitbucket.org/profusionmobi/fuego/branch/jenkins-user-on-build?dest=fuego-test

  git fetch && git checkout jenkins-user-on-build

  This patch is almost a 'clean revert' of the patch that moved the jenkins
uid
  mapping to the entrypoint. We're just setting the correct jenkins id
during
  docker build, by passing uid/gid through the docker-build-image.sh script
and
  reading them through the Dockerfile.

  This one should probably solve the issue, given that no ownership will
need to
  be changed, since Jenkins starts for the first time with the correct user
already.


Please just make sure to run a `git clean -dxf` in the repo before running,
to remove anything that jenkins might have written to fuego-rw.


I'm also attaching the patches, for you to apply them directly if you
prefer.



Thank you very much



On Thu, Mar 8, 2018 at 9:51 PM, <Tim.Bird at sony.com> wrote:

> I just tried to everything on Ubuntu 16.04, using docker version 1.13.1,
> and I get the same problem.
>
> When I exit the container, and try to restart it, Jenkins fails to start,
> and the
> log says:
> java.io.FileNotFoundException: /var/cache/jenkins/war/META-INF/MANIFEST.MF
>
> The file is there, owned by jenkins.jenkins.
>
> Here is more information:
> jenkins at timdesk:/var/cache/jenkins$ ls -la
> ls: cannot access war: Permission denied
> total 8
> drwxr-x---  4 jenkins jenkins 4096 Mar  9 00:37 .
> drwxr-xr-x 20 root   root    4096 Mar  9 00:37 ..
> d?????????  ? ?        ?           ?                ? war
> jenkins at timdesk:/var/cache/jenkins$l id
> uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins)
> ------
>
> So, we've still got a permission problem in here somewhere.
>  -- Tim
>
> > -----Original Message-----
> > From: Tim.Bird at sony.com
> >
> > Same behavior.
> >  -- Tim
> >
> >
> > > -----Original Message-----
> > > From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-
> > > bounces at lists.linuxfoundation.org] On Behalf Of Guilherme Camargo
> > > Sent: Thursday, March 08, 2018 2:20 PM
> > > To: Bird, Timothy <Tim.Bird at sony.com>
> > > Cc: fuego at lists.linuxfoundation.org
> > > Subject: Re: [Fuego] [PATCH 00/11] Add Fuego Functional.fuegotest
> > >
> > > ​Tim, can you please try to add `--privileged` to the `docker create`​
> call on
> > > fuego-host-scripts/docker-create-container.sh ? This should not be the
> > final
> > > fix, it's just for testing.
> > >
> > > ```
> > >
> > > sudo docker create -it --name ${DOCKERCONTAINER} \
> > >     --privileged \
> > >     -v /var/run/docker.sock:/var/run/docker.sock \
> > >     -v /boot:/boot:ro \
> > >     -v $DIR/../fuego-rw:/fuego-rw \
> > >     -v $DIR/../fuego-ro:/fuego-ro:ro \
> > >     -v $DIR/../../fuego-core:/fuego-core:ro \
> > >     -e http_proxy=${http_proxy} \
> > >     -e https_proxy=${https_proxy:-$http_proxy} \
> > >     --net="host" ${DOCKERIMAGE} || \
> > >     echo "Could not create fuego-container. See error messages."
> > >
> > > ```
> > >
> > >
> > > Thanks
> > >
> > >
> > > On Thu, Mar 8, 2018 at 6:32 PM, <Tim.Bird at sony.com
> > > <mailto:Tim.Bird at sony.com> > wrote:
> > >
> > >
> > >
> > >
> > >     > -----Original Message-----
> > >     > From: fuego-bounces at lists.linuxfoundation.org <mailto:fuego-
> > > bounces at lists.linuxfoundation.org>  [mailto:fuego- <mailto:fuego->
> > >     > bounces at lists.linuxfoundation.org
> > > <mailto:bounces at lists.linuxfoundation.org> ] On Behalf Of Guilherme
> > > Campos
> > >     > Camargo
> > >     > Sent: Wednesday, March 07, 2018 11:55 AM
> > >     > To: fuego at lists.linuxfoundation.org
> > > <mailto:fuego at lists.linuxfoundation.org>
> > >     > Subject: [Fuego] [PATCH 00/11] Add Fuego Functional.fuegotest
> > >     >
> > >     > Hello, Tim
> > >     >
> > >     > Please see a few more commits that have been added to
> > >     > Functional.fuegotest.
> > >     > They include bug-fixes and some new tests (Shell and Selenium).
> > >     >
> > >     > Not sure if you had the chance to take a look at my previous
> > > patches yet, but
> > >     > if not, please consider using these one instead.
> > >     >
> > >     > There are many commits, but most of them are pretty small. Please
> > > feel
> > >     > free to ask me to squash some of them if you prefer.
> > >     >
> > >     > To run these, you will need to checkout the `fuego-test` branch
> > > from
> > >     > Profusion's fuego and fuego-core forks and then simply use fuego
> > > as usual to
> > >     > add the fuego-test board and the Functional.fuegotest test.
> > >     >
> > >     > In summary:
> > >     >
> > >     > On host:
> > >     > git clone --branch fuego-test
> > > https://bitbucket.org/profusionmobi/fuego-
> > > <https://bitbucket.org/profusionmobi/fuego->
> > >     > core.git
> > >     > git clone --branch fuego-test
> > > https://bitbucket.org/profusionmobi/fuego.git
> > > <https://bitbucket.org/profusionmobi/fuego.git>
> > >     > cd fuego
> > >     > ./install.sh
> > >     > ./fuego-host-scripts/docker-remove-container.sh
> > >     > ./fuego-host-scripts/docker-create-container.sh
> > >     > ./fuego-host-scripts/docker-start-container.sh
> > >     >
> > >
> > >
> > >     The build worked.
> > >
> > >     > In fuego:
> > >     > ftc add-nodes fuego-test
> > >     > ftc add-jobs -b fuego-test -t Functional.fuegotest
> > >
> > >     these worked.
> > >
> > >     > Then you will be able to start the test through Jenkins and see
> the
> > > results.
> > >     Running the test in jenkins resulted in the log that's attached.
> > >
> > >      -- Tim
> > >
> > >
> >
> > _______________________________________________
> > Fuego mailing list
> > Fuego at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/fuego
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20180309/4f7c6e23/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: chown_jenkins.patch
Type: text/x-patch
Size: 1683 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20180309/4f7c6e23/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jenkins_user_on_build.patch
Type: text/x-patch
Size: 1440 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20180309/4f7c6e23/attachment-0003.bin>


More information about the Fuego mailing list