Self-Hosted Traditional issues upgrading to 8.49.1 and 8.49.2

Amanda Jennewein
Amanda Jennewein
  • Updated

Date: November 5, 2020

Audience: Agents and Admins

Environment Details: Self-hosted customers upgrading to 8.49.1 and 8.49.2

Problem/Summary: Customers upgrading to versions 8.49.1 and 8.49.2 have encountered two distinct issues.

  1. Our install.sh script cannot upgrade Docker on RHEL distributions due to Red Hat Linux's lack of support for Docker 18.09. As a result, the upgrade process fails when attempting to upgrade Docker 18.09 via Linux Repos. During installation, you may encounter an error indicating that the Docker repository and mirrors are inaccessible.
  2. The second issue affects air-gapped users and users in proxied environments. The problem is that the replicated and replicated-operator config files must be updated correctly during the upgrade. We are now setting these to use the docker0 address rather than the public address we used to set up. After the upgrade, you will see "connection refused" errors in the UI and the logs. 

 Screen_Shot_2020-11-05_at_2.47.06_PM.png

Solution for Docker install issue: Manually install Docker 19.03. 

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

 

Solution for the Connection Refused Issue:

 

1. get the docker0 ip address 

ifconfig docker0

You need the inet address. In this case 172.17.0.1 (I believe this is always the address but it is good to confirm)

docker.png

 

2. get the jamacore IP address 

sudo docker ps | grep core

In this example, it is 10.11.1.89

core.png

 

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/ 

vi /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_ADDERSS= the docker0 IP 

 

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/ 

vi /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

 

Feedback: Did this article help you resolve the issues described?

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.