Upgrade to Ambari 7.1.x.0

After reviewing the information related to Ambari UI and the Quick Links, and backing up the Ambari Server configuration file, perform the recommended steps for upgrading Ambari.

Upgrading Ambari

Loading Filters ...

Upgrade to Ambari 7.1.8

After reviewing the information related to Ambari UI and the Quick Links, and backing up the Ambari Server configuration file, perform the recommended steps for upgrading Ambari.

If you are running Ambari Metrics in your cluster, stop the service and put it in Maintenance Mode. From Ambari Web, browse to Services > Ambari Metrics and select Stop from the Service Actions menu.
Stop the Ambari Server. On the host running Ambari Server: ambari-server stop
Stop all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent stop.
Fetch the new Ambari repo and replace the old repository file with the new repository file on all hosts in your cluster.

important
Important: Check your current directory before you download the new repository file to make sure that there are no previous versions of the ambaridc.repo file. If you do not, and a previous version exists, the new download will be saved with a numeric extension, such as ambari.repo.1. Make sure that the version you copy is the new version.
Select the repository appropriate for your environment from the following list:
- For RHEL/CentOS/Oracle Linux 7:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8/centos7/ambari.repo -O /etc/yum.repos.d/ambari.repo 
```
- For Ubuntu 18:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8/ubuntu18/ambari.list -O /etc/apt/sources.list.d/ambari.list
```
- For Sles 12:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8/sles12/ambari.repo -O /etc/zypp/repos.d/ambari.repo
```

Upgrade Ambari Server. On the host running Ambari Server:

For RHEL/CentOS/Oracle Linux:

yum clean all

Before upgrading Ambari Server, you must update the username and password of baseurl and gpgkey in the ambari.repo file. Run the following command:

vi /etc/yum.repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                            [ambari-7.1.8.0
                            #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                            name=ambari Version - ambari-7.1.8.0
                            baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/centos7
                            gpgcheck=1
                            gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
                            enabled=1
                            priority=1

yum info ambari-server

In the information output, visually validate that there is an available version containing "7.1.8.0"

yum upgrade ambari-server

For Ubuntu 18:

apt-get clean all

Before upgrading Ambari Server, you must update the username and password in the ambari.list file. Run the following command:

vi /etc/apt/sources.list.d/ambari.list

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                            #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                            deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/ubuntu18 Ambari main
                            apt-get update
                            apt-cache show ambari-server | grep Version

In the information output, visually validate that there is an available version containing "7.1.8.0"

apt-get upgrade ambari-server

For SLES 12:

zypper clean

Before upgrading Ambari Server, you must update the username and password in the ambari.repo file. Run the following command:   

vi /etc/zypp/repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                            [ambari-7.1.8.0]
                            #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                            name=ambari Version - ambari-7.1.8.0
                            baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/sles12
                            gpgcheck=0
                            gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
                            enabled=1
                            priority=1

Create the following file with your paywall credentials (replace <username> with your paywall username and <password> accordingly): /etc/zypp/credentials.d/ambari.cat

username=<username> 
                            password=<password>

In the information output, visually validate that there is an available version containing "7.1.8.0"

Zypper up ambari-server

After the upgrade process completes, check Ambari host to make sure the new files have been installed:

For RHEL/CentOS/Oracle Linux 7:rpm -qa | grep ambari-server

For SLES 12:rpm -qa | grep ambari-server
For Ubuntu 18:
```
dpkg -l ambari-server
```
Check for upgrade success by noting progress during the Ambari Server installation process you started in Step 5.
- As the process runs, the console displays output similar to the following:
  
  Setting up Upgrade Process Resolving Dependencies > Running transaction check
- If the upgrade fails, the console displays output similar to the following:
  
  Setting up Upgrade Process No Packages marked for Update
- A successful upgrade displays output similar to the following:
  
  Updated: ambari-server.noarch 0:7.1.8.0. Complete!
important
Confirm there is only one ambari-server*.jar file in /usr/lib/ambari-server. If there is more than one JAR file with name ambari-server*.jar, move all JARs except ambari-server-7.1.8*.jar to /tmp before proceeding with upgrade.

Upgrade all Ambari Agents. On each host in your cluster running an Ambari Agent:

For RHEL/CentOS/Oracle Linux: Before upgrading Ambari Agent, you must update the username and password in the ambari.repo file. Run the following command:

vi /etc/yum.repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                                    [ambari-7.1.8.0
                                    #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                                    name=ambari Version - ambari-7.1.8.0
                                    baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/centos7
                                    gpgcheck=1
                                    gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
                                    enabled=1
                                    priority=1

yum upgrade ambari-agent

For Ubuntu: Before upgrading Ambari Agent, you must update the username and password in the ambari.list file. Run the following command:   

vi /etc/apt/sources.list.d/ambari.list

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                                    #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                                    deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/ubuntu18 Ambari main

apt-get update
                                        apt-get install ambari-agent

For SLES: Before upgrading Ambari Agent, you must update the username and password in the ambaridc.repo file. Run the following command:   

vi /etc/zypp/repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.8.0-21
                                    [ambari-7.1.8.0]
                                    #json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
                                    name=ambari Version - ambari-7.1.8.0
                                    baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/sles12
                                    gpgcheck=0
                                    gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.8.0/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
                                    enabled=1
                                    priority=1

Perform ambari-agent upgrade

zypper up ambari-agent

After the upgrade process completes, check Ambari host to make sure the new files have been installed:
For RHEL/CentOS/Oracle Linux 7:
```
rpm -qa | grep ambari-agent
```
For SLES 12:
```
rpm -qa | grep ambari-agent
```
For Ubuntu 18:
```
dpkg -l ambari-agent 
```
Upgrade Ambari Server database schema. On the host running Ambari Server: ambari-server upgrade. When the Ambari Server database schema has been upgraded, you should see command output like this: Ambari Server ‘upgrade’ completed successfully.
Start the Ambari Server. On the host running Ambari Server: ambari-server start
Start all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent start
Open Ambari Web UI. Point your browser to the Ambari Web UI:
- When Ambari Server is configured for HTTPS: https://<your.ambari.server>:8443
- When Ambari Server is configured for HTTP: http://<your.ambari.server>:8080
where <your.ambari.server> is the name of your ambari server host. For example, c7401.ambari.apache.org.

important
Refresh your browser so that it loads the new version of the Ambari Web code. If you have problems, clear your browser cache manually, then restart Ambari Server.
Log in using the Ambari administrator credentials that you have set up. For example, the default name/password is admin/admin. You will see a Restart indicator next to each service after upgrading. Ambari upgrade has modified the configuration properties of your cluster based on the new configuration types and properties being made available for each service with this release of Ambari. Review these changes by comparing the previous configuration with the latest version created by "ambari-upgrade".

caution
Do not manually restart these services unless future steps in the upgrade guide prompt you to do so. Manually restarting these services may significantly disrupt your upgrade. Ambari will restart each service automatically during the HDP upgrade.

note
Even though the installer prompts you to sync LDAP, doing so is not required.

Upgrade to Ambari 7.1.7.1

After reviewing the information related to Ambari UI and the Quick Links, and backing up the Ambari Server configuration file, perform the recommended steps for upgrading Ambari.

If you are running Ambari Metrics in your cluster, stop the service and put it in Maintenance Mode. From Ambari Web, browse to Services > Ambari Metrics and select Stop from the Service Actions menu.
Stop the Ambari Server. On the host running Ambari Server: ambari-server stop
Stop all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent stop.
Fetch the new Ambari repo and replace the old repository file with the new repository file on all hosts in your cluster.

important
Important: Check your current directory before you download the new repository file to make sure that there are no previous versions of the ambaridc.repo file. If you do not, and a previous version exists, the new download will be saved with a numeric extension, such as ambari.repo.1. Make sure that the version you copy is the new version.
Select the repository appropriate for your environment from the following list:
- For RHEL/CentOS/Oracle Linux 7:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/centos7/ambari.repo -O /etc/yum.repos.d/ambari.repo 
```
- For Ubuntu 18:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/ubuntu18/ambari.list -O /etc/apt/sources.list.d/ambari.list
```
- For Sles 12:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/sles12/ambari.repo -O /etc/zypp/repos.d/ambari.repo
```

Upgrade Ambari Server. On the host running Ambari Server:

For RHEL/CentOS/Oracle Linux:

yum clean all

Before upgrading Ambari Server, you must update the username and password of baseurl and gpgkey in the ambari.repo file. Run the following command:

vi /etc/yum.repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
[ambari-7.1.7.1]
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.7.1
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/centos7
gpgcheck=1
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

yum info ambari-server

In the information output, visually validate that there is an available version containing "7.1.7.1"

yum upgrade ambari-server

For Ubuntu 18:

apt-get clean all

Before upgrading Ambari Server, you must update the username and password in the ambari.list file. Run the following command:

vi /etc/apt/sources.list.d/ambari.list

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/ubuntu18 Ambari main
apt-get update
apt-cache show ambari-server | grep Version

In the information output, visually validate that there is an available version containing "7.1.7.1"

apt-get upgrade ambari-server

For SLES 12:

zypper clean

Before upgrading Ambari Server, you must update the username and password in the ambari.repo file. Run the following command:   

vi /etc/zypp/repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
[ambari-7.1.7.1]
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.7.1
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/sles12
gpgcheck=0
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

Create the following file with your paywall credentials (replace <username> with your paywall username and <password> accordingly): /etc/zypp/credentials.d/ambari.cat

username=<username> 
password=<password>

In the information output, visually validate that there is an available version containing "7.1.7.1"

Zypper up ambari-server

After the upgrade process completes, check Ambari host to make sure the new files have been installed:

For RHEL/CentOS/Oracle Linux 7:rpm -qa | grep ambari-server

For SLES 12:rpm -qa | grep ambari-server
For Ubuntu 18:
```
dpkg -l ambari-server
```
Check for upgrade success by noting progress during the Ambari Server installation process you started in Step 5.
- As the process runs, the console displays output similar to the following:
  
  Setting up Upgrade Process Resolving Dependencies > Running transaction check
- If the upgrade fails, the console displays output similar to the following:
  
  Setting up Upgrade Process No Packages marked for Update
- A successful upgrade displays output similar to the following:
  
  Updated: ambari-server.noarch 0:7.1.7.1. Complete!
important
Confirm there is only one ambari-server*.jar file in /usr/lib/ambari-server. If there is more than one JAR file with name ambari-server*.jar, move all JARs except ambari-server-7.1.7*.jar to /tmp before proceeding with upgrade.

Upgrade all Ambari Agents. On each host in your cluster running an Ambari Agent:

For RHEL/CentOS/Oracle Linux: Before upgrading Ambari Agent, you must update the username and password in the ambari.repo file. Run the following command:

vi /etc/yum.repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
[ambari-7.1.7.1]
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.7.1
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/centos7
gpgcheck=1
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

yum upgrade ambari-agent

For Ubuntu: Before upgrading Ambari Agent, you must update the username and password in the ambari.list file. Run the following command:   

vi /etc/apt/sources.list.d/ambari.list

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/ubuntu18 Ambari main

apt-get update
apt-get install ambari-agent

For SLES: Before upgrading Ambari Agent, you must update the username and password in the ambaridc.repo file. Run the following command:   

vi /etc/zypp/repos.d/ambari.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.7.1-14
[ambari-7.1.7.1]
#json.url = https://archive.cloudera.com/p/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.7.1
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/sles12
gpgcheck=0
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.7.1/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

Perform ambari-agent upgrade

zypper up ambari-agent

After the upgrade process completes, check Ambari host to make sure the new files have been installed:
For RHEL/CentOS/Oracle Linux 7:
```
rpm -qa | grep ambari-agent
```
For SLES 12:
```
rpm -qa | grep ambari-agent
```
For Ubuntu 18:
```
dpkg -l ambari-agent 
```
Upgrade Ambari Server database schema. On the host running Ambari Server: ambari-server upgrade. When the Ambari Server database schema has been upgraded, you should see command output like this: Ambari Server ‘upgrade’ completed successfully.
Start the Ambari Server. On the host running Ambari Server: ambari-server start
Start all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent start
Open Ambari Web UI. Point your browser to the Ambari Web UI:
- When Ambari Server is configured for HTTPS: https://<your.ambari.server>:8443
- When Ambari Server is configured for HTTP: http://<your.ambari.server>:8080
where <your.ambari.server> is the name of your ambari server host. For example, c7401.ambari.apache.org.

important
Refresh your browser so that it loads the new version of the Ambari Web code. If you have problems, clear your browser cache manually, then restart Ambari Server.
Log in using the Ambari administrator credentials that you have set up. For example, the default name/password is admin/admin. You will see a Restart indicator next to each service after upgrading. Ambari upgrade has modified the configuration properties of your cluster based on the new configuration types and properties being made available for each service with this release of Ambari. Review these changes by comparing the previous configuration with the latest version created by "ambari-upgrade".

caution
Do not manually restart these services unless future steps in the upgrade guide prompt you to do so. Manually restarting these services may significantly disrupt your upgrade. Ambari will restart each service automatically during the HDP upgrade.
note
Even though the installer prompts you to sync LDAP, doing so is not required.
note
While upgrading from HDP 3.1.5 to CDP Private Cloud Base 7.1.7 using Ambari 7.1.7, you may encounter the following error message
```
Fail: HBase is not ready to upgrade.
```
.
The workaround is to click IGNORE AND PROCEED.

Upgrade to Ambari 7.1.6.0

After reviewing the information related to Ambari UI and the Quick Links, and backing up the Ambari Server configuration file, perform the recommended steps for upgrading Ambari.

If you are running Ambari Metrics in your cluster, stop the service and put it in Maintenance Mode. From Ambari Web, browse to Services > Ambari Metrics and select Stop from the Service Actions menu.
Stop the Ambari Server. On the host running Ambari Server: ambari-server stop
Stop all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent stop.
Fetch the new Ambari repo and replace the old repository file with the new repository file on all hosts in your cluster.

important
Important: Check your current directory before you download the new repository file to make sure that there are no previous versions of the ambaridc.repo file. If you do not, and a previous version exists, the new download will be saved with a numeric extension, such as ambaridc.repo.1. Make sure that the version you copy is the new version.
Select the repository appropriate for your environment from the following list:
- For RHEL/CentOS/Oracle Linux 7:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/centos7/ambaridc.repo -O /etc/yum.repos.d/ambaridc.repo 
```
- For Ubuntu 18:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/ubuntu18/ambaridc.list -O /etc/apt/sources.list.d/ambaridc.list
```
- For Sles 12:
```
wget -nv https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/sles12/ambaridc.repo -O /etc/zypp/repos.d/ambari.repo
```
Upgrade Ambari Server. On the host running Ambari Server:
For RHEL/CentOS/Oracle Linux:
```
yum clean all
```
Before upgrading Ambari Server, you must update the username and password of baseurl and gpgkey in the ambaridc.repo file. Run the following command:
```
vi /etc/yum.repos.d/ambaridc.repo
```
For example, the output displays the following:
```
#VERSION_NUMBER=7.1.6.0-38
[ambari-7.1.6.0]
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.6.0
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/centos7/
gpgcheck=1
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1
```
```
yum info ambari-server
```
In the information output, visually validate that there is an available version containing "7.1.6.0"
```
yum upgrade ambari-server
```
For Ubuntu 18:
```
apt-get clean all
```
Before upgrading Ambari Server, you must update the username and password in the ambaridc.list file. Run the following command:
```
vi /etc/apt/sources.list.d/ambaridc.list
```
For example, the output displays the following:
```
#VERSION_NUMBER=7.1.6.0-38
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/ubuntu18/ Ambari main                       
apt-get update
apt-cache show ambari-server | grep Version 
```
In the information output, visually validate that there is an available version containing "7.1.6.0"
```
apt-get upgrade ambari-server
```
For SLES 12:
```
zypper clean
```
Before upgrading Ambari Server, you must update the username and password in the ambari.repo file. Run the following command:   
```
vi /etc/zypp/repos.d/ambaridc.repo
```
For example, the output displays the following:
```
#VERSION_NUMBER=7.1.6.0-38
[ambari-7.1.6.0]
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.6.0
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/sles12/
gpgcheck=0
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1           
```
Create the following file with your paywall credentials (replace <username> with your paywall username and <password> accordingly): /etc/zypp/credentials.d/ambari.cat
```
username=<username> 
password=<password>
```
In the information output, visually validate that there is an available version containing "7.1.6.0"
```
Zypper up ambari-server
```
After the upgrade process completes, check Ambari host to make sure the new files have been installed:

For RHEL/CentOS/Oracle Linux 7:rpm -qa | grep ambari-server

For SLES 12:rpm -qa | grep ambari-server
For Ubuntu 18:
```
dpkg -l ambari-server
```
Check for upgrade success by noting progress during the Ambari Server installation process you started in Step 5.
- As the process runs, the console displays output similar to the following:
  
  Setting up Upgrade Process Resolving Dependencies > Running transaction check
- If the upgrade fails, the console displays output similar to the following:
  
  Setting up Upgrade Process No Packages marked for Update
- A successful upgrade displays output similar to the following:
  
  Updated: ambari-server.noarch 0:7.1.6.0. Complete!
important
Confirm there is only one ambari-server*.jar file in /usr/lib/ambari-server. If there is more than one JAR file with name ambari-server*.jar, move all JARs except ambari-server-7.1.6*.jar to /tmp before proceeding with upgrade.

Upgrade all Ambari Agents. On each host in your cluster running an Ambari Agent:

For RHEL/CentOS/Oracle Linux: Before upgrading Ambari Agent, you must update the username and password in the ambaridc.repo file. Run the following command:

vi /etc/yum.repos.d/ambaridc.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.6.0-38
[ambari-7.1.6.0]
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.6.0
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/centos7/
gpgcheck=1
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/centos7/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

yum upgrade ambari-agent

For Ubuntu: Before upgrading Ambari Agent, you must update the username and password in the ambari.list file. Run the following command:   

vi /etc/apt/sources.list.d/ambaridc.list

For example, the output displays the following:

#VERSION_NUMBER=7.1.6.0-38
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
deb https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/ubuntu18/ Ambari main

apt-get update
apt-get install ambari-agent

For SLES: Before upgrading Ambari Agent, you must update the username and password in the ambaridc.repo file. Run the following command:   

vi /etc/zypp/repos.d/ambaridc.repo

For example, the output displays the following:

#VERSION_NUMBER=7.1.6.0-38
[ambari-7.1.6.0]
#json.url = http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
name=ambari Version - ambari-7.1.6.0
baseurl=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/sles12/
gpgcheck=0
gpgkey=https://[***USERNAME***]:[***PASSWORD***]@archive.cloudera.com/p/ambaridc/7.x/7.1.6.0/sles12/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

Perform ambari-agent upgrade

zypper up ambari-agent

After the upgrade process completes, check Ambari host to make sure the new files have been installed:
For RHEL/CentOS/Oracle Linux 7:
```
rpm -qa | grep ambari-agent
```
For SLES 12:
```
rpm -qa | grep ambari-agent
```
For Ubuntu 18:
```
dpkg -l ambari-agent 
```
Upgrade Ambari Server database schema. On the host running Ambari Server: ambari-server upgrade. When the Ambari Server database schema has been upgraded, you should see command output like this: Ambari Server ‘upgrade’ completed successfully.
Start the Ambari Server. On the host running Ambari Server: ambari-server start
Start all Ambari Agents. On each host in your cluster running an Ambari Agent: ambari-agent start
Open Ambari Web UI. Point your browser to the Ambari Web UI:
- When Ambari Server is configured for HTTPS: https://<your.ambari.server>:8443
- When Ambari Server is configured for HTTP: http://<your.ambari.server>:8080
where <your.ambari.server> is the name of your ambari server host. For example, c7401.ambari.apache.org.

important
Refresh your browser so that it loads the new version of the Ambari Web code. If you have problems, clear your browser cache manually, then restart Ambari Server.
Log in using the Ambari administrator credentials that you have set up. For example, the default name/password is admin/admin. You will see a Restart indicator next to each service after upgrading. Ambari upgrade has modified the configuration properties of your cluster based on the new configuration types and properties being made available for each service with this release of Ambari. Review these changes by comparing the previous configuration with the latest version created by "ambari-upgrade".

caution
Do not manually restart these services unless future steps in the upgrade guide prompt you to do so. Manually restarting these services may significantly disrupt your upgrade. Ambari will restart each service automatically during the HDP upgrade.

note
Even though the installer prompts you to sync LDAP, doing so is not required.