Step 4: After you upgrade the Operating System to a new Major Version

Cloudera Manager needs access to a package repository that contains the updated software packages. You can choose to access the Cloudera public repositories directly, or you can download those repositories and set up a local repository to access them from within your network. If your cluster hosts do not have connectivity to the Internet, you must set up a local repository.

1. Log in to the Cloudera Manager Server host.

   ssh my_cloudera_manager_server_host

2. Log in to each cluster host.

   ssh cluster_host

3. Remove any older files in the existing repository directory:

   RHEL / CentOS

   sudo rm /etc/yum.repos.d/cloudera*manager.repo*

   SLES

   sudo rm /etc/zypp/repos.d/cloudera*manager.repo*

   Ubuntu

   sudo rm /etc/apt/sources.list.d/cloudera*.list*

4. Fill in the form at the top of this page.
5. Create a repository file so that the package manager can locate and download the binaries. Do one of the following, depending on whether or not you are using a local package repository:

   • Using a local package repository. (Required when cluster hosts do not have access to the internet.)

     1. Configure a local package repository hosted on your network.
     2. In the Package Repository URL, replace the entire URL with the URL for your local package repository. A username and password are not required to access local repositories.
     3. Click Apply.

   • Using the Cloudera public repository

     1. Substitute your USERNAME and PASSWORD in the Package Repository URL where indicated in the URL.
     2. Click Apply

   Package Repository URL:

6. RHEL / CentOS

   Create a file named /etc/yum.repos.d/cloudera-manager.repo with the following content:

   [cloudera-manager]
   # Packages for Cloudera Manager
   name=Cloudera Manager
   baseurl=https://archive.cloudera.com/p/cm7/[**Cloudera Manager version**]/redhat[version]/yum/
   gpgkey=https://archive.cloudera.com/p/cm7/[**Cloudera Manager version**]/redhat[version]/yum/RPM-GPG-KEY-cloudera
   gpgcheck=1

   Copy this file to the same location on all cluster hosts.

   SLES

   Create a file named /etc/zypp/repos.d/cloudera-manager.repo with the following content:

   [cloudera-manager]
   # Packages for Cloudera Manager
   name=Cloudera Manager
   baseurl=https://archive.cloudera.com/p/cm7/[**Cloudera Manager version**]/sles[version]/yum/
   gpgkey=https://archive.cloudera.com/p/cm7/[**Cloudera Manager version**]/sles[version]/yum/RPM-GPG-KEY-cloudera
   gpgcheck=1

   Copy this file to the same location on all cluster hosts.

   Ubuntu

   Create a file named /etc/apt/sources.list.d/cloudera_manager.list with the following content:

   # Packages for Cloudera Manager
   deb [arch=amd64] https://myUsername:myPassword@archive.cloudera.com/p/cm7/[**Cloudera Manager version**]/ubuntu[version]/apt focal-cm[**Cloudera Manager version**] contrib 

   Run the following command:

   sudo apt-get update

   Copy this file to the same location on all cluster hosts.

   The repository file, as created, refers to the most recent maintenance release of the specified minor release. If you would like to use a specific maintenance version, for example 5.15.1, replace 5.15 with 5.15.1 in the generated repository file shown above.

7. A Cloudera Manager upgrade can introduce new package dependencies. Your organization may have restrictions or require prior approval for installation of new packages. You can determine which packages may be installed or upgraded:

   RHEL / CentOS

   yum deplist cloudera-manager-agent

   SLES

   zypper info --requires cloudera-manager-agent

   Ubuntu

   apt-cache depends cloudera-manager-agent