Cloudera Docs

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

Loading Filters ... 7.13.1 7.11.3 7.7.3 7.7.1 7.6.7 7.6.1 7.4.4 7.3.1 7.1.9.1000 7.1.9 7.1.8 7.1.7.3000 7.1.7.2000 7.1.7.1000 7.1.7 7.1.6 7.3.1 7.1.9.1000 7.1.9 7.1.8 7.1.7.3000 7.1.7.2000 7.1.7.1000 7.1.7

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

This topic describes how to upgrade the operating system on a Cloudera Manager managed host.

Establish Access to the Software

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/cm5/redhat/7/x86_64/cm/5.15
gpgkey=https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck=1
    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/cm5/sles/12/x86_64/cm/5.15
gpgkey=https://archive.cloudera.com/cm5/sles/12/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck=1
    Ubuntu
    Create a file named /etc/apt/sources.list.d/cloudera_manager.list with the following content:
    # Packages for Cloudera Manager
deb https://archive.cloudera.com/cm5/debian/jessie/amd64/cm/ jessie-cm5.15 contrib
deb-src https://archive.cloudera.com/cm5/debian/jessie/amd64/cm/ jessie-cm5.15 contrib
    Run the following command:
    sudo apt-get update

    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

Start Databases

  1. If you are using the embedded PostgreSQL database, start the database:
    sudo systemctl start cloudera-scm-server-db
  2. If there were database servers stopped, they must be restarted.

Start Cloudera Manager Server & Agent

The appropriate services typically will start automatically on reboot. Otherwise, start the Cloudera Manager Server & Agent as necessary.

  1. Start the rpcbind service if it is not automatically started. 
    sudo service rpcbind start
  2. Start the Cloudera Manager Agent.
    RHEL 7, SLES 12, Ubuntu 18.04 and higher
    sudo systemctl start cloudera-scm-agent
    If the agent starts without errors, no response displays.
    RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
    sudo service cloudera-scm-agent start
    You should see the following: 
    Starting cloudera-scm-agent: [ OK ]
  3. Start the Cloudera Manager Server.
    sudo systemctl start cloudera-scm-server
  4. Verify that the Cloudera Manager Agent downloaded a proper parcel for your new operating system. You can use the following command to check in Cloudera Manager logs for downloaded parcels: 
    grep "Completed download" /var/log/cloudera-scm-agent/cloudera-scm-agent.log
    (Download might take some time. Look for the operating system in the names of the downloaded parcels.

Start Roles

  1. From the All Hosts page, select the host that you have just upgraded.
  2. Choose End Maintenance (Enable Alerts/Decommission) from the Actions menu and confirm.
  3. Start any Cloudera Management Service roles that were running on this host and were stopped.
  4. Choose Host Recommission from the Actions menu and confirm.
  5. Choose Start Roles on Hosts from the Actions menu and confirm.
  6. Start any services that were stopped due to lack of high availability.