3. Upgrading Ambari Server and Agents

Local repository installs only: Copy the old stacks definition file (/var/lib/ambari-server/resources/stacks/HDPLocal/[1.2.0 or 1.2.1]/repos/repoinfo.xml to a safe place. You will be using it in Step 7.

Upgrade the Server:

For RHEL/CentOS

yum clean all
yum upgrade ambari-server ambari-log4j

For SLES

zypper clean
zypper up ambari-server ambari-log4j

Check for upgrade success:
- As the process runs, the console should produce output similar, although not identical, to this:
```
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package ambari-agent.x86_64 0:1.2.2.3-1 will be updated
---> Package ambari-agent.x86_64 0:1.2.2.4-1 will be an update ...
```
  Once the process is complete, check each host to make sure the new files have been installed:
```
rpm -qa | grep ambari
```
- If the upgrade fails, the console should produce output similar to this:
```
Setting up Upgrade Process
No Packages marked for Update
```
Check to see if you have a folder named /etc/ambari-server/conf.save. If you do, rename it back:
```
mv /etc/ambari-server/conf.save /etc/ambari-server/conf
```
To save any customizations you may have made to the properties file, copy the following properties from the new properties file version named /etc/ambari-server/conf/ambari.properties to the old properties file version named /etc/ambari-server/conf/ambari.properties.rpmsave .
- jce_policy.url
- server.version.file
- server.connection.max.idle.millis
Save the new ambari.properties to a backup folder and rename ambari.properties.rpmsave as ambari.properties.
Upgrade the schema for Ambari Server:
```
ambari-server upgrade
```
Local repository installs only: Take the version of the repoinfo.xml file you copied in Step 1, and copy it back to /var/lib/ambari-server/resources/stacks/HDPLocal/[1.2.0 or 1.2.1]/repos/repoinfo.xml.

Upgrade the Agent on all hosts:

For RHEL/CentOS
```
yum upgrade ambari-agent ambari-log4j
```
For SLES
```
zypper up ambari-agent ambari-log4j
```

Check to see if you have a folder named /etc/ambari-agent/conf.save on each Agent host. If you do, rename it back:
```
mv /etc/ambari-agent/conf.save /etc/ambari-agent/conf
```
Check to see if you have a file named ambari-agent.ini.rpmsave file. If you do, rename it back. On each Agent host:
```
mv /etc/ambari-agent/conf/ambari-agent.ini.rpmsave /etc/ambari-agent/conf/ambari-agent.ini
```
Update the stack version in the Server database, depending on if you are using a local repository:
```
ambari-server upgradestack HDP-1.3.0
```
OR
```
ambari-server upgradestack HDPLocal-1.3.0
```

Legal notices