Note for Editors: please put each issue in it's own page section
You can change the Jenkins port during installation of Fuego, using an argument to the install.sh script. For example, to install Fuego with Jenkins configured to use port 9999, use the following command during installation:
To change the Jenkins port for an already-built Fuego container, start the container, and inside the container edit the file:
Change the line that says: HTTP_PORT=8090
Change to port to whatever your like.
Also, check the line that defines JENKINS_ARGS. Mine looked like this:
Change this line to read as follows:
Then restart Jenkins:
- $ service jenkins restart
The error string is jenkinssu: System error
Takuo Kogushi provides the following response:
I had the same issue. I did some search in the net and found it is not a problem of fuego itself. As far as I know there are two workarounds;
- 1) Rebuild and install libpam with --disable-audit option (in the container) or
- 2) Modify docker-create-container.sh to add --pid="host" option to docker create command
Here is a patch provided by Koguchi-san:
Actually I have not tried the first one and do not know if there is any side effects for the second. ---
This may be related to this docker bug: https://github.com/docker/docker/issues/5899
- /home/jenkins/fuego/engine/scripts/overlays/base/base-board.fuegoclass because it is missing double quotes.
The symptom is the following: You see the following in the test log for some test you tried to run:
The error string here is "Bad port 'email@example.com'"
This occurs because the port is empty. It should have been passed to the ssh command after the '-p' command line option, but since it is empty, it uses the account-name@address combination as the argument.
The reason it is empty is that a bug in the base-board.fuegoclass is missing the double-quotes.
This is fixed in the fuegotest repository with the following commit:
The timeout for ssh commands is specified in the file
You can change ConnectTimeout to something longer by editing the file.
FIXTHIS - make ConnectTimeout for ssh connections a board-level test variable
The symptom is that when you are watching the console output for a test, the test stops at the point of each SSH connection to the target.
One cause of long ssh connection times can be that the target ssh server (sshd) is configured to do DNS lookups on each inbound connection.
To turn this off, on the target, edit the file:
- /etc/ssh/sshd_config and add the line:
This line can be added anywhere in the file, but I recommend adding it right after the UsePrivilegeSeparation line (if that's there).