[Fuego] Fuego v1.1 setup queries

[Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

Hi,

I tried setting up Fuego v1.1 based on the Fuego_Quickstart_Guide. Please
find my queries based on that below.

1. Only Jenkins CI server and network benchmark servers are started when I
execute 'fuego-host-scripts/docker-start-container.sh' and the control goes
to 'root@linux-pc-name:/#' after that. Is that fine? Is this what you call
as 'container prompt'?

2. Typo in 'Create board file' section. '$ cd fuego-rw/boards' instead of '$
cd fuego-ro/boards'

3. (container prompt)$ FTC add-nodes myboard docker doesn't work. I get
missing or unrecognized command. Use "ftc help" to get usage help. Where is
the list of 'ftc global options' available?

Iam currently stuck while adding a node that I created. Please clarify the
above so that I could proceed further.

Regards,
Dhinakar

[-- Attachment #2: Type: text/html, Size: 1534 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

One more thing, $ ftc list-plans returns unrecognized command and if I try
$ ftc list plan I could see 'OSError: [Errno 2] No such file or directory:
'/home/jenkins/overlays/testplans' error point to the older path.

Regards,
Dhinakar

On Apr 10, 2017 7:08 PM, "dhinakar k" <dhinakar.k@gmail.com> wrote:

Hi,

I tried setting up Fuego v1.1 based on the Fuego_Quickstart_Guide. Please
find my queries based on that below.

1. Only Jenkins CI server and network benchmark servers are started when I
execute 'fuego-host-scripts/docker-start-container.sh' and the control goes
to 'root@linux-pc-name:/#' after that. Is that fine? Is this what you call
as 'container prompt'?

2. Typo in 'Create board file' section. '$ cd fuego-rw/boards' instead of '$
cd fuego-ro/boards'

3. (container prompt)$ FTC add-nodes myboard docker doesn't work. I get
missing or unrecognized command. Use "ftc help" to get usage help. Where is
the list of 'ftc global options' available?

Iam currently stuck while adding a node that I created. Please clarify the
above so that I could proceed further.

Regards,
Dhinakar

[-- Attachment #2: Type: text/html, Size: 2203 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[Bird, Timothy]

> -----Original Message-----
> From: dhinakar k on Monday, April 10, 2017 6:39 AM
>
> I tried setting up Fuego v1.1 based on the Fuego_Quickstart_Guide. Please
> find my queries based on that below.
> 
> 1. Only Jenkins CI server and network benchmark servers are started when I
> execute 'fuego-host-scripts/docker-start-container.sh' and the control goes
> to 'root@linux-pc-name:/#' after that. Is that fine? Is this what you call as
> 'container prompt'?
Yes.

> 
> 2. Typo in 'Create board file' section. '$ cd fuego-rw/boards' instead of '$ cd
> fuego-ro/boards'

Thanks for the report.  I fixed it.
 
> 
> 3. (container prompt)$ FTC add-nodes myboard docker doesn't work. I get
> missing or unrecognized command. Use "ftc help" to get usage help. Where
> is the list of 'ftc global options' available?
> 
> 
> Iam currently stuck while adding a node that I created. Please clarify the
> above so that I could proceed further.

Sorry - the bug that Daniel reported (that I screwed up ftc in the last commit
of the 1.1.0 release) is the problem here.  I've fixed this in the master
branch.  I haven't done my own build and testing yet.  I'll have more
confidence in my fix in about an hour.  But you can try this now:

Outside the container, cd to fuego-core.
There, do a 'git pull' command, to get the correct 'ftc' version.
 $ cd <some-dir>/fuego-core
 $ git pull

Inside the container (at the container prompt), verify that you got the right ftc
with 'ftc version'

   # ftc version
ftc: version 1.1.0

This version of ftc should support the add-nodes and add-jobs commands necessary
to continue.

Thanks for hanging in there, and for the bug reports.
 -- Tim

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

Hi Tim,

Thanks much for the prompt response.
I will do a git pull and then try and let you know if any further issues.

Regards,
Dhinakar

On Mon, Apr 10, 2017 at 11:03 PM, Bird, Timothy <Tim.Bird@sony.com> wrote:

>
>
> > -----Original Message-----
> > From: dhinakar k on Monday, April 10, 2017 6:39 AM
> >
> > I tried setting up Fuego v1.1 based on the Fuego_Quickstart_Guide. Please
> > find my queries based on that below.
> >
> > 1. Only Jenkins CI server and network benchmark servers are started when
> I
> > execute 'fuego-host-scripts/docker-start-container.sh' and the control
> goes
> > to 'root@linux-pc-name:/#' after that. Is that fine? Is this what you
> call as
> > 'container prompt'?
> Yes.
>
> >
> > 2. Typo in 'Create board file' section. '$ cd fuego-rw/boards' instead
> of '$ cd
> > fuego-ro/boards'
>
> Thanks for the report.  I fixed it.
>
> >
> > 3. (container prompt)$ FTC add-nodes myboard docker doesn't work. I get
> > missing or unrecognized command. Use "ftc help" to get usage help. Where
> > is the list of 'ftc global options' available?
> >
> >
> > Iam currently stuck while adding a node that I created. Please clarify
> the
> > above so that I could proceed further.
>
> Sorry - the bug that Daniel reported (that I screwed up ftc in the last
> commit
> of the 1.1.0 release) is the problem here.  I've fixed this in the master
> branch.  I haven't done my own build and testing yet.  I'll have more
> confidence in my fix in about an hour.  But you can try this now:
>
> Outside the container, cd to fuego-core.
> There, do a 'git pull' command, to get the correct 'ftc' version.
>  $ cd <some-dir>/fuego-core
>  $ git pull
>
> Inside the container (at the container prompt), verify that you got the
> right ftc
> with 'ftc version'
>
>    # ftc version
> ftc: version 1.1.0
>
> This version of ftc should support the add-nodes and add-jobs commands
> necessary
> to continue.
>
> Thanks for hanging in there, and for the bug reports.
>  -- Tim
>
>

[-- Attachment #2: Type: text/html, Size: 2750 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 4638 bytes --]

Hi Tim,

After 'git pull' and getting the recent 1.1.0 version of ftc, I get the
below error while
trying to add nodes.

root@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@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@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@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?

Regards,
Dhinakar

On Mon, Apr 10, 2017 at 11:59 PM, dhinakar k <dhinakar.k@gmail.com> wrote:

> Hi Tim,
>
> Thanks much for the prompt response.
> I will do a git pull and then try and let you know if any further issues.
>
> Regards,
> Dhinakar
>
> On Mon, Apr 10, 2017 at 11:03 PM, Bird, Timothy <Tim.Bird@sony.com> wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: dhinakar k on Monday, April 10, 2017 6:39 AM
>> >
>> > I tried setting up Fuego v1.1 based on the Fuego_Quickstart_Guide.
>> Please
>> > find my queries based on that below.
>> >
>> > 1. Only Jenkins CI server and network benchmark servers are started
>> when I
>> > execute 'fuego-host-scripts/docker-start-container.sh' and the control
>> goes
>> > to 'root@linux-pc-name:/#' after that. Is that fine? Is this what you
>> call as
>> > 'container prompt'?
>> Yes.
>>
>> >
>> > 2. Typo in 'Create board file' section. '$ cd fuego-rw/boards' instead
>> of '$ cd
>> > fuego-ro/boards'
>>
>> Thanks for the report.  I fixed it.
>>
>> >
>> > 3. (container prompt)$ FTC add-nodes myboard docker doesn't work. I get
>> > missing or unrecognized command. Use "ftc help" to get usage help. Where
>> > is the list of 'ftc global options' available?
>> >
>> >
>> > Iam currently stuck while adding a node that I created. Please clarify
>> the
>> > above so that I could proceed further.
>>
>> Sorry - the bug that Daniel reported (that I screwed up ftc in the last
>> commit
>> of the 1.1.0 release) is the problem here.  I've fixed this in the master
>> branch.  I haven't done my own build and testing yet.  I'll have more
>> confidence in my fix in about an hour.  But you can try this now:
>>
>> Outside the container, cd to fuego-core.
>> There, do a 'git pull' command, to get the correct 'ftc' version.
>>  $ cd <some-dir>/fuego-core
>>  $ git pull
>>
>> Inside the container (at the container prompt), verify that you got the
>> right ftc
>> with 'ftc version'
>>
>>    # ftc version
>> ftc: version 1.1.0
>>
>> This version of ftc should support the add-nodes and add-jobs commands
>> necessary
>> to continue.
>>
>> Thanks for hanging in there, and for the bug reports.
>>  -- Tim
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 6155 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[Bird, Timothy]

> -----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@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@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@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@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

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 4378 bytes --]

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?
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)?

Regards,
Dhinakar

Regards

On Apr 11, 2017 1:04 AM, "Bird, Timothy" <Tim.Bird@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@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@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@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@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
>
>
>

[-- Attachment #2: Type: text/html, Size: 5817 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[Bird, Timothy]

> -----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@sony.com
> <mailto:Tim.Bird@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@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@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@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@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
> 
> 
> 

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 7556 bytes --]

Hi Tim,

Thanks for the prompt response.
Yes it is because of my environment. The Jenkins v2.54 running on port 8080
is the problem. I will uninstall​ Jenkins on the host and try installing
Fuego again. Meanwhile Iam in office now, here ftc commands work fine after
'git pull' in ftc-core directory. The Jenkins version on the dashboard is
v2.32.1 as per Dockerfile.

Regarding creating nodes and jobs manually, please send me sample
config.xml files, I will keep it as a backup.

Regards,
Dhinakar


On Apr 11, 2017 9:00 AM, "Bird, Timothy" <Tim.Bird@sony.com> wrote:

> -----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@sony.com
> <mailto:Tim.Bird@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@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@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@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@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
>
>
>

[-- Attachment #2: Type: text/html, Size: 10419 bytes --]

Re: [Fuego] Fuego v1.1 setup queries

[Bird, Timothy]

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]



> -----Original Message-----
> From: dhinakar k on Monday, April 10, 2017 8:51 PM
> Hi Tim,
> 
> Thanks for the prompt response.
> Yes it is because of my environment. The Jenkins v2.54 running on port 8080
> is the problem. I will uninstall​ Jenkins on the host and try installing Fuego
> again. Meanwhile Iam in office now, here ftc commands work fine after 'git
> pull' in ftc-core directory. The Jenkins version on the dashboard is v2.32.1 as
> per Dockerfile.
> 
> Regarding creating nodes and jobs manually, please send me sample
> config.xml files, I will keep it as a backup.

Here are some samples:
bbb-node-config.xml was copied from /var/lib/jenkins/nodes/bbb/config.xml in my Docker container.
bbb.default.Functional.hello_world-config.xml was copied from
/var/lib/jenkins/jobs/bbb.default.Functional.hello_world/config.xml in my Docker container.

Now that you've got 'ftc add-nodes' and 'ftc add-jobs' working, you should be able to create
files like these from the command line.  But if you put these (renamed to just 'config.xml'
into appropriate directories, and then have Jenkins re-read its configuration, these should
show up inside the Jenkins interface.  To have Jenkins re-read its configuration, go to
the top Jenkins menu in the dashboard (by clicking on the Jenkins icon or the Jenkins menu
item at the top left of any Jenkins interface page.)  The select "Manage Jenkins", then select
"Reload Configuration from Disk" (about 4 items down on the page that appears).

 -- Tim
 

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: bbb.default.Functional.hello_world-config.xml --]
[-- Type: text/xml; name="bbb.default.Functional.hello_world-config.xml", Size: 1637 bytes --]

<?xml version="1.0" encoding="UTF-8"?><project>
    <actions/>
    <description/>
    <keepDependencies>false</keepDependencies>
    <properties/>
    <scm class="hudson.scm.NullSCM"/>
    <assignedNode>bbb</assignedNode>
    <canRoam>false</canRoam>
    <disabled>false</disabled>
    <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
    <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
    <triggers/>
    <concurrentBuild>false</concurrentBuild>
    <customWorkspace>$FUEGO_RW/buildzone</customWorkspace>
    <builders>
    <hudson.tasks.Shell>
        <command>export Reboot=false
export Rebuild=true
export Target_PreCleanup=true
export Target_PostCleanup=true
export TESTDIR=Functional.hello_world
export TESTNAME=hello_world
export TESTSPEC=default
#export FUEGO_DEBUG=1
timeout --signal=9 100m /bin/bash $FUEGO_CORE/engine/tests/${TESTDIR}/${TESTNAME}.sh
</command>
    </hudson.tasks.Shell>
    </builders>
    <publishers>
    
    <hudson.plugins.descriptionsetter.DescriptionSetterPublisher plugin="description-setter@1.10">
      <regexp/>
      <regexpForFailed/>
      <description>&lt;a href="/fuego/userContent/fuego.logs/Functional.hello_world/bbb.default.${BUILD_NUMBER}.${BUILD_ID}/testlog.txt"&gt;log&lt;/a&gt;</description>
      <descriptionForFailed>&lt;a href="/fuego/userContent/fuego.logs/Functional.hello_world/bbb.default.${BUILD_NUMBER}.${BUILD_ID}/testlog.txt"&gt;log&lt;/a&gt;</descriptionForFailed>
      <setForMatrix>false</setForMatrix>
    </hudson.plugins.descriptionsetter.DescriptionSetterPublisher>
    </publishers>
    <buildWrappers/>
</project>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: bbb-node-config.xml --]
[-- Type: text/xml; name="bbb-node-config.xml", Size: 414 bytes --]

<?xml version='1.0' encoding='UTF-8'?>
<slave>
  <name>bbb</name>
  <remoteFS>/var/lib/jenkins</remoteFS>
  <numExecutors>1</numExecutors>
  <mode>NORMAL</mode>
  <retentionStrategy class="hudson.slaves.RetentionStrategy$Always"/>
  <launcher class="hudson.slaves.CommandLauncher">
    <agentCommand>java -jar /fuego-core/engine/slave.jar</agentCommand>
  </launcher>
  <label></label>
  <nodeProperties/>
</slave>

Re: [Fuego] Fuego v1.1 setup queries

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

Thanks Tim, I will check them out and get back if I have any queries.

Regards,
Dhinakar

On Apr 11, 2017 10:11 AM, "Bird, Timothy" <Tim.Bird@sony.com> wrote:

>
>
> > -----Original Message-----
> > From: dhinakar k on Monday, April 10, 2017 8:51 PM
> > Hi Tim,
> >
> > Thanks for the prompt response.
> > Yes it is because of my environment. The Jenkins v2.54 running on port
> 8080
> > is the problem. I will uninstall​ Jenkins on the host and try installing
> Fuego
> > again. Meanwhile Iam in office now, here ftc commands work fine after
> 'git
> > pull' in ftc-core directory. The Jenkins version on the dashboard is
> v2.32.1 as
> > per Dockerfile.
> >
> > Regarding creating nodes and jobs manually, please send me sample
> > config.xml files, I will keep it as a backup.
>
> Here are some samples:
> bbb-node-config.xml was copied from /var/lib/jenkins/nodes/bbb/config.xml
> in my Docker container.
> bbb.default.Functional.hello_world-config.xml was copied from
> /var/lib/jenkins/jobs/bbb.default.Functional.hello_world/config.xml in my
> Docker container.
>
> Now that you've got 'ftc add-nodes' and 'ftc add-jobs' working, you should
> be able to create
> files like these from the command line.  But if you put these (renamed to
> just 'config.xml'
> into appropriate directories, and then have Jenkins re-read its
> configuration, these should
> show up inside the Jenkins interface.  To have Jenkins re-read its
> configuration, go to
> the top Jenkins menu in the dashboard (by clicking on the Jenkins icon or
> the Jenkins menu
> item at the top left of any Jenkins interface page.)  The select "Manage
> Jenkins", then select
> "Reload Configuration from Disk" (about 4 items down on the page that
> appears).
>
>  -- Tim
>
>

[-- Attachment #2: Type: text/html, Size: 2284 bytes --]