Instructions for removing object protocol packages when upgrading protocol nodes to Red Hat Enterprise Linux 8.x

The presence of the object packages and their dependencies can prevent upgrade to Red Hat® Enterprise Linux®® 8.x. Therefore, it is necessary to remove the associated packages from the system when you are upgrading protocol nodes to Red Hat Enterprise Linux® 8.x. After the upgrade is complete, the object packages can be reinstalled.

Important:
  • CES Swift Object protocol feature is not supported from IBM Storage Scale 5.2.0 onwards.
  • IBM Storage Scale 5.1.8 is the last release that has CES Swift Object protocol.
  • IBM Storage Scale 5.2.0 will tolerate the update of a CES node from IBM Storage Scale 5.1.8.
    • Tolerate means:
      • The CES node will be updated to 5.2.0.
      • Swift Object support will not be updated as part of the 5.2.0 update.
      • You may continue to use the version of Swift Object protocol that was provided in IBM Storage Scale 5.1.8 on the CES 5.2.0 node.
      • IBM will provide usage and known defect support for the version of Swift Object that was provided in IBM Storage Scale 5.1.8 until you migrate to a supported object solution that IBM Storage Scale provides.
      • CES Swift Object is replaced with IBM Storage Scale S3. For more details, refer S3 support overview.
      • For more information about Swift Object in IBM Storage Scale, refer to the IBM Storage Scale 5.2.0 documentation.
  • Contact IBM for further details and migration planning.

The object protocol is only supported on Red Hat Enterprise Linux® 8.x with IBM Storage Scale version 5.1.0.1 and later. Systems at earlier versions of IBM Storage Scale with object protocol need to upgrade to version 5.1.0.1 or later after the system upgrade to Red Hat Enterprise Linux® 8.x.

Attention: The object protocol is not supported in IBM Storage Scale 5.1.0.0. If you want to deploy the object, upgrade to the IBM Storage Scale 5.1.0.1 or a later release.
  1. If the object protocol is running in the cluster, stop it according to the following instructions.
  2. After the object protocol is stopped, certain packages need to be cleaned up to prevent conflicts during the upgrade to Red Hat Enterprise Linux 8.x.
    Run the following command to uninstall these packages and their dependencies:
    yum erase isa-l liberasurecode openstack-keystone openstack-selinux openstack-swift-account openstack-swift-container openstack-swift-object 
    openstack-swift-proxy python2-bcrypt python2-cinderclient python2-dogpile-cache python2-glanceclient python2-keystoneauth1 python2-keystoneclient python2-keystonemiddleware 
    python2-neutronclient python2-novaclient python2-openstackclient python2-osc-lib python2-os-client-config python2-oslo-cache python2-oslo-concurrency python2-oslo-config 
    python2-oslo-context python2-oslo-db python2-oslo-i18n python2-oslo-middleware python2-oslo-service python2-pbr python2-pysocks python2-repoze-lru python2-requests 
    python2-requestsexceptions python2-scrypt python-argparse python-cadf python-cliff-tablib python-debtcollector python-dns python-funcsigs python-greenlet python-httplib2 
    python-jinja2 python-keystone python-msgpack python-openstackclient-lang python-oslo-cache-lang python-oslo-concurrency-lang python-oslo-db-lang python-oslo-i18n-lang 
    python-oslo-middleware-lang python-pip python-posix_ipc python-pyeclib python-simplejson python-sqlalchemy python-swift python-tablib python-testtools python-wrapt 
    python-wsgiref python-zope-event swift3 python-keyring python-idna python-PyMySQL 
  3. After the packages that are mentioned in the preceding step are removed, the following packages must be downgraded to the level of the system Red Hat Enterprise Linux packages by running the following command:
    yum downgrade pyOpenSSL python2-cryptography
    If these packages are not removed or downgraded, the upgrade to Red Hat Enterprise Linux 8.x using the leapp utility might fail with a message such as the following message:
    [ERROR] Actor: prepare_upgrade_transaction Message:  A Leapp Command Error occurred
    The leapp command with the --verbose option might display messages such as the following message:
    file *** from install of package ### conflicts with file from package ###
    If the messages are related to the packages associated with the object protocol, performing the cleanup steps eliminates these errors.
After the object protocol is stopped and the associated packages are removed, proceed with the Red Hat Enterprise Linux 8.x upgrade.
Note: Due to the object packages being removed for the leapp upgrade, these special steps need to be done when you are using the installation toolkit to upgrade the object protocol to version 5.1.x after the system upgrade is complete:
  1. Use the installation toolkit offline upgrade for the protocol nodes.
  2. After the installation toolkit has successfully completed the upgrade, manually migrate the object configuration data to version 5.1 by using the following command:
    mmobj config manage --version-sync
For more information, see Upgrading Swift Object packages to IBM Storage Scale 5.1.8 or earlier by using the installation toolkit.