Applying the Fix Pack 2

Use this information if you have IBM® Telco Network Cloud Manager - Performance, version 1.4.6 is already installed.

Apply the Telco Network Cloud Manager - Performance Fix Pack 2 on Red Hat® OpenShift® by using the Operator Lifecycle Manager (OLM) user interface and CASE (Container Application Software for Enterprises).

Before you begin

Download the command-line tool cloudctl version 3.12.x..
Download IBM Cloud Pak® CLI (cloudctl) from https://github.com/IBM/cloud-pak-cli/releases link. The cloudctl verifies the integrity of the Telco Network Cloud Manager - Performance CASE's digital signature by default. If you want to verify the cloudctl binary, follow the instructions in https://github.com/IBM/cloud-pak-cli#check-certificatekey-validity link. Extract the cloudctl binary, give it executable permissions, and ensure that it is in your PATH.

Uninstall the 1.4.6 Operator

Log in to OpenShift Container Platform web console.
If you renamed any annotation manager values previously, you must rename them back to the original name tncp-operator.
Stop all processors that are running in the NiFi user interface.
Go to Operators > OperatorHub > openshift-marketplace and search for tncp.
Click the installed Telco Network Cloud Manager - Performance, 1.4.6 version, and then click Uninstall.
Note: Do not delete the instance. All the Pods are still running.

Applying the Fix Pack 2

Install the catalog in the openshift-marketplace project by using the following command:

cloudctl case launch --case ibm-tncp-case-1.4.6-fp002.tgz --namespace openshift-marketplace --inventory operator --action install-catalog --tolerance 1

You can see the following output:

# cloudctl case launch --case ibm-tncp-case-1.4.6-fp002.tgz --namespace openshift-marketplace --inventory operator --action install-catalog --tolerance 1

Welcome to the CASE launcher

Attempting to retrieve and extract the CASE from the specified location

[✓] CASE has been retrieved and extracted

Attempting to validate the CASE

Skipping CASE validation...

Attempting to locate the launch inventory item, script, and action in the specified CASE

[✓] Found the specified launch inventory item, action, and script for the CASE

Attempting to check the cluster and machine for required prerequisites for launching the item

Checking for required prereqs...

 

Prerequisite                             Result

Kubernetes version is 1.14.6 or greater  true

Cluster has at least one amd64 node      true

 

Required prereqs result: OK

Checking user permissions...

 

Kubernetes RBAC Prerequisite                            Verbs                               Result  Reason

rbac.authorization.k8s.io.clusterroles/*                get,list,watch,create,patch,update  true

apiextensions.k8s.io.customresourcedefinitions/v1beta1  get,list,watch,create,patch,update  true

security.openshift.io.securitycontextconstraints/       get,list,watch,create,patch,update  true

 

User permissions result: OK

[✓] Cluster and Client Prerequisites have been met for the CASE

Running the CASE operator launch script with the following action context: installCatalog

Executing inventory item operator, action installCatalog : launch.sh

-------------Installing Catalog-------------

Error from server (AlreadyExists): namespaces "openshift-marketplace" already exists

Context "noi/api-tncpdevbvt2-cp-fyre-ibm-com:6443/kube:admin" modified.

Already on project "openshift-marketplace" on server https://api.tncpdevbvt2.cp.fyre.ibm.com:6443.

catalogsource.operators.coreos.com/ibm-tncp-catalog configured

[✓] CASE launch script completed successfully

OK

Verify that the catalog Pod is running in the openshift-marketplace project.
Go to Operators > OperatorHub > openshift-operators and search for tncp.
You can see an extra tile for the Fix Pack 2 catalog.
Click the FP002 catalog tile and click Install.
From the Install Operator page, provide the following details:
- Update Channel
  The supported update channels are shown, with 1.4 selected by default. It indicates that an Operator subscription is automatically created to keep the Operator up to date when new versions are delivered to the channel.
  Note: Make sure to select 1.4 channel.
- Installation Mode
  Choose whether to install the Operator into all namespaces in the cluster or into a specific namespace. By default, All namespaces on the cluster is selected.
- Installed Namespace
  By default, openshift-operators is selected. If you install the Operator in the openshift-operators project, it is accessible by all other projects or namespaces.
  Note: If you chose the option A specific namespace on the cluster, you can change the namespace. This option is not supported for the IBM Telco Network Cloud Manager - Performance Operator.
- Approval Strategy
  Click Automatic to indicate that the installation must proceed with no additional approval. The running instance of your Operator is automatically upgraded whenever new versions are delivered to the channel.
  
  Click Manual if you want to review a generated Install Plan for the Operator and then manually approve the installation. You must review the Install Plan for each new Operator version that is delivered to the channel, and then manually approve an upgrade.
  
  Note: If needed, you can change the approval strategy later.
Verify that the operator Pod is created and running in the openshift-operators project.
Go to the tncp project from Operators > Installed Operators > tncp.
Go to Workloads > Pods and verify that all Telco Network Cloud Manager - Performance Pods are re-created with the latest image.
Note: If the Inventory Pod is not up and running, restart it.
If you had an updated annotation manager value for any specific configuration changes, configure the parameters again and rename the manager value.

Install Technology Packs

After Telco Network Cloud Manager - Performance is installed, follow the steps in Installing Technology Packs to install the Technology Packs: