Read Me for 8.49.1 and 8.49.2 installs

By Kristina posted 14 days ago

  

The patches for Jama Connect Standard 8.49 introduced some security updates, so we recommend upgrading to 8.49.2 if you are on 8.49.0. (8.49.2 supplanted 8.49.1.) There are some special steps you need to take if Jama Connect is installed on a Red Hat environment, if you access Jama Connect via a proxy, or if you are using Jama Connect Standard Airgap. Note that if you are currently on 8.49.0 and plan to upgrade to 8.56.0 shortly, moving to 8.49.2 is not necessary. 

Red Hat Docker install issue: 

The install.sh script that we provide on our community can not upgrade Docker on RHEL distributions. This is because Red Hat Linux no longer supports Docker 18.09, so the script fails when attempting to upgrade Docker 18.09 via Linux repos. You will see an error that the Docker Repo and mirrors could not be reached while running the install script. You will need to manually install Docker 19.03.  

Example error:

Trying other mirror.
One of the configured repositories failed (Docker main Repository),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=docker-main-repo ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable docker-main-repo
or subscription-manager repos --disable=docker-main-repo
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=docker-main-repo.skip_if_unavailable=true
failure: repodata/0615103afda1f7dfe0638913d6c66d2a52f0e2b15bb4f5a80f9b609d098a6639-filelists.sqlite.bz2 from docker-main-repo: [Errno 256] No more mirrors to try.
https://yum.dockerproject.org/repo/main/centos/7/repodata/0615103afda1f7dfe0638913d6c66d2a52f0e2b15bb4f5a80f9b609d098a6639-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found


How to fix:

1. Get the install .rpm from here: https://download.docker.com/linux/centos/7/x86_64/stable/Packages/docker-ce-19.03.9-3.el7.x86_64.rpm

You can download it via a browser and copy it to the server, or you can use wget on the server to download it directly. 

2. Install Docker 19.03

sudo yum localinstall  https://download.docker.com/linux/centos/7/x86_64/stable/Packages/docker-ce-19.03.9-3.el7.x86_64.rpm

3. start the docker service 

systemctl start docker  

4. run the install script as you normally would just skip the docker install 


 Airgap/Proxied network Connection Refused Issue:

The second issue affects airgapped users and users in proxied environments. The issue is that the replicated and replicated-operator config files are not updated correctly during the upgrade. We are now setting these to use the docker0 address rather than the public address that we used to set up. 

 

You will see "connection refused" errors in the UI and the logs after the upgrade. 

 

How to fix:

1. get the docker0 ip address 

ifconfig docker0

You need the inet address. In this case, it is 172.17.0.1: 

2. get the jamacore IP address 

sudo docker ps | grep coreIn this example, it is 10.11.1.89

3. Edit the replicated file. 

On Debian and Ubuntu systems this file is located in /etc/default/
On RHEL and yum based systems it is located in /etc/sysconfig/ 
Cat the file located at /etc/default/replicated

The file should look something like this:
RELEASE_CHANNEL=stable
PRIVATE_ADDRESS=<Docker0 IP>
SKIP_OPERATOR_INSTALL=0
REPLICATED_OPTS="
REPLICATED_UI_OPTS="" 

Set the PRIVATE_ADDRESS= the docker0 IP 
If you have troubles with this, contact your IT team or server administrator.

4. Edit the replicated-operator file 
On Debian and Ubuntu systems this file is located in /etc/default/
On RHEL and yum based systems it is located in /etc/sysconfig/ 
Cat the file located at /etc/default/replicated-operator

The file should look something like this: 
RELEASE_CHANNEL=stable
DAEMON_ENDPOINT=<Docker0 IP>:9879
DAEMON_TOKEN=Ej7K00R4tEf
DAEMON_HOST=<Docker0 IP>
PRIVATE_ADDRESS=<Docker0 IP>
REPLICATED_OPERATOR_OPTS=" NODENAME=jamadev01 -e PUBLIC_ADDRESS=<JAMA CORE IP>"

set DAEMON_ENDPOINT= the docker0 IP:9879
set DAEMON_HOST=the docker0 IP
set PRIVATE_ADDRESS=the docker0 IP
set PUBLIC_ADDRESS=the jamacore IP

5. restart the replicated services 

sudo systemctl restart replicated
sudo systemctl restart replicated-operator 

6. restart Jama from the admin console

0 comments
38 views