Upgrade Readiness App Does not Upgrade in Cluster

Applicability

Description

While trying to upgrade the apps on SHC through Deployer under  $SPLUNK_HOME/etc/shcluster/apps, running: splunk apply shcluster-bundle fails to upgrade and throws the below warning.

Warning: Depending on the configuration changes being pushed, this command might initiate a rolling restart of the cluster members. Please refer to the documentation for the details. Do you wish to continue? [y/n]: yWARNING: Server Certificate Hostname Validation is disabled. Please see server.conf/[sslConfig]/cliVerifyServerName for details. The configuration bundle contains the following default apps: python_upgrade_readiness_app.Do not use the deployer to push default apps to the search head cluster members. Read the topic "Use the deployer to distribute apps and configuration updates" in the Distributed Search manual on docs.splunk.com for details.If you are sure you want to do this, push the configuration bundle again using the "-push-default-apps true" option.splunk apply shcluster-bundle -push-default-apps trueWarning: Depending on the configuration changes being pushed, this command might initiate a rolling restart of the cluster members. Please refer to the documentation for the details. Do you wish to continue? [y/n]: yBundle has been pushed successfully to all the cluster members.

As python_upgrade_readiness_app is a default app, it causes failure to upgrade other apps. 

Investigation

Warnings when bundles with default apps are pushed:

Do not use the deployer to push default apps to the search head cluster members. Read the topic "Use the deployer to distribute apps and configuration updates" in the Distributed

Please Note:  It is not the best practice to migrate default apps to SHC, as the default apps version will change in accordance with the Splunk Enterprise version while upgrading.

The below document will explain it: Migrate from Standalone Searchheads 

Resolution

Workaround:
 

Since the URA app failed to upgrade, the below procedure needs to be followed to upgrade the app to the latest version.

1. Add the built-in app to the bundle on the deployer

2. Perform a push using -push-default-apps true

3. Remove the app from the bundle

4. Perform subsequent pushes without the -push-default-apps true option.

This will leave the built-in app upgraded on the SHC members until the next Splunk upgrade or bundle push with the built-in app included and -push-default-apps true set. This does require extra steps however upgrading this app should be rarely needed.

If the above workaround does not work, please follow the below resolution.

Resolution:

Best Practice: Instead of upgrading the default apps to the latest version, upgrade the Splunk Enterprise version which contains the latest default apps.

Related Links