[Fuego] Fuego v1.1 setup queries

Tue Apr 11 03:30:16 UTC 2017

> -----Original Message-----
> From: dhinakar k on Monday, April 10, 2017 8:13 PM
> Hi Tim,
> 
> At home, on my laptop I have only one Jenkins running on port 8080. Initially
> during Fuego installation I reported Jenkins error. It was because I had
> uninstalled Jenkins from my PC and hence Jenkins service wasn't running. I
> thought Jenkins will be installed and service will be started by Fuego during
> the installation. To fix that I installed Jenkins (default lates v2.54) and did a
> 'sudo service jenkins restart' after which Fuego installation was successful. I
> think some where in your setup you had mentioned Jenkins 2.32.1 version.
> Could that be the problem?

I'm confused by your setup.  Fuego should not use Jenkins running on the
host machine (in this case, your laptop), but only the one in the container.

When you create the container, it installs Jenkins, and runs it inside the
container.  If there is one already running on the host, on the same port,
they will conflict.  The version that is installed by our container creation
script is 2.32.1.  If you are seeing Jenkins version 2.54, then something is
different about your environment.  See the Dockerfile, lines 44-53 for
the Jenkins installation that should occur inside the container.  It is
very explicitly trying to download and install Jenkins version 2.32.1.

Did you, by chance, do an upgrade of Jenkins using the web interface?

Are you running ftc inside the docker container?  This is required for it
to work.

I'm thinking there's something odd going on.  One way to make sure that
the interface you are seeing in your web browser is the one inside the
container, would be to do the following (at the container prompt):
1. # service jenkins stop
2. (try to access the Jenkins web interface with your browser)
3.  # service jenkins start
4. (try to access the Jenkins web interface with your browser)

If you can still access the web interface in step 2, then it's not the Jenkins
inside the container that you're seeing in your interface.

> Also, what is the workaround in such cases? Can I create a node in the
> Jenkins dashboard directly? How to add tests for  e.g. LTP tests in that (via
> dashboard)?

It *is* possible to create nodes and jobs manually, but it is time-consuming.
I can send you some sample config.xml files for nodes and jobs, that you could
copy for your own use.  Let me know if you'd like me to send some.  We can use
these for debugging, but the method of using ftc add-nodes and ftc add-jobs
really should be working for you.
 -- Tim

> Regards,
> Dhinakar
> 
> Regards
> 
> On Apr 11, 2017 1:04 AM, "Bird, Timothy" <Tim.Bird at sony.com
> <mailto:Tim.Bird at sony.com> > wrote:
> 
> 
> 
> 
> 	> -----Original Message-----
> 	> From: dhinakar k on  Monday, April 10, 2017 12:21 PM
> 	>
> 	> After 'git pull' and getting the recent 1.1.0 version of ftc, I get the
> below error
> 	> while trying to add nodes.
> 	>
> 	> root at Ubuntu-RC510:/fuego-ro/boards# ftc add-nodes dhinakar
> docker
> 	> Error in request. Possibly authentication failed [403]: Forbidden
> 	> Usage: ftc add-nodes [-f] <board1> <board2> ...
> 	>   By convention the name of the node and board is the same. Also,
> 	>   the corresponding board file (<board_name>.board) must exist.
> 	>   Use list-boards to see available boards.
> 	>
> 	>   Use -f for "force" mode. This tries to remove the node before
> adding it
> 	>
> 	>
> 	> '-f' option also give error (check below)
> 	>
> 	> root at Ubuntu-RC510:/fuego-ro/boards# ftc add-nodes -f dhinakar
> 	> dockerError in request. Possibly authentication failed [403]:
> Forbidden
> 	> Usage: ftc add-nodes [-f] <board1> <board2> ...
> 	>   By convention the name of the node and board is the same. Also,
> 	>   the corresponding board file (<board_name>.board) must exist.
> 	>   Use list-boards to see available boards.
> 	>
> 	>   Use -f for "force" mode. This tries to remove the node before
> adding it
> 	>
> 	>
> 	> ftc list-boards output is shown below,
> 	>
> 	> root at Ubuntu-RC510:/fuego-ro/boards# ftc list-boards
> 	> Boards in this system:
> 	>    bbb
> 	>    beaglebone-serial
> 	>    dhinakar
> 	>    docker
> 	>    lager
> 	>    qemu-arm
> 	>    template-dev
> 	>
> 	>
> 	> but ftc list-nodes output show error (as shown below)
> 	>
> 	> root at Ubuntu-RC510:/fuego-ro/boards# ftc list-nodes
> 	> Traceback (most recent call last):
> 	>   File "/usr/local/bin/ftc", line 2982, in <module>
> 	>     main()
> 	>   File "/usr/local/bin/ftc", line 2868, in main
> 	>     do_list_nodes(conf)
> 	>   File "/usr/local/bin/ftc", line 1065, in do_list_nodes
> 	>     node_list = [node['name'] for node in server.get_nodes()]
> 	>   File "/usr/local/lib/python2.7/dist-packages/jenkins/__init__.py",
> line 1170,
> 	> in get_nodes
> 	>     nodes_data =
> 	>
> json.loads(self.jenkins_open(Request(self._build_url(NODE_LIST))))
> 	>   File "/usr/local/lib/python2.7/dist-packages/jenkins/__init__.py",
> line 430,
> 	> in jenkins_open
> 	>     self.maybe_add_crumb(req)
> 	>   File "/usr/local/lib/python2.7/dist-packages/jenkins/__init__.py",
> line 303,
> 	> in maybe_add_crumb
> 	>     self._build_url(CRUMB_URL)), add_crumb=False)
> 	>   File "/usr/local/lib/python2.7/dist-packages/jenkins/__init__.py",
> line 448,
> 	> in jenkins_open
> 	>     e.code, e.msg)
> 	> jenkins.JenkinsException: Error in request. Possibly authentication
> failed
> 	> [403]: Forbidden
> 	>
> 	> Looks like when there are no new nodes initially this exception
> happens.
> 	>
> 	> Please check and let me know.
> 	>
> 	>
> 	> Note: Jenkins version shown in the Dashboard home page is 2.54.
> Could that
> 	> be an issue?
> 
> 	It might be that, or it might be something to do with changing the
> port.
> 	It looks like all remote Jenkins operations are failing, with the
> authentication
> 	failure.  We default to using the 'anonymous' user in Jenkins (as run
> by Fuego).
> 
> 	One thing to check is whether you are talking to the correct Jenkins.
> 	If I recall correctly, you have a different Jenkins running on port 8080,
> and
> 	the Fuego Jenkins running on port 8081.  Is that correct?
> 
> 	If this is the case, can you edit the following line in ftc:
> 
> 	self.JENKINS_URL = "http://localhost:8080/fuego"
> 	and change it to:
> 	self.JENKINS_URL = "http://localhost:8081/fuego"
> 
> 	Let me know if that works.
> 	 -- Tim
> 
> 
> 