APAR status
Closed as program error.
Error description
When using Kubernetes with IBM Spectrum Protect Plus, the Helm tool must be configured on the target cluster so that a new deployment can be ran with the helm command line. Deploying a package with Helm enables cluster-wide role-based access control (RBAC) rules and role bindings to be generated. For the Kubernetes cluster, to install Helm as root user with the Kubernetes administrative user account, run the following script, which is included in the installation package: ./helm_install_k8s.sh However, if this script fails, the script will not clean up after itself and will leave a folder titled "linux-amd64" found under the "install" folder. In addition to the folder not being cleaned up, the script does not handle an upgrade of Helm if it is already installed on the system. IBM Spectrum Protect Plus Versions Affected: 10.1.6 Initial Impact: MEDIUM Additional Keywords: TS003841773 SPP ISPP SPPSUP1809 K8 HELM
Local fix
1. If the helm_install_k8s.sh script fails: Remove manually the "linux-amd64" folder found under the ibm-spectrum-protect-plus-bundle/charts/ibm-spectrum-protect-plu s-prod/ibm_cloud_pak/pak_extensions/install folder and continue with Step 2. 2a. If a Helm 2.16.x version is not installed, then run the helm_install_k8s.sh script. 2b. If a Helm 2.16.x version is installed, then prior to running the helm_install_k8s.sh script again, update one line in this file: helm init -service-account tiller ?to?> helm init -upgrade --service-account tiller3. If running helm_install_k8s.sh script was successful, continue by running the helm_install.sh script to install the product. If there are still errors with either running this script or the baas_install.sh script, please contact support team.
Problem summary
**************************************************************** * USERS AFFECTED: * * IBM Spectrum Protect Plus level 10.1.6 * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * This problem is currently projected to be fixed in IBM * * Spectrum Protect Plus level 10.1.7. Note that this is * * subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
With IBM Spectrum Protect Plus 10.1.7, the behavior described will not be there because the script is not used in this level anymore. In IBM Spectrum Protect Plus 10.1.7, we are supporting a newer version of Helm and therefore no longer need the script in question. For users on IBM Spectrum Protect Plus 10.1.6, they should use the workaround as described under the Local Fix section.
Temporary fix
Comments
APAR Information
APAR number
IT34617
Reported component name
SP PLUS
Reported component ID
5737SPLUS
Reported release
A16
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-10-20
Closed date
2020-11-30
Last modified date
2020-11-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SP PLUS
Fixed component ID
5737SPLUS
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A16","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
31 January 2024